Resume Teardown #79: Senior Growth PM, 75%, Great Metrics Detached From Decisions
This is part of our Resume Teardown series where we score real PM resumes (anonymized) and break down what the evaluation found.
TL;DR: A senior growth PM with a product-focused master's, moving from consumer subscriptions into regulated fintech, scored 75% with a perfect 100% ATS score. The outcomes are strong and specific. Most of them are detached from the named feature, problem, or decision that produced them.
The Resume
Background: Senior IC product manager with a product-management master's from a top US university and a data science bachelor's. Current PM role at a US fintech focused on debt resolution. Previously PM at a consumer health and fitness app, and PM at an early-stage consumer media tech startup. Earlier data analyst role at a global asset management firm. Co-founded an AI data-query chatbot side project and led a business-school consulting engagement for a large US brokerage.
What looked good on the surface:
- Strong, quantified outcomes across every role: 150k customers served, $5M in enrolled debt, 20% trial-to-paid lift, 50% retention increase
- Genuine growth-PM craft: SQL cohort analysis, A/B testing, PRDs, onboarding and upsell experiments tied to conversion
- A real generative AI signal through the chatbot side project, with discovery and external startup validation
- A clean, coherent layout that parses perfectly
Score: 75%
The ATS Score Is 100%. The Resume Still Scored 75%.
This teardown is a useful reminder that ATS readiness and resume quality are not the same thing.
This resume scored a perfect 100% on ATS: clean headers, consistent dates, strong keyword coverage, no parsing issues. It still scored 75% overall, because ATS measures whether a machine can read your resume, not whether a hiring manager is convinced by it.
The gap here is not formatting. It is that the strong outcomes are floating free of the decisions behind them. A recruiter sees impressive numbers but cannot always tell what this PM personally decided to produce them. The verdict names it:
Several strong metrics are detached from a named feature or customer problem, which makes individual product judgment harder to assess.
That is the whole teardown. The numbers are real. The decision layer that would make them yours is thin.
The Core Gap: Metrics Without the Decision
Look at two of the strongest bullets side by side.
"Managed automation improvements that enhanced efficiency of CX teams by 75%, leading to a decrease in operational expenses by making data-driven decisions for optimal user experiences."
A 75% efficiency gain is a great number. But the product intervention is vague. What automation did you ship? What was the workflow before? "Making data-driven decisions for optimal user experiences" is filler that adds words without adding evidence. A hiring manager cannot tell what you built.
"Drove a 50% increase in user retention by analyzing user feedback and app usage data in SQL to inform feature updates."
A 50% retention lift is excellent. But which feature drove it? What did the feedback reveal? What did you prioritize as a result, and how was retention defined? The result is attributed to "feature updates," which is not a decision a hiring manager can evaluate.
The fix pattern:
Before: "Drove a 50% increase in user retention by analyzing user feedback and app usage data in SQL to inform feature updates."
After: "Found that [X%] of churn happened in the first week via usage analysis, prioritized a [specific feature] to close that gap, and lifted 30-day retention 50%."
Same metric. The after version names the insight, the decision, and the retention window. That is the difference between a number and a product story.
The PRD Bullet That Describes the Job, Not the Work
One bullet is pure job description:
"Developed comprehensive PRDs to guide engineering and design teams, ensuring alignment with stakeholder expectations."
Every PM writes PRDs. A bullet that only says you wrote PRDs tells a hiring manager nothing about your judgment. It occupies a line that could show a specific product decision.
Replace it with the PRD that mattered: what feature or problem it covered, the key requirement or trade-off you resolved in it, and what the launch produced. A PRD is only interesting as evidence of the decision it documents.
The same applies to the roadmap bullet in the current role. "Built and prioritized roadmap by collaborating with stakeholders and aligning business goals and KPIs with customer needs" describes the process of roadmapping. It does not name a single thing you chose to prioritize or cut. One concrete prioritization call, with the reasoning, would show more than the whole bullet does now.
The AI Side Project: Strongest Signal, Thinnest Evidence
Because this resume triggered the AI PM signal, the chatbot project is a lever. Right now it is underpowered for AI product roles.
"Spearheaded the roadmap for a GPT-3 enabled Slack chatbot, allowing business users to ask data questions using plain text."
The discovery work behind it is solid: 30 user interviews, an MVP, external startup validation. But the bullets say nothing about the AI product decisions, which is exactly what an AI PM interviewer screens for.
For a plain-text-to-data chatbot, the interesting questions are: how were questions translated into answers, what could users ask and not ask, how did you evaluate whether a response was useful, and what happened when the model answered wrong? Add the evaluation criteria, the scope boundaries, and the failure-case handling. The discovery is already strong. The AI judgment layer is missing.
The Missing Through-Line
There is no summary, and for this candidate that is the costliest omission, because the career spans contexts that do not obviously connect.
Consumer subscriptions, consumer health, early-stage media tech, and now regulated fintech is a wide arc, and without a summary the recruiter has to connect the dots. The verdict says exactly this: the resume makes the reader work to assemble one story.
There is a clean through-line available: a data-led growth PM who moved into regulated fintech. Two lines before the education section stating that positioning, and surfacing the 150k-customer or $5M result immediately, would frame everything below as intentional progression rather than a series of unrelated roles.
One more structural fix: the titles are all "Product Manager," so the scope growth is buried in the bullets. A one-line scope statement under each role (product area, customer, ownership level) would make the seniority progression visible at a glance.
Dimension Scores
Leadership and Impact: 80%
The highest dimension and genuinely strong. Real ownership in the current role (a compliance debt-resolution product serving 150k customers, a launch tied to $5M in enrolled debt) and outcomes spanning retention, conversion, efficiency, and adoption. The gap is the one running through this whole teardown: the metrics are detached from the named feature and decision. Attach the largest outcomes to the problem and the product change behind them.
Experience and Background: 75%
A credible senior IC track with widening product contexts and increasingly material outcomes. The gap is that identical "Product Manager" titles hide the scope progression. Add a scope line per role.
Skills and Tools: 73%
Strong, substantiated PM craft: SQL analysis, cohort definition, A/B testing, PRDs, feedback analysis, roadmap, and GTM. Experimentation evidence is a standout. The gap is the AI evaluation layer on the chatbot project.
Domain Expertise: 72%
Broad exposure across consumer subscription, growth, media tech, and regulated fintech. The current role's compliance and debt-resolution context is the strongest, most specific domain evidence. Pick the domain with the deepest product decisions (regulated fintech is the clear candidate) and position around it rather than presenting all four equally.
ATS Readiness: 100%
A clean sweep, and worth studying as a model.
Pass across the board: Standard section headers (Education, Experience, Projects & Leadership, Skills), consistent month-year dates with Present used correctly, no spelling issues, no scrambled or orphaned text, and strong PM keyword coverage placed inside experience bullets rather than crammed into a skills list.
The keywords found include roadmap, stakeholder, strategy, metrics, prioritization, cross-functional, launch, user research, data-driven, go-to-market, retention, experimentation, requirements, iteration, and trade-offs. This is what good keyword placement looks like: the terms appear because the work is described in PM language, not because they were stuffed into a list.
The lesson: A 100% ATS score means the machine and the recruiter can both read your resume cleanly. It does not mean the content is doing its job. This resume cleared the formatting bar completely, and the remaining 25% is entirely about content: connecting outcomes to decisions.
Key Takeaways
1. A metric without a decision is a number, not a product story. "50% retention increase" and "75% efficiency gain" are strong, but detached from the feature and the insight that drove them, a hiring manager cannot assess your judgment. Attach every major outcome to the problem, the product change, and the reasoning.
2. ATS readiness and resume quality are different things. A perfect ATS score gets you read. It does not get you convinced. Do not mistake clean formatting for a strong resume. This one scored 100% on ATS and still had 25 points of content work left.
3. "Developed PRDs" is a job responsibility, not evidence. Every PM writes PRDs. The interesting part is the decision the PRD documented. Replace responsibility bullets with the specific trade-off you resolved and what the launch produced.
4. For AI roles, discovery is table stakes. The judgment layer is the signal. Interviews, MVP, and validation show you can run a process. How you evaluated answer quality, scoped what users could ask, and handled wrong answers shows you can own an AI product. Add that layer.
5. A wide career arc needs a stated through-line. Four different contexts with no summary makes a recruiter assemble your story, and the risk is they read "unfocused." Name the through-line (data-led growth PM into regulated fintech) and surface your biggest result up top.
The Pattern
This is a "metrics without the decision" resume from a strong senior growth PM.
The outcomes are real, quantified, and span retention, conversion, efficiency, and adoption, which is more than most senior resumes manage. The gap is consistent: the numbers are not attached to the named feature, the customer problem, or the prioritization call that produced them, so a hiring manager cannot fully assess individual product judgment. The fix is not more results. It is connecting the results already here to the decisions behind them, naming a through-line, and deepening the AI evidence. That turns an interested-but-conditional read into a confident senior IC yes.
Score your own resume to see how your product manager resume performs across all four dimensions.