Hey Reader,

Welcome back to Guided Growth where we talk about the skills that accelerate your career beyond just writing great code.

This is The Unwritten Rules #1: a 4-part series where I share the career rules that exist but nobody shared them with you.

A reader replied to my newsletter last month.

"200+ applications. 4 months. 6 callbacks. 0 offers. What am I doing wrong?"

From their side they're working hard. 200 applications is a lot of effort.

From my side it looks like noise.

I post a role. 300+ applications land in a week. I have maybe 45 minutes to review them. That's 10-15 seconds per resume.

In that scan, I'm looking for one thing: did this person apply to me or to everyone?

300 applications received

↓ 280 are generic and skipped in seconds

↓ 15 show some relevance

↓ 5 feel tailored

↓ These 5 get my full attention.

How do I spot a generic application? It takes 5 seconds.

❌ "Passionate engineer with 4 years of experience seeking challenging opportunities in a growth-oriented company."

That sentence fits every company on earth. Skipped.

✅ "I noticed your team moved from a monolith to microservices last year. I did the same migration and hit the exact same data consistency wall."

One sentence. Shows you know what we do. Shows you've done something relevant. That's all it takes.

Here's the math most engineers don't think about:

The Sprayer: 200 applications × 5 min each. ~3% callback rate. ~6 callbacks. Zero preparation.

The Sniper: 20 applications × 2 hours each. ~35% callback rate. ~7 callbacks. Fully prepared.

Same number of callbacks. One-tenth the applications. And the interviews go better because you actually know the company.

The harder the market, the more targeted you need to be. Not less.

If this changed how you think about applications, do reply and tell me.

That's The Unwritten Rules #1. Next Thursday: the system design answer I hear every week and why it tells me you've never built a real system.

Thanks,

Abhishek

The Guided Growth