Networking for Software Engineers Who Hate Networking

"Networking" might be the most disliked word in software engineering. It conjures business cards, forced coffee chats, and posts that open with "Thrilled to announce." I dislike all of that as much as you probably do, which is why it took me an embarrassingly long time to notice the pattern in my own career: nearly every job I've held traces back to a person rather than a posting. A former teammate reached out, or I reached out to a former teammate, or a coworker carried my resume to the right desk and a process that ignores thousands of cold applicants suddenly moved in days.

One note on vantage point before we get into it. Unlike my interviewer-side articles, there's no chair of authority here, since nobody interviews you on networking. This is candidate-side experience, mine plus a lot of conversations with engineers mid-search, so weigh it accordingly.

The public data on how people actually land jobs shifts around depending on who ran the survey, but referrals and former colleagues consistently sit at or near the top, and that lines up with my own history closely enough that I'll say it plainly: your next two jobs will most likely come from people you already know. The encouraging part is that the version of networking which produces this result is lightweight, mostly generous, and rarely feels like networking while you're doing it.

Why the warm intro wins

The real function of a referral is skipping the pile. Someone inside the company vouches for you, so a human reads your resume with a mild positive prior instead of an algorithm scanning it with none. A referral also derisks the hire, because "a person I trust worked with this candidate and would gladly do it again" answers the question a resume can barely gesture at. I'm working on a fuller piece about how applications actually get seen, and the channel math there is sobering, but the short version is that one genuine relationship realistically outweighs a weekend of one-click applying.

Keeping in touch without the coffee chats

This is the part everyone assumes takes real effort, and in practice it's the cheapest part of the whole system. Three habits cover it. Congratulate former coworkers when they land somewhere new (a sentence is enough). Leave a genuine comment when someone you worked with ships or writes something, and make it specific, because "congrats!" is filler while "loved that migration writeup, we fought the same foreign key problem last year" is a relationship. And once or twice a year, when something genuinely reminds you of a specific person, send the check-in ("saw the news about your company and thought of you, how's the new team?").

Two or three real touches a year keeps a working relationship warm essentially indefinitely, and the bar is modest: the person remembers working with you fondly and knows roughly what you do now. Building that foundation across your whole network costs maybe an hour a quarter.

Being findable

Plenty of us carry around a Field of Dreams theory of career growth, where you quietly do excellent work and the recruiters simply appear. Build it and they will come, except they also need a way to find the field. Being findable comes down to two small investments. The first is a profile that states in plain words what you do ("backend engineer, payments infrastructure, mostly Go and Postgres"), because whoever is looking for you is searching in plain words, and a clever headline hides you. The second is one or two public artifacts with your name attached, in whatever form suits your temperament: a writeup of a problem you solved, a small repository, a meetup talk, thoughtful public answers. You don't need anything resembling a "personal brand" (a phrase I find as itchy as you do). A single artifact does the job, because its purpose is that when a former coworker's team opens a role and your name surfaces, the easy vouch is right there: "she's great, and here's her writeup on exactly this kind of problem."

Give before you ask

Some care is warranted here, because running a favor ledger is its own kind of gross and people sense it immediately. The framing that has worked for me is simpler: being generous now makes asking later feel normal in both directions. In practice that looks like introducing two people who would clearly benefit from knowing each other, answering the question you happen to know the answer to, and walking a former teammate's resume in when your own company is hiring (ten minutes of your time, remembered for years, and it teaches you what a good referral ask looks like from the receiving end). It also looks like reviewing a friend's resume or running them through a practice round before their loop. None of it is clever strategy. It just means that when you eventually need something, you already exist in people's memory as someone who helps, and your ask reads completely differently.

A warm note versus a cold pitch

Two messages, both composites of patterns I've genuinely seen, details changed. First, the cold pitch:

"Hi, I came across your profile and was really impressed by your journey! Would love to pick your brain sometime. Also, would you be able to refer me for the SDE II opening?"

It fails almost every time, and the reasons are worth spelling out. It asks a stranger to spend internal credibility on someone they cannot vouch for, the flattery is copy-paste generic, and "pick your brain" is an unbounded request with no shape. Most recipients ignore it and feel faintly guilty doing so.

Now the warm note:

"Hey Priya, I saw [company] just opened a role on the payments team. I've been doing fraud detection work at [current company] for the past three years and I'm starting to look around. No pressure at all, and no worries if the answer is no, but if you like it there I'd love 15 minutes to hear what the team is actually like before I apply."

Same species of message, entirely different animal: an existing relationship, a specific role, one sentence of context that makes vouching easy, a small bounded ask (and note that it requests a conversation rather than a referral), and an explicit out. In my experience the referral tends to get offered unprompted somewhere in that conversation, precisely because you made offering it feel easy and safe.

Reconnecting after years of silence deserves its own line, because the anxiety around it stops a lot of people. Just name it. "I know it's been a while, and I'll be honest that I'm reaching out partly because I'm starting a job search" works far better than pretending the gap isn't there. People respect the honesty, and nearly everyone has sent some version of that message themselves.

Plant before you need the fruit

In the 4-week prep plan I compared starting interview prep to planting a fruit tree, where the best time to start was a while ago and the second best time is now. Relationships follow the same rule with even higher stakes, because at least a fruit tree grows on a schedule you can look up. You cannot plant a seed the week you're hungry. A network watered with a few honest messages a year, sustained over years, yields the one thing no amount of money buys during a layoff: people who already trust you, thinking of you the moment a role opens.

If you're reading this in the middle of a search with a fully dormant network, don't be too hard on yourself, since that has described most of us at some point (certainly me). The triage version works better than you'd fear: list the ten people you most enjoyed working with, and send each of them the honest reconnection note above. People are reliably more generous than the anxious version of you predicts, and most of them remember exactly how stressful searching is.

If this article produces exactly one action, I'd make it small: today, send one honest note to one former coworker you liked, with no agenda beyond the note itself. A congratulations, a real comment on something they made, a check-in. That's the entire system, run once, and the compounding starts from there.