Visibility, interpretation and timing, not just performance.

Important: After signing up, you'll receive a confirmation email. Your subscription isn't complete until you click "Confirm subscription" in that email. Check your spam.

Jun 22 • 2 min read

Why your resume gets no reply


I applied for a role I'm a good fit for. Why haven't I heard back?

Let’s agree on one thing. Resumes usually get evaluated twice: first by a system, then by a human scanning under time pressure.

When your positioning and fit are clear, the second stage is usually the real bottleneck.

A recruiter is not reading your resume completely. They are scanning for signals that make your level and impact obvious in seconds. Everything else becomes noise.


Let me share a case from last year

Someone reached out after being rejected at application stage from a big tech company. She had 3.5 years of experience, strong company names, and solid technical work. Nothing about her background was weak.

The problem was what her resume emphasized. It leaned toward participation: code reviews, oncall, mentoring teammates. None of this is wrong, but without outcomes it reads like activity rather than impact.

We rewrote it by removing low signal bullets, clarifying ownership, and turning vague contributions into measurable impact. A few weeks later she reapplied and got a recruiter response with a phone screen.

This is what I mean by signal: what you surface, intentionally or not, that changes how someone evaluates you.


The 6 second test

You’ll read your resume 50 times. A recruiter will read it for ~6-10* seconds before deciding whether to continue.

*commonly cited in hiring research

A useful test: look at your resume for 6 seconds. What stands out first?

Readers experience the document as a whole. Your goal is to make the important information impossible to miss, not to fit more on the page.


Fix signal, don’t add content

Put your strongest work first

  • strongest achievements
  • technologies relevant
  • evidence of impact

A good summary tells me who you are and what problems you solve.

Turn activity into ownership

Weak: “Mentored teammates”
Stronger: “Improved team delivery by growing 3 engineers into independent owners”

Same work, different scope implied.

Make numbers meaningful

Bad: “Improved deployment time by 50%”
Better: “Reduced deployment time from 1.5 hours to 45 minutes for 150+ engineers”

The value in numbers is the scale and who benefits.

ATS matters, but only to a point

Consistent structure and role relevant keywords matter for getting through parsing.

Don't over think it though. Modern ATS systems handle common resume formats and layouts well.


Resumes are a positioning exercise

Two engineers with similar experience can look very different because one makes their value easier to interpret.

As seniority increases, what matters changes:

  • less implementation detail
  • more ownership
  • more judgment and tradeoffs

If that is not visible, seniority is not inferred.


AI use

For writing: exercise caution. Useful if it refines, not useful if it replaces thinking. The weakest resumes and outreach messages I see are usually AI-first: full of phrases that sound cool without saying much.

For critiquing: it's high leverage. Ask “What are the 3 weakest signals?” or “What would a recruiter remember after 6 seconds?”


Closing insight

The best resumes are not comprehensive. They’re selective about what is included in the first place.

If I removed 50% of your resume today, which bullets would survive because they change how someone evaluates you, not because they feel safe?

That answer is usually your real candidate profile.


What’s next

Even a strong resume fails if it does not reach the right people.

Next, I’ll go deeper on increasing the chances of being seen in the first place.


Important: After signing up, you'll receive a confirmation email. Your subscription isn't complete until you click "Confirm subscription" in that email. Check your spam.


Read next ...