Networking for engineers who hate networking

I've watched a thousand engineers cringe at the word "networking." Including me, for years. The image it conjures — a hotel ballroom, business cards, "what do you do?" exchanged with strangers in a forced loop — is the version of networking that almost nobody actually does and almost nobody benefits from.

The version that works is something different. Quieter. More compounding. Mostly compatible with introversion.

The networking that doesn't work#

For the avoidance of doubt: this article is not about:

LinkedIn cold messages saying "I'd love to connect."
Meetup events where you collect business cards.
"Quick coffee?" requests to senior people you don't know.
Conference receptions with name tags.
Anything that requires you to perform extroversion.

These activities are not pointless — extroverts get real value from them — but they're not the leverage for most engineers.

The networking that works#

The mental model: a professional network is the by-product of being useful in public for years, not the result of explicit "networking" effort.

The compounding inputs:

Publish things people read. Blog posts, OSS projects, talks (even small ones), thoughtful comments. Your work creating value beyond your job pulls people toward you.
Help individuals one at a time. Answer specific questions thoughtfully. Review someone's PR. Explain something they were stuck on.
Show up consistently in the communities you care about. Same Slack/Discord, same conferences (the ones you genuinely enjoy), same online spaces, over years.
Stay in light-touch contact with people you've worked with. A "hey, congrats on the promotion" once a year is not weird; it's how relationships persist.
Be findable. Bio, blog, real photo, clear story of "this is who I am, this is what I do." See LinkedIn and GitHub articles.

You'll notice none of these involve standing in a ballroom.

The asymmetry of asks#

Cold-emailing strangers asking for help has a low success rate. Cold-emailing strangers offering help has a much higher one.

Specific patterns:

"I noticed your project X has issue Y. I have an idea for a fix; want me to send a PR?"
"I read your post on Z and I have a question about how it interacts with [related thing]. Have you written about that?"
"I'm starting to work on [problem you've solved] and your blog was a huge help. What would you watch out for in this specific scenario?"

Each of these is an opener. Each is also the start of a real exchange. Cold "let's connect" messages are not.

Specific moves for introverts#

These are the ones I actually use:

Async > sync. A thoughtful Slack reply to someone's question can do more for a relationship than a 30-minute call. Asynchronous communication is where introverts shine.

Pre-commit to one event per year. Pick one conference, attendee or speaker, that aligns with your interests. Go, talk to 3 people you'd like to know better, leave when you're tired. One event a year is sustainable; one a month isn't.

Maintain a tiny "people I find interesting" list. 10-30 people. Not "important" people. Just engineers whose work you admire. Read their stuff. Comment occasionally with substance. Years pass and a couple become real friends.

Reply to internet strangers' good takes. Thoughtful, specific replies on Twitter / Bluesky / Mastodon / blog comments are how you become known by people you've never met. Half my industry friends started this way.

Help juniors specifically. When a junior engineer DMs you a question, answer it well. Some of those juniors become directors a decade later. The math works out even if you do it for the right reasons.

Run a tiny Discord/Slack/group. 10-50 people who care about a niche. Hosting beats attending.

The "network" you build#

After 5-10 years of the above, you'll have:

5-10 people you'd be comfortable asking for a real favor (job intro, technical advice, opinion on a hard decision).
30-100 people you've worked with directly, who'd take your call.
500-2000 people who've read enough of your work to recognize your name.

That's a network. Not a Rolodex. A shared context with people who know you exist and have had at least one positive interaction with you.

You don't get there by going to networking events. You get there by being good and being public.

Specific situations#

You want to leave your current job. Tell 3-5 people in your network 2-3 months before you start interviewing. Not "I'm desperate." Just "I'm starting to look around. If you hear of something interesting in [specific area], I'd appreciate the heads-up." Most jobs find people via this exact channel.

You want to start a company / freelance / change paths. The network you've built over years is the seed. Tell people what you're doing; some will hire you, some will refer customers, some will introduce you to investors. None of this works if you didn't already have the network.

You're stuck on a technical problem nobody at work has seen. Post it publicly. Ask in the relevant Discord/Slack. Often the answer comes from someone you don't know who has solved exactly this. Your past being-public-in-the-community made the response possible.

You want to mentor / be mentored. Identify the person you'd want to learn from. Engage with their work substantively over months. When the relationship has weight, the ask becomes natural. Don't lead with the ask.

What "networking" doesn't fix#

A few things worth being honest about:

A bad reputation is unfixable by networking. If you've been known as the engineer who ships broken code, no amount of LinkedIn presence saves you.
A weak public presence (no blog, no GitHub, no LinkedIn) makes networking output-bound on luck. Fix that first.
Networking doesn't replace doing the work. It compounds the work.

You need substance. Networking helps the substance be visible.

A starting playbook for "I have no network"#

If you're starting from zero — early career, recently moved countries, recently switched fields:

Pick 2-3 communities. Not 10. Show up in each.
Comment, contribute, help others. Build a few months of "they recognize my name" before introducing yourself.
Publish something useful. A blog post, an OSS contribution, a thoughtful comment thread.
DM 3 people who've been useful to you. Specific thanks, no ask.
Repeat for a year.

By the end of year 1 you'll have a small but real network. By year 3, something useful. By year 10, the network does work for you you don't see.

The compounding is the point. The networking events are not.