The Engineers You Actually Want Aren't Reading Your Job Post

You posted on LinkedIn, Naukri, and your careers page. You got 300 applications. Maybe 5–10 are worth interviewing. Meanwhile, the engineers you actually want — the ones building interesting things at good companies — didn't apply at all. Here's why, and what to do about it.

Good engineers don't job - hunt the way you think they do

They wait to be found

A strong engineer at a good company gets 10–20 recruiter messages per week on LinkedIn. They don't need to search. Opportunities come to them.

They rely on referrals

When they want to switch, they ask their network. A WhatsApp message to 5 engineer friends surfaces more relevant options than any job board.

They move fast

When a good engineer decides to switch, they're in and out of the market within 2–4 weeks. If your posting has been up for 3 months, the best candidates have already moved on.

What's wrong with your job posting

The requirements list is 15 items long

Good engineers read this and think either "they don't know what they actually need" or "they're looking for a unicorn." List 3–5 must-haves and 2–3 nice-to-haves.

The description is about the company, not the work

"[Company] is a fast-growing, innovative company backed by top-tier VCs..." Nobody cares at this stage. What they want to know: What will I build? What problems will I solve? Who will I work with? What's the scale?

"You'll own the payment processing pipeline that handles 2M transactions/day. Your first project will be migrating from a monolith to event-driven microservices. You'll work directly with the VP of Engineering and a team of 6 engineers." That's a job description that makes someone stop scrolling.

The salary isn't listed

60–70% of serious candidates won't apply to a posting without a salary range. They've been burned before - spending a week on interviews only to discover the budget is 15L below their expectation.

The posting sounds like every other posting

"We're looking for a passionate, self-motivated engineer who thrives in a fast-paced environment." Every startup in India has posted some version of this sentence. It says nothing.

What to do instead

1. Write the role description as if you're explaining it to a friend

"We need someone to rebuild our search infrastructure. Right now, it's powered by Elasticsearch, and it works okay for 100K products, but we're scaling to 10M, and it's falling apart. You'd own this end to end."

2. Lead with the problem, not the requirements

Describe the challenge. The right technologies should be obvious from the problem. And if a candidate has the right skills but uses a different stack, you probably want them anyway.

3. Have your engineers post about the role

A LinkedIn post from your lead engineer saying "here's what we're working on and why it's interesting" will attract more qualified candidates than a corporate job posting. Engineers trust other engineers.

4. Use recruiters for passive talent

The best candidates are passive - they're not looking, but they'd move for the right opportunity. Reaching them requires direct outreach, usually through a recruiter or network introduction.

5. Respond quickly to applicants

If a strong candidate does apply, respond within 24–48 hours. Every day of delay increases the chance that they get scooped by someone else.

The mindset shift

Stop thinking of hiring as "post a job and wait for applicants." For startups and mid-size companies, hiring is an active, outbound process. The job posting is a billboard. It helps with awareness. But it's not your hiring strategy.