Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
98 changes: 95 additions & 3 deletions org-cyf-guides/content/employability/networking/_index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,98 @@
---
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 - if you need help with this, check out the [LinkedIn guide](../linkedin-profile)
- 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:**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The 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.

When thinking about who to connect with, focus on people at a similar level to you — other software engineers, bootcamp graduates, or people a year or two into their careers. Peer connections are often more natural, more likely to lead to genuine relationships, and can be just as valuable as speaking to senior people. Engineering managers and senior leaders can be harder to reach and may have less time, so connecting sideways rather than upwards is usually a more effective place to start.

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.

**Starting a conversation** can feel like the hardest part. A simple opener is often enough - commenting on the event, the speaker, or something in the environment gives a natural starting point. If you can find common ground early - even something unrelated to work, like where someone is based or a shared experience - the conversation tends to flow more easily from there.

**Leaving a conversation** gracefully is just as important. You don't need to wait for an awkward silence. A simple close works well: "It was really good to meet you, I'll connect with you on LinkedIn." That's it. It's polite, it's natural, and it sets up the next step without any pressure.

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

Here are some examples of good networking questions to get you started:
- "What does a typical day look like for you in this role?"
- "What's been the most useful thing you've learned on the job?"
- "Is there anything you wish you'd known when you were starting out?"
- "What kinds of problems does your team spend most of its time solving?"

These work because they invite the other person to share their experience rather than putting them on the spot or asking for favours.

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:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The 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.

- At the end of a conversation, ask for the person's LinkedIn and connect with them on the spot — it's easy to forget names afterwards and LinkedIn is a better first step than asking for a phone number or email, as it feels less personal and more professional.
- 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?
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
title: Networking Practice Exercises
date: 2024-07-17T11:13:37
description: Practice networking conversations with your peers
emoji: 🤝
weight: 7
---

# Networking: Collective Exercise

Practising with peers helps you build confidence before real networking situations. Use this session to try out your introduction, test your questions, and write a follow-up message with support from the group.

## Learning Objectives

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

1. Each person drafts a short introduction (who you are, what you're learning, what role you're interested in).
2. In pairs, practice your introductions with each other.
3. Ask each other 2–3 networking questions and practice listening and responding naturally.
4. Write a short follow-up message as if you had just met this person at an event.
5. Share your follow-up messages with the group and discuss: does it feel natural? Is there anything you would change?
Loading