The Passive Candidate Playbook

Most senior engineers have the same quiet arrangement with themselves: I'm not looking, but I'd move for the right thing.

The problem is that "the right thing" is unpredictable. It opens on a Tuesday with no announcement. It fills in two weeks. And if you find out about it through LinkedIn three weeks after it posted, you're already behind twenty people who applied on day one.

This is the passive candidate's core problem: you can't be first in line for a role you don't know exists.

The playbook below is about solving that problem systematically — without becoming an active job seeker, without recruiters in your inbox, and without spending time on things that don't matter.

Step 1: Build your shortlist before you need it

Most people only start thinking seriously about where they'd want to work when they're already unhappy somewhere. That's backwards.

Build your shortlist now — the 10 to 20 companies you'd actually consider leaving for. Not the ones you'd be fine with. The ones where, if you got a call tomorrow saying "we have a role that's a fit," you'd feel a genuine pull.

Be honest with yourself about this list. A lot of engineers put companies on a mental shortlist that are more about prestige than actual fit. That's fine as data, but separate "would genuinely want to work there" from "would look good on a resume."

Your shortlist should include:

• Companies whose product you actually use or care about
• Teams whose engineering culture you respect (engineering blogs, conference talks, open source work are all signals)
• Companies at a stage that matches what you want — early-stage if you want to build, later-stage if you want scale problems and resources

Once you have the list, write it down somewhere. The act of making it concrete is important.

Step 2: Know their hiring patterns

Every company on your list has a rhythm. Most people never bother to learn it.

High-growth startups that just raised a Series B or C will go on a hiring surge for 6–12 months post-funding. Enterprise companies hire heavily in Q1 before headcount freezes kick in later in the year. Consumer companies often pause hiring in summer. Frontier AI companies like Anthropic and OpenAI are hiring continuously right now because the category is expanding faster than the talent pool.

None of this is secret information. Funding rounds are public. Headcount growth is visible on LinkedIn. You can tell a lot about a company's hiring tempo just by watching how often they post new roles over a few months.

The implication: when a company on your list raises a round or announces a major expansion, that's a signal. Something will open soon. If you're paying attention, you have a head start.

Step 3: Set up your alert infrastructure

This is the part most passive candidates skip entirely, then regret.

The average senior engineering role at a company like Stripe, Linear, or Anthropic fills in 10 to 14 days. The best candidates — the ones who did a referral prep call, polished their materials, and thought about why they wanted the role — applied in the first 48 to 72 hours.

That's not because they were lucky. It's because they had alerts set up.

What this looks like in practice:

• Follow the companies you care about directly on their ATS (Greenhouse, Lever, Ashby) so you see roles before they syndicate to aggregators
• Set up notifications for specific role titles at specific companies — not "engineering roles generally"
• Check in on your shortlist companies at least every couple of weeks, even without explicit alerts

The alert infrastructure isn't about being obsessive. It's about converting a passive preference ("I'd move for the right thing") into an actual system that gives you a fair shot when that thing appears.

Step 4: Keep your materials at 80%

Here's what kills passive candidates: the role opens, they want to apply, but their resume hasn't been updated in 18 months, they can't remember what they actually built at their last company, and they need two weeks to prepare — by which time the pipeline is full.

You don't need polished, interview-ready materials at all times. But you need them at 80%.

That means:

• A resume that reflects your current role accurately (update it when your scope changes, not when you're leaving)
• A rough sense of your strongest recent projects and the measurable impact of each
• A clear answer to "why are you interested in us" for each company on your shortlist — this should be specific enough that it couldn't apply to any other company

That last one is the hardest and most important. Passive candidates often have vague reasons ("I've always admired what you're building"), which read as exactly that — vague. The candidates who move fast in a pipeline are the ones who can say, specifically, why this company at this moment.

Step 5: Respond within 24 hours

When a role opens at a company you've been watching, move fast. Not in a desperate way — in a prepared way.

Recruiters at desirable companies often reach out to preferred candidates directly before the role is even posted publicly. If you've done the work above — followed the company, maybe engaged with their engineering blog, perhaps even done an informational call with someone there — you're more likely to be on that early list.

When you do reach out or apply, don't treat it like most of your job applications. Write a short cover note that shows you've been paying attention to the company. Mention something specific — a technical decision they made, a product direction you've been following, a problem you know they're working on. This is where the "watching before you need to" phase pays off.

---

The compounding effect

The thing that makes this playbook work over time is that it compounds.

The companies you're watching now, you'll understand better in six months. The relationships you build passively — following someone's engineering blog, engaging thoughtfully in a community where their engineers are active — create surface area for opportunities to find you.

The passive candidate who does this well doesn't feel passive at all when the right role appears. They feel prepared.

That's the difference between "I wish I'd heard about this sooner" and "I applied on day two, moved through the pipeline fast, and had an offer before most people knew the role existed."

---

Crush is built for exactly this: follow the companies you'd actually leave for, set your role criteria once, and get one alert the moment a match opens — directly from the company's ATS, before it hits the aggregators.

Set up your watchlist on Crush →