-
-
Notifications
You must be signed in to change notification settings - Fork 126
Add networking guide content #1758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,102 @@ | ||
| --- | ||
| emoji: 🥅 | ||
| title: Networking | ||
| description: Show employers your true potential by optimising your Linkedin profile | ||
| weight: 5 | ||
| date: 2024-07-17T11:13:37 | ||
| description: Build connections to support your job search | ||
| emoji: 🤝 | ||
| weight: 6 | ||
| --- | ||
| # Networking | ||
| In this guide, we will review how to network effectively as an early-career person in tech. It is structured around three parts: getting into the right headspace before reaching out, having simple and honest conversations in different settings, and turning those connections into small, natural next steps that support your job search over time. | ||
|
|
||
| To use this guide you should: | ||
| - Have a basic understanding of the type of role or area in tech you're interested in | ||
| - Have a LinkedIn profile or be in the process of setting one up | ||
| - Be open to having short, low-pressure conversations with people in the industry | ||
|
|
||
| After using this guide you will: | ||
| - Approach networking with a clearer and more realistic mindset | ||
| - Know how to start simple conversations in different settings (in-person, online, one-to-one) | ||
| - Be able to turn conversations into small, natural next steps | ||
|
|
||
| ## Getting Ready to Network | ||
| For many early-career people in tech, networking brings mixed feelings. Some days it sounds useful, other days it feels tiring or unnecessary. Very often, there's resistance at the start, followed by a quiet realisation afterwards that it wasn't as bad as expected, and sometimes even enjoyable. That experience is common, even if people don't always say it out loud. | ||
|
|
||
| Networking isn't a performance, and it isn't a test of confidence. It's also not something only outgoing people are good at. Many strong connections come from quieter conversations, where someone listens carefully, asks thoughtful questions, and takes genuine interest. That approach often suits junior roles in tech, where curiosity and clear thinking matter more than being loud or confident. | ||
|
|
||
| It helps to be clear about what networking is, and what it isn't. | ||
|
|
||
| **Networking is a way to:** | ||
| 1. Learn how roles and teams really work, beyond job descriptions. | ||
| 1. Build familiarity and trust over time. | ||
| 1. Stay motivated and connected during a long job search. | ||
|
|
||
| **Networking isn't:** | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I really like this framing of what it is and isn't 😃 |
||
| 1. Asking strangers for jobs. | ||
| 1. Collecting contacts without purpose. | ||
| 1. A guarantee of immediate results. | ||
|
|
||
| When job searching becomes intense, it can start to take over everything. Every spare hour goes into another application, another form, another rejection. Networking can feel like extra effort on top of that. For many people, though, it becomes the more human part of the process. It creates moments of connection and perspective, which can matter more than they seem at first. | ||
|
|
||
| **Exercise:** | ||
| - Write down one reason you feel hesitant about networking | ||
| - Write down one thing you genuinely want to learn from someone working in tech | ||
|
|
||
| Note: How does reframing networking as "learning from someone" feel compared to "asking for a job"? | ||
|
|
||
| ## Having Simple, Human Conversations | ||
| Early-career networking works best when it stays simple. You're not expected to impress anyone or to have everything figured out. Most people respond well to honesty, curiosity, and clear intent. | ||
|
|
||
| Applications often remove context. A CV lists skills, a form asks for examples, but neither shows how someone thinks or what they're curious about. Conversations allow that to come through naturally. They also give space for people to speak more openly about what their work actually involves, what they enjoy, and what they've learned along the way. | ||
|
|
||
| Networking conversations can happen in many places: | ||
| 1. **In-person events and meetups**, where a shared topic gives an easy starting point. | ||
| 1. **One-to-one coffee chats**, which often feel more comfortable for quieter personalities. | ||
| 1. **Online spaces** such as LinkedIn, Slack groups, or tech communities, where engagement can happen at a slower pace. | ||
|
|
||
| Good conversations are rarely complicated. They usually involve a few simple questions, careful listening, and a short, clear introduction about where you're at and what you're trying to learn. You don't need to speak to everyone in the room. One conversation that feels real is often enough. | ||
|
|
||
| It's also worth remembering that a conversation doesn't need to lead to a job to be valuable. Gaining clarity, hearing a different perspective, or feeling less alone in the process are all meaningful outcomes. | ||
|
|
||
| **Exercise:** | ||
| - Draft a short introduction (3–4 sentences) about who you are, what you're learning, and what kind of role you're interested in | ||
| - Write 2–3 questions you could ask someone working in a role you're interested in | ||
|
|
||
| Note: Do your questions invite the other person to share their experience, or do they only ask for help? | ||
|
|
||
| ## Turning Connections into Next Steps | ||
| For early-career professionals, the job market can feel especially tough right now. In the age of AI, junior roles are often filtered first. Applications are screened quickly, and many people never hear back. When this happens repeatedly, it can quietly affect confidence and motivation. | ||
|
|
||
| A common response is to apply to more roles, faster. While that reaction makes sense, it often leads to exhaustion rather than progress. Networking doesn't fix the system, but it does change how you experience it. | ||
|
|
||
| Through conversations, people become more than a CV. Others start to understand how you think, what you care about, and where you're trying to go. These are things automated systems struggle to capture. Over time, this context can make a real difference. | ||
|
|
||
| Moving from a conversation to a next step doesn't need to feel awkward: | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would explicitly suggest that people ask for other people's LinkedIn at the end of a conversation and add them during the interaction. I've made the mistake myself of thinking I'll remember someone's name and then forgetting it. And I think we should also suggest LinkedIn is better than phone numbers or emails at least initially as it's less private. |
||
| - Send a short thank you message after a chat | ||
| - Mention something specific you found helpful — this shows attention and care | ||
| - Stay lightly in touch without asking for anything, allowing the relationship to develop naturally | ||
|
|
||
| When it does feel right to ask for help, asking for **advice** is often easier than asking for **favours**. Questions about what to focus on next, which skills matter most, or who else might be helpful to speak to open doors without pressure. | ||
|
|
||
| **Exercise:** | ||
| - After a networking conversation, write a short follow-up message you could send (2–4 sentences) | ||
|
|
||
| Note: Does your message mention something specific from the conversation? Does it avoid asking for anything directly? | ||
|
|
||
| ## Learning Objectives | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd suggest splitting out the group exercises to a different page as currently it's a bit disjointed. The previous exercises on the page felt more individual to be done whilst reading this page but the group one with the mention of the timer is for a different context. This is how I did it on one of the page I was doing which had a similar thing. https://curriculum.codeyourfuture.io/guides/employability/job-search/ |
||
| Our goal is to collectively do the following: | ||
| - [ ] Identify the difference between asking for a job and asking for advice. | ||
| - [ ] Draft a short personal introduction suitable for a networking conversation. | ||
| - [ ] Write 2–3 questions to use in a networking conversation. | ||
| - [ ] Reach out to at least one person in your network or the CYF community. | ||
| - [ ] Write a follow-up message after a networking conversation. | ||
|
|
||
| ## Set-Up | ||
| - [ ] Split up into pairs or groups of no more than 3 | ||
| - [ ] Set a whole class timer for 20 minutes | ||
|
|
||
| ## Instructions | ||
| - [ ] Each person drafts a short introduction (who you are, what you're learning, what role you're interested in). | ||
| - [ ] In pairs, practice your introductions with each other. | ||
| - [ ] Ask each other 2–3 networking questions and practice listening and responding naturally. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it might be useful for the trainees to see some examples of what appropriate "networking questions" are - for me, I like to express (often very fake) interest in whatever the person I'm talking to is doing: "Oh you work in insurance systems? - I bet keeping up with the changes in a regulated industry is challenging - how does knowing those changes are coming impact your roadmap planning?" (ugh that conversation didn't even really happen and I'm already bored). |
||
| - [ ] Write a short follow-up message as if you had just met this person at an event. | ||
| - [ ] Share your follow-up messages with the group and discuss: does it feel natural? Is there anything you would change? | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd recommend adding an internal link to the LinkedIn guide like (../../linkedin-profile)). If you need help with markdown just let me know and I can do the change on your branch.