Balkrishna Attal

Blog / Careers & Resumes

Careers & ResumesSeptember 5, 2026·5 min read

Why Most PM Resumes Get Rejected in 6 Seconds

You've probably heard the six-second-scan number before. Whether it's exactly six or closer to fifteen, the shape of the problem is the same, and most product management resumes lose it in the first two lines.

— views

I read a lot of product management resumes — as a hiring manager, and now as the person people send them to before an interview. The same handful of mistakes show up constantly, often on resumes that belong to genuinely capable people. The resume just doesn't say so yet.

Mistake 1: Responsibilities instead of outcomes

"Responsible for the onboarding flow and worked with design and engineering to ship improvements." This tells a reader what your job was, not what happened because of you. Compare it to: "Redesigned onboarding's first screen; activation rose from 34% to 41% over one quarter." Same person, same work, completely different resume.

Mistake 2: No numbers anywhere

Not every number needs to be a dramatic percentage. "Ran weekly user interviews with 6-8 customers for four months" is a number. "Managed a backlog of 40+ items across three squads" is a number. Numbers are how a stranger calibrates scope in five seconds, without needing to ask you a clarifying question first — and in a six-second scan, there's no time for a clarifying question.

Mistake 3: Leading with the feature, not the impact

"Launched a referral program" is a feature. "Launched a referral program that became 18% of new signups within two months" is impact. The feature is the least interesting part of the sentence to a reader who's evaluating fifty resumes this week — everyone launched something. Fewer people can say what happened next.

Mistake 4: A generic summary line at the top

"Results-driven product manager with a passion for building innovative solutions." I'd guess a third of the resumes I read open with some close variant of this sentence. It says nothing a hiring manager can act on, and it spends your most valuable six seconds saying it.

A real rewrite, start to finish

Before: "Managed the checkout experience for an e-commerce app. Worked cross-functionally to improve conversion."

After: "Owned checkout for a 2M-user e-commerce app. Identified a drop-off point in address entry tied to one autofill bug, fixed it, and lifted checkout completion by 3.4 points — worth roughly ₹40L in recovered monthly revenue."

Both describe the same six weeks of work. Only one of them survives a six-second scan and makes it to the pile that gets read properly.

The first thing I actually look for

Before I read a single bullet point, I look for one clear, specific, numbered outcome in the top third of the resume — something that tells me this person can point at a result and say "that happened because of a decision I made." If I can't find one in the first scan, I go looking for it deliberately, which most recruiters reading fifty resumes in an afternoon simply won't do.

If you already know your resume is probably one of these and you just can't see it clearly anymore because you've stared at it too long — that's exactly the blind spot a second pair of eyes is good for.

Stuck on something like this yourself?

I take on a small number of 1:1 calls, career conversations, and resume reviews each month.

See how we could work together
BA

Balkrishna Attal

A product leader with a background in civil engineering. Writes about product decisions, careers, and moving into product from somewhere else.