A worked example · for the job-seeker

Re-aiming a strong candidate — without rewriting them.

A representative worked example: a composite drawn from real engagements, with every identifying detail changed. It shows the process and the before/after — not a specific person.

The candidate. A space-industry product manager — ~7 years, came up through systems engineering and grew into product, has shipped satellite and ground-segment products end to end. A metrics-dense CV: features delivered, roadmaps run, uptime and adoption numbers, cross-functional teams led.

The role. Senior Product Manager at an Earth-observation analytics company — freshly Series-B funded and pushing its platform into a new commercial vertical (non-space enterprise buyers). The job description leaned on customer discovery, owning commercial outcomes, taking a product from PMF into scale, and translating deep-tech into language a non-technical buyer trusts.

The situation. A strong builder, aimed at the wrong target. The CV read "excellent feature-shipper." The role wanted "owns commercial outcomes." An aim problem, not a substance problem.

The read

Four decision-makers, scored separately.

Before touching the CV, I read the role the way it's actually decided — through the four people in the hiring loop, each weighted by influence.

Who's decidingScoreWhat they were thinking
Hiring manager (VP Product)80"Clearly technical and ships — but show me a commercial outcome they owned, not just a roadmap they ran."
The team (peer PM / eng)84"Speaks engineering fluently, credible — easy yes on respect."
Recruiter / TA80"Solid PM and real space domain — but I'm not seeing the enterprise-SaaS / new-vertical signal."
Senior leadership (CPO)76"Can they take us from PMF into a new vertical, and sell the value to non-space enterprise buyers?"

Composite: 79/100 — strong. The pattern was clean: everyone rated the craft high and flagged the same gap — the commercial half of the story was buried.

The diagnosis

Re-aim, don't rewrite.

The work didn't need fixing. It needed pointing at the right people. Three moves:

  1. Lead with outcomes, not features. The CV opened with engineering depth and delivery — true, but it made them read as a builder, not an owner. Re-order so the adoption, retention, and revenue impact comes first, engineering second, so the VP Product sees "owns commercial results" in the first five seconds.
  2. Surface the discovery work. They had actually run dozens of customer interviews and shaped the roadmap from them — but it was filed under "engineering" language. Relabel it honestly as product discovery / customer development with enterprise buyers — the exact new-vertical signal the company was screening for. No invention; just stop hiding the commercial half of the job they already did.
  3. The one honest tightening. The CV said "led product strategy." The scope they truly owned end-to-end was one product line; the broader strategy they contributed to. A sharp VP Product notices that gap — and if it reads as inflated, it quietly discounts everything else. So lead with the product they genuinely owned 0→1 / PMF→scale (a line they grew from pilot to seven-figure ARR), and present the wider strategy work separately, labelled as "contributed to." Honest — and still strong.
What stayed untouched: the technical credibility, the shipped record, the cross-functional trust, the metrics. The bones were strong. You don't sand down what's already load-bearing.

The output

What they walked away with.

I didn't turn this person into someone else. I helped them see what was already true about their own work — and aim it at the people actually deciding.

That's the whole job: separate the signal from the noise, point it at the truth, and send them in stronger than they came.

Between roles, or aiming at one that matters? Let's re-aim it together.

Start a conversation