Your CV didn't get rejected.
It never got read.

This CV tells a story about someone who was in the room when important things happened. It doesn't tell a story about someone who made important things happen. That is the gap between where this application is and where it needs to be.

A hiring manager reviewing CVs for a Head of Product role at a Series B company is looking for evidence of three things: commercial judgment, a shipping track record under real constraint, and leadership that produced measurable outcomes. This CV gestures at all three without demonstrating any of them. “Led the product discovery process” is a task description. “Rebuilt the product discovery process after two failed launches, reducing time-to-decision by 40%” is evidence. You have the former throughout. You need the latter.

The formatting is clean and readable. This CV won't be filtered out on presentation. But formatting has never been the problem. CVs that don't get callbacks aren't failing on layout, they're failing on proof. A hiring manager cannot tell what changed in any of the organisations you worked for because you were there. That is what needs to change before this CV generates interviews.

The competitive context for a Head of Product job search in B2B SaaS right now is brutal. You're not being compared to the average CV. You're being compared to the top 5% of a stack of 80 to 120 applications for a single role. A CV that requires someone to give you the benefit of the doubt has already lost that comparison.

The instincts here are probably sound and the experience is real, but none of that is visible from the outside yet. Hiring managers for senior product roles at funded startups are not hunting for potential. They are filtering for proof. A CV that requires someone to read between the lines and find the real candidate is a CV that ends up in the no pile before the interview stage.

The word “led” appears seven times across this CV. In not one instance does the sentence that follows say what changed as a result. “Led a cross-functional team” — how many people, what did you ship, did it work, what did it cost to get there? “Led the roadmap planning process” — what shipped from that process, what didn't, and why? Leadership without a named outcome attached to it reads as process participation, not ownership. That's the single rewrite this CV needs most.

The most recent role is the biggest problem on this page. It's your freshest and most relevant evidence for a Head of Product application, and it reads like product management in steady state. If there is a real story buried in that role — a difficult call you made, a direction you changed, a launch that mattered commercially — it needs to be written down. Not saved for the interview. A CV that makes someone curious enough to invite you to an interview has already done half the job.

One structural observation: there is no competitive or market framing anywhere on this CV. A senior product leader is expected to understand the space they're operating in, not just the product. One sentence per role that contextualises the market (who you were competing with, what the product category looked like, where you sat in it) would change how this CV reads at a senior level.