How to Build a Network in Tech When You Don't Know Anyone

TL;DR

Starting from zero is normal, especially for bootcamp grads and career changers.
You don't need a large network. A handful of real connections at target companies does more than hundreds of LinkedIn followers.
Begin with weak ties: former colleagues, classmates, and LinkedIn alumni who have already made the move to tech.
Then expand into communities where engineers actually spend time (Discord servers, meetups, open source projects).
Make yourself findable before you reach out. A complete LinkedIn profile and a public GitHub matter.
This takes months. Plan for it.

Most people who are early in a tech job search feel like they're starting from nothing. They don't have a friend who works at a company they're targeting. They didn't go to a school with a strong CS alumni presence. They came from another industry, or they went to a bootcamp, or they just graduated and haven't had a chance to build anything yet.

That's a reasonable place to be. It doesn't mean you're at a structural disadvantage that can't be closed. It means you need to be deliberate about it.

The mistake most people make is thinking that "networking" means showing up to a networking event, handing out business cards, and hoping something happens. That approach is ineffective for almost everyone. Effective networking is quieter, slower, and more intentional. It's a series of individual conversations, not a blitz of mass outreach.

Here's the sequence that actually works.

Step 1: Map What You Already Have

Before you reach out to anyone new, figure out who you already know who might have even a loose connection to tech.

This is called working your weak ties. Weak ties are acquaintances rather than close friends. They work differently from strong ties in a job search. Your close friends know mostly what you know. Your acquaintances (former colleagues, people you went to school with, people you've met at events in other contexts) often have access to entirely different social circles and information.

Ask yourself:

Did anyone I worked with before transition into a tech role?
Is anyone from my university or bootcamp cohort working at a company I'd like to work at?
Does anyone I know peripherally work at a tech company, even in a non-engineering role?
Are there people I connected with years ago on LinkedIn who are now in the industry?

You don't need these people to be your close friends. You need them to have a reason to take a short conversation with you. Former colleagues, former classmates, and people you've had even one real interaction with are much more likely to respond than complete strangers.

Start by making a list of 10 to 20 people who fit this description. That's your first outreach list.

Step 2: Use LinkedIn Alumni Search Before Reaching Out Cold

Before you approach anyone you don't know at all, exhaust the LinkedIn alumni search. Most people skip this step and go straight to cold outreach. That's harder than it needs to be.

Here's what the LinkedIn alumni search actually does. If you go to your school's LinkedIn page, there's usually an "Alumni" tab. You can filter by where they work, what they do, and when they graduated. This is one of the most underused job search tools available.

If you went to a coding bootcamp, the same logic applies. Most bootcamps have LinkedIn alumni pages. Search for people from your cohort or earlier cohorts who are now working as engineers.

The reason this matters is that shared background is a genuine reason to reach out. "I'm a recent grad from X program and I noticed you made the transition to Y company" is a real opener. It's not manufactured. The person has a reason to be receptive, because they were once where you are.

Reaching out to engineers effectively covers exactly what to say once you've found someone worth contacting. The short version: keep it short, make a specific ask (usually 15 to 20 minutes of their time), and don't ask for a job in the first message.

Step 3: Join Communities Where Engineers Actually Spend Time

Once you've worked through your warm leads, you need to build new connections. The most effective places to do this right now are Discord servers, local meetups, and (if you have the time) open source projects.

Discord servers have become one of the main hubs for developers to discuss problems, share resources, and find each other. Many servers have job boards, career channels, and places where engineers talk openly about their work. If you participate consistently in a server over a few months, people start to recognize your name. That recognition is the beginning of a real connection.

The key word is "participate." Lurking builds nothing. Answering questions when you can, sharing something useful you found, and asking specific questions that show you've done some homework: those are the things that make you visible in a positive way. Discord communities for junior developers covers how to evaluate servers and participate in a way that builds a reputation rather than just noise.

Local meetups are uneven. Some are good; some are mostly sales people trying to sell you things. The good ones tend to be organized around specific technologies (a local Ruby group, a frontend meetup, a machine learning study group) rather than general "tech networking" events. Events built around learning rather than pitching tend to attract people who are there to talk shop, which makes real conversations easier.

When you go to a meetup, don't try to collect contacts. Try to have one or two real conversations. Ask what the person is working on. Ask what they like about it. Talk about something you're building. That's it. You don't need to pitch yourself. The goal is to meet one person you'd want to follow up with.

Open source contribution is slower but has a high ceiling. If you start contributing to a project, even with documentation updates, issue triage, or small bug fixes, you start showing up in that project's GitHub history. Maintainers and regular contributors notice. Over time, those interactions can become professional relationships. This only works if you stick with it for months, not days.

Step 4: Make Yourself Findable

This step often gets skipped because it feels passive. But if you're doing outreach and your LinkedIn profile is incomplete or your GitHub is empty, you're making it harder for people to say yes to you.

When someone gets a message from you, the first thing they'll do is look you up. What they find matters.

A complete LinkedIn profile means: a current headline that says what you're working toward (not just "student"), a summary that explains your background and what you're building, and links to projects or a portfolio. You don't need a long bio. You need enough that someone can confirm you're a real professional making a genuine effort.

A public GitHub means: repositories with readable code, commit history that shows you're actively working, and READMEs that explain what each project does and why it exists. Good GitHub profiles covers what actually matters in detail, but the summary is: show that you write code consistently and that you can explain your own work.

Being findable also means showing up in searches. If your LinkedIn headline says "looking for work" but doesn't mention what kind of work, what technologies you use, or what you're building, you won't show up when a recruiter or hiring manager is searching for candidates. Specificity helps.

Step 5: Do the Outreach

With a list of people to contact and a profile that makes you look credible, now you actually reach out.

The full networking guide covers this in depth. For building from scratch, the specific principles that matter most:

Volume matters, but quality matters more. Sending 50 identical messages gets worse results than sending 10 personalized ones. Each message should reference something specific about the person: where they work, something they've written, a project they've contributed to, or the background you share.

The ask is almost always "15 minutes of your time." Not "can you help me get a job," not "can I pick your brain" (vague and often annoying), but a specific, bounded request for a short conversation. Most people can say yes to 15 minutes. Almost no one wants to say yes to an open-ended commitment.

Expect a low response rate and plan for it. If 1 in 5 or 1 in 10 people respond, that's normal. It's not a reflection of your worth. People are busy. Messages get missed. If you send out 20 good outreach messages and get 4 conversations, that's a productive week.

Follow up once. If you don't hear back in a week or so, send a single short follow-up. Something like: "Following up in case this got buried. Happy to keep it short. Let me know if there's a good time." If you still don't hear back, move on. Chasing people creates a bad impression and wastes your time.

Step 6: Convert Conversations Into Ongoing Connections

The goal of a networking conversation is not to get a referral. It's to have a real conversation with someone who works in the industry, leave a good impression, and open the door to a relationship that might lead somewhere over time.

After a conversation, send a short thank-you message within 24 hours. Reference one thing you talked about. Keep it to 3 to 5 sentences.

Then, a few weeks or a month later, follow up with something useful. An article they might find interesting. A question that came out of something they mentioned. An update on something you said you were working on. This is how acquaintances become real contacts over time. Not through a single interaction, but through a handful of interactions over months.

The referral playbook covers what to do when you're ready to ask someone for a referral specifically. That's a distinct conversation from a general networking chat, and timing it right matters.

The Realistic Timeline

Building a network from scratch takes months, not days. Most people who complain that networking "doesn't work" tried it for two or three weeks and gave up.

Here's a realistic expectation: in the first month, you're doing a lot of profile work and low-volume outreach. In months two and three, you're having your first real conversations and starting to show up in communities. By month four or five, you have a small set of real contacts in the industry. By month six, one or two of those contacts might be in a position to vouch for you or pass along a referral.

That timeline sounds long. But if you're serious about a tech job search, you're already going to be at this for months. Adding consistent, low-volume networking to your routine costs a few hours a week and changes the trajectory of your search.

You don't need to know 500 people in tech. You need to know 10 to 20, well enough that a few of them would respond if you asked for help. That's achievable starting from zero.

For more on what to actually say when you reach out, read how to reach out to engineers you don't know. If you want to understand how LinkedIn can work as a networking tool without feeling like self-promotion, LinkedIn without feeling like a spammer is worth reading before you update your profile.

If you want structured support building your network alongside the rest of your job search, here's how the Globally Scoped program works.