CV and ATS guide for product managers
A hiring manager wants the product, the user, and what changed after you shipped. “Owned roadmap” without a result is a skip.
Common ATS gaps
- JD wants a domain (payments, health, B2B SaaS) that never appears in a role title or bullet.
- Tools (Jira, Amplitude, SQL) only in a graphic or icon row.
- No collaboration nouns the JD uses (discovery, PRD, experiment) even when the work is there.
Keywords that only count with proof
Write the domain and the artefact: discovery, spec, launch, experiment. Add SQL or analytics only if you queried or briefed from it.
Common questions
- How long should a PM CV be?
- One page for early PM; two if you have multiple shipped products with distinct outcomes. Cut strategy essays — keep launches.
- Should I use AI to write my PM resume?
- Use it to tighten verbs and order. Do not let it invent “led 0→1” or a TAM figure you cannot defend in the interview.