Why the Best Engineers Aren't on LinkedIn

Here's something counterintuitive: the engineers who companies most want to hire are the ones who are hardest to find. They're not refreshing job boards. They're not updating their LinkedIn headline to "Open to Opportunities." They're not responding to recruiter cold messages about "exciting roles at stealth-mode startups."

They're just... building things. And somehow, they still land at Stripe, Figma, or wherever they actually want to go.

This isn't an accident. It's a structural feature of how senior technical hiring actually works — and if you understand it, you can position yourself on the right side of it.

The Signal Problem

LinkedIn's fundamental problem for senior engineers isn't the spam (though the spam is genuinely awful). It's that activity on the platform sends the wrong signal.

When a senior engineer updates their profile to "open to work" or starts liking posts about engineering culture at Big Tech companies, they're broadcasting availability. And availability at the senior level is a mild yellow flag. The implicit question in every recruiter's head: if they're this good, why are they looking?

This is unfair. People leave jobs for completely legitimate reasons — bad management, stagnant growth, company direction, life changes. But the perception exists, and the best recruiters — the ones with the most interesting roles — operate on it. They don't wait for signals of availability. They go find the people who aren't looking.

So the platforms optimized for "I'm looking" end up surfacing a self-selected pool that skews toward people who are motivated to leave rather than people who are great at the job.

Where Senior Roles Actually Get Filled

The hiring funnel for a Staff Engineer or Principal PM role at a high-signal company looks nothing like what most people assume. It usually goes something like this:

Internal referrals first. Hiring managers ask their best engineers: who's the best person you've ever worked with? Do they have anyone from a previous company they'd love to work with again? These conversations happen before a job posting goes live, often before the req is even officially open.

Targeted sourcing from existing networks. Recruiters at the top companies don't search LinkedIn. They search GitHub commit history, conference speaker lists, open source project maintainers, Substack authors in technical niches, Discord server regulars. They're looking for demonstrated expertise in public, not self-reported skills in a profile.

Community reputation. In any technical niche — distributed systems, developer tooling, ML infrastructure, design systems — there's a relatively small community of people who know each other. If you've made meaningful contributions to that community, word gets around. Companies send messages to people they've been watching for months.

The job posts externally as a formality. By the time a role hits LinkedIn, there's often already a preferred candidate in the pipeline. The public posting is due diligence, not discovery.

This doesn't mean LinkedIn is useless. It's how you get found for mid-level roles at companies you've never heard of. For senior positions at the places worth taking seriously, you need a different approach.

The Paradox of Passive Candidacy

Here's where it gets interesting. The engineers who successfully land at their dream companies without job searching aren't entirely passive — they're just investing their energy differently.

They write about problems they've solved, in enough detail that other people working on the same problems find it useful. They contribute to open source projects that are dependencies for companies they'd want to work at. They speak at smaller, higher-signal conferences rather than broadcasting on general platforms. They're visible to the right people, not visible to everyone.

The goal isn't to get found by recruiters. It's to become the person that the hiring manager at your target company already knows by name before they open a req.

This takes longer. It doesn't produce immediate results. But it compounds in a way that LinkedIn activity never does. A blog post that becomes a reference for solving a hard distributed systems problem will get you calls from companies for years. A LinkedIn post about your professional values will generate recruiter spam for a week.

What This Means for Positioning

If you're a senior engineer who would entertain a move to one or two specific companies under the right circumstances — which describes most senior ICs who are intellectually honest with themselves — the question to ask is: am I visible to those companies specifically?

Not globally visible. Specifically visible to the people making hiring decisions at the companies on your shortlist.

A few things that actually move the needle:

Public work that's relevant to their problems. Write about the specific technical challenges your target company faces. If you want to work at a developer tools company, write about developer experience. If you're targeting a data infrastructure company, write about the paper you read on columnar storage. Be genuinely useful, not performatively visible.

Direct engagement with their community. Most companies worth working at have open communities — GitHub discussions, Discord servers, office hours, podcasts where engineers from the company talk about what they're building. Be a thoughtful presence there. Not in a sycophantic way. In the way that demonstrates you understand the problem space.

Internal advocates. The most reliable path is still someone inside the company who thinks of you when the role opens. Maintaining relationships with people you've worked with — even loosely, even just staying in touch quarterly — is worth more than any amount of profile optimization.

The watchlist posture. Senior engineers who successfully navigate passive candidacy don't apply to jobs. They stay informed about what companies are actually hiring for, so that when the right role opens at the right company, they can move quickly. Not because they were on the job market, but because they were paying attention.

The ATS Problem

Here's a wrinkle that most people miss: even when a dream company opens the exact right role, you might not hear about it. Not because you're not qualified. Because job postings are transient, the ATS buries applications from people who weren't already in the pipeline, and the role might be filled in three weeks.

LinkedIn is particularly bad at this. The platform is optimized for engagement, not for surfaces that help you track specific companies you care about. You can "follow" companies, but the signal is buried in noise.

The engineers who successfully navigate passive candidacy have some kind of systematic way to stay informed about hiring activity at their shortlist of companies — whether that's personal relationships inside those companies, industry newsletters that cover hiring moves, or tools that watch ATS systems directly.

The goal is to compress the time between "role opens" and "you know about it" to as close to zero as possible. That's the actual competitive advantage in senior hiring. Not being found. Being ready.

---

Crush watches the applicant tracking systems of the companies on your list — not LinkedIn job posts, which lag by days or weeks and often recycle old listings. When your target company opens a role that matches what you're looking for, you hear about it the same day. No spam, no noise, just the signal you actually wanted.

Set up your watchlist on Crush