The Network That Actually Opens Doors

---

Let me tell you about the job I didn't get because I didn't have a network, and then the job I did get because I did.

Early in my career, I was a strong engineer by most measures. I was shipping quality code, getting good performance reviews, building systems I was proud of. But my professional world was essentially the forty people in my office. When I started looking for my next role, I did it the way most engineers do: updated my resume, sent it through job portals, waited. I got a few interviews. I got some offers. I took what looked best on paper without any real understanding of the culture, the engineering quality, the trajectory of the team. It was fine. But it was blind.

A few years later, I'd spent time genuinely building relationships in the engineering community in my city — going to meetups consistently, writing about what I was learning, helping other engineers when they got stuck on things I knew. When I was ready to move, I didn't send a resume to a stranger. A friend mentioned my name to an engineering director she respected. That director had already read things I'd written. The conversation we had when he reached out was substantively different from a cold interview. Within two conversations, I had a level of mutual understanding with him that most candidates spend six rounds of interviews trying to build from scratch.

This is the difference a real network makes. Not that someone will hand you a job. But that the information quality around your decisions improves dramatically, the opportunities that reach you are better filtered toward what you're actually looking for, and the people evaluating you already have a basis for judgment that a resume cannot provide.

The Transactional vs. Structural Network

The most common networking advice engineers receive is transactional: attend events, collect contacts, follow up, stay visible. This advice produces a transactional network — one where you are primarily thinking about what you might get and other people are primarily sensing that dynamic.

A transactional network of two thousand LinkedIn connections is nearly worthless for the things that matter most in a career. When you're trying to decide whether to take a job at a company, knowing someone who actually worked there and will give you an unvarnished account of the engineering culture is enormously more valuable than having any number of first-degree connections at that company who are essentially strangers. When you're trying to work through a hard architectural decision, a single phone call with someone whose technical judgment you genuinely trust is worth more than a thousand replies in a technical forum.

What you're building when you're building a real network is not a collection of contacts. It's a set of relationships where genuine mutual respect and interest exists. Where you know enough about someone's thinking that you can weight their opinion appropriately. Where they know enough about you that when they say "you should talk to Ruchit about this," it carries real signal.

The structural network — the one that's actually useful — is built not through networking events but through showing up consistently in the same community over time, doing work that people can see and evaluate, being genuinely helpful when someone has a problem you can address, and having conversations that are actually interesting rather than instrumentally motivated.

Why "Who You Know" Is Not a Dirty Phrase

A lot of engineers — particularly in India, where there's a cultural tendency to believe that merit should speak for itself — resist the idea that professional relationships matter. The belief is: if you're good enough, opportunities will find you; if you need connections, you're compensating for lack of skill.

This is a comforting story that the data doesn't support.

In over a thousand interviews, I've consistently seen that referred candidates perform substantially differently in process — not because they're smarter, but because they arrive with more context, they've been pre-screened by someone whose judgment the company trusts, and they're already motivated in a way that cold-apply candidates often aren't. This produces better hiring outcomes for the company, which is why referrals remain by far the most reliable hiring channel for almost every engineering organization.

The engineers who understand this aren't gaming the system. They're participating in how the system actually works. The ones who insist on purity — that their work alone should speak — often find themselves in a world where their excellent work is being done in invisible contexts that nobody outside their immediate team can see.

Beyond jobs: the most valuable career information — what it's actually like to work at a specific company at a specific stage, what the engineering culture at that startup will look like in two years given its growth trajectory, which technical domains are genuinely over-hyped versus substantively important — this information travels through trusted relationships, not LinkedIn posts. The engineers who make consistently better career decisions are usually the ones who have more of this inside information.

Building Without Faking It

Here is the tension that stops most engineers from building a real network: they don't want to be fake. They don't want to reach out to people with hidden agendas. They don't want to be seen as someone who's only helpful when they want something.

The good news is that the genuine approach is also the effective one. In fact, the transactional approach is both morally uncomfortable and practically inferior. So you don't have to choose between integrity and effectiveness.

The genuine approach looks like this: find communities organized around problems and ideas you actually care about. Contribute to them without any specific agenda. Be consistently curious about other people's work. When you can help someone with something they're stuck on, help them. When someone else says something interesting, engage with it specifically — not with a generic compliment, but with a real response that shows you understood what was interesting about it.

Over time, this produces relationships with people you genuinely like and respect, who genuinely like and respect you. The career benefits follow from that as a natural consequence, not as a primary motive.

The key word in all of this is consistency. A network isn't built by attending one conference or publishing one article. It's built by showing up in a community repeatedly over years. People trust people they keep seeing. The engineer who has been coming to the same Bangalore infrastructure meetup for three years and who everyone recognizes — that engineer has built something real. The engineer who shows up when they're job hunting has not.

The Personal Board of Advisors

One specific structure I recommend to every engineer I mentor: build a personal board of advisors. Not a formal thing with titles — just three to five people across different career stages and contexts who you actively maintain relationships with and who will give you honest feedback when you need it.

The composition matters. You want someone who is roughly where you want to be in ten years — someone who has lived the fork you're approaching and can tell you what it actually looks like. You want someone who has managed people and can give you an informed outside view of how you're developing as a leader. You want someone who is at a very different kind of company than your current one — if you're at a services company, someone from a product company; if you're in India, someone who has worked internationally. You want at least one person who will tell you when you're wrong, not just when you're right.

The maintenance rhythm doesn't need to be elaborate. A meaningful conversation every few months, not just a "staying in touch" ping. The conversation has to be substantive enough that both people get something from it — that's what makes it mutual rather than extractive.

For a lot of engineers in India, the instinct is to look only within their college alumni network for this kind of relationship. The IIT and NIT networks are real and genuinely valuable — the shared experience creates a base of trust that's hard to replicate. But anchoring exclusively to college networks limits you in two ways: it creates an echo chamber of people with similar backgrounds and similar career trajectories, and it means you miss the perspectives that come from genuinely different paths. Your board of advisors should have at least one person who is nothing like you professionally.

The Community Play

Beyond individual relationships, there is significant value in identifying one or two communities where you consistently show up and contribute — not as a consumer, but as a participant who adds something.

The mechanism here is reputation at scale. Individual relationships are necessarily limited in number. A community presence means that a much larger group of people have a basis for knowing who you are and what you're about, without requiring one-on-one relationship time with each of them.

In 2026, the most substantively valuable engineering communities I've seen are organized around specific technical domains with a culture of deep engagement — not broad "tech" communities, but the groups of people who go deep on distributed systems, or database internals, or AI reliability engineering, or security architecture. These communities are usually smaller than the large tech Twitter conversations, and the relationships formed in them are proportionally more real.

Writing is one of the highest-leverage community contributions. A well-argued technical article that explains something clearly — that takes a hard concept and makes it accessible, or that presents a non-obvious perspective on a common problem — travels widely and establishes credibility with people you'll never meet directly. The engineers who write regularly and well have a surface area of reputation that is disproportionate to the effort.

Open source contribution, where it's genuine — where you're actually using a project and have something real to contribute, not submitting documentation fixes for exposure — is another. But it's genuinely valuable only when the contribution is substantive enough to be noticed by the people whose judgment matters.

Online vs. Offline

A lot of engineers ask whether online or offline relationship-building is more effective. My experience is that they serve different purposes.

Offline — meetups, conferences, local engineering gatherings — is where relationships start most naturally. There's something about physical presence and real-time conversation that creates the initial basis of connection faster than online interaction typically does. In India's major tech cities — Bangalore, Hyderabad, Pune, Delhi NCR — the engineering community is large enough and active enough that consistent offline presence in relevant communities is genuinely productive.

Online is where you can maintain and develop relationships across geographic constraints, and where you can establish a reputation with a much wider audience. The limitation is that online relationships, especially those that never become offline ones, have a ceiling on their depth and trust.

The pattern I've seen work best: build the relationship online through genuine engagement and mutual interest, deepen it through a video call or an in-person meeting at some point, and then maintain it through a combination of both.

A Note on Authenticity and the Long Game

The last thing I want to say about networks is this: they only stay valuable if you keep them real.

The relationship you had with a former colleague that was genuine and warm will fade if you only reach out when you need something. The reputation you built by being genuinely helpful will erode if people start to sense that the helpfulness has become strategic. People have accurate instincts about this.

The engineers who maintain strong networks over decades aren't running a strategic optimization. They're genuinely curious about other people, genuinely interested in seeing their community thrive, genuinely invested in the problems and ideas their community is working on. The career benefits are a byproduct of that investment, not its purpose.

A network built this way is not just professionally useful. It's one of the things that makes a long engineering career worth having — the people you know and respect, who know and respect you, who you've worked through hard problems with and who you'll work through more hard problems with. That's not networking. That's professional community. The difference matters.

In the next chapter, we'll turn to one of the most consequential decisions in that career — one that your network will almost certainly play a role in helping you make well: whether to stay on the IC path or move into engineering management.