Resume Teardown #74: Data-Led Growth PM, 75% Score, Strong Metrics Missing Their Story
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 PM with 3 years of full-time product experience across consumer subscriptions, health and fitness tech, and regulated debt-resolution fintech scored 75%. The outcomes are strong: 150k customers, $5M in enrolled debt, 20% trial-to-paid conversion lift, 7% premium conversion via SQL-defined cohorts. The gap is that the resume surfaces the numbers without the decisions behind them, which makes a hiring manager interested but uncertain about scope and judgment.
The Resume
Background: Product Manager at a regulated fintech company focused on debt resolution. Previously Product Manager at a consumer health and fitness app. Before that, Product Manager at an early-stage consumer media tech startup. Earlier Data Analyst role at a major global asset management firm. Master of Information Management and Systems from a top university. B.S. in Informatics from a top university.
What looked good on the surface:
- Real outcomes across retention, conversion, operational efficiency, and customer scale: 150k customers, $5M enrolled debt, 3% retention increase, 20% upsell conversion lift
- SQL and data analysis used directly in product decisions, not just listed as a skill
- A/B testing connected to measurable conversion results across two separate roles
- AI product signal via a GPT-3 Slack chatbot project with discovery, MVP, and external validation
- ATS score 100% — clean formatting, strong keyword placement, no parsing issues
Score: 75%
What the Score Reflects
75% for a senior PM with 3 years of full-time product experience is a good baseline. The hiring manager verdict reflects genuine interest with conditions: the outcomes stand out, but the resume makes the reader work to understand decision scope and individual judgment. That gap is entirely closeable without changing a single experience on the resume.
The scoring found one clear pattern across all four dimensions: the metrics are present, but they are detached from the product decisions that produced them.
The Metrics-Without-Decisions Pattern
The most valuable outcomes on this resume are real and meaningful. But they are framed as results that happened, not as results this PM caused through a specific decision.
Look at the most important bullet in the current role:
"Increased customer retention by 3% and drove $5M in new debt enrolled within 3 months of launching a new service that provided clients with legal protection against creditors."
Two strong numbers and a meaningful context. But a hiring manager reads this and immediately asks: what made this a product decision rather than a feature request? What was the trade-off? Who did you have to convince? What did you learn during those 3 months that you didn't expect?
The bullet answers what. It does not answer why or how.
Here is the same bullet with the decision layer added:
Before: "Increased customer retention by 3% and drove $5M in new debt enrolled within 3 months of launching a new service that provided clients with legal protection against creditors."
After: "Identified legal protection against creditors as the top drop-off reason through support ticket analysis, prioritized it over two competing roadmap items, and shipped in 3 months — driving $5M in new enrolled debt and a 3% retention improvement."
Same outcomes. The second version shows the diagnostic work, the prioritization call, and the result. Now the hiring manager can assess judgment, not just output.
The Strongest Section: MyFitnessPal
The health and fitness app role has the most structurally complete bullets on the resume, and they show what the rest of the document should do.
"Leveraged SQL to analyze customer data and redefined user cohorts for marketing campaigns that drove a 7% increase in premium version conversions."
This is a good PM bullet. Tool (SQL) → method (cohort redefinition) → outcome (7% premium conversion). The causal chain is visible. A recruiter can follow how the PM's specific contribution produced the result.
"Built A/B tests for premium upsell messaging, reaching 10k new users and increasing trial-to-paid conversion rates by 20%."
Also strong. What was tested, the reach, and the result. Clean and credible.
These two bullets are the model. The current role has better outcomes but weaker framing. Applying the health and fitness app's causal structure to the current role's numbers would close most of the gap.
The Three Bullets That Need Surgery
Bullet 1: The roadmap bullet
"Built and prioritized roadmap by collaborating with stakeholders and aligning business goals and KPIs with customer needs."
This describes a process, not a decision. Every PM builds and prioritizes a roadmap. What makes this PM's roadmap work distinctive? What did they choose to sequence? What did they push out and why? What KPI movement resulted?
Replace with a specific prioritization call: what was the competing option, what evidence drove the choice, what happened as a result.
Bullet 2: The CX efficiency bullet
"Managed automation improvements that enhanced efficiency of CX teams by 75%, leading to a decrease in operational expenses."
75% efficiency improvement is a compelling number. But "automation improvements" is vague enough to describe anything from a Zapier workflow to a custom ML pipeline. Name the specific automation capability you shipped (workflow routing, document processing, status update automation), quantify the expense reduction if available, and separate the operational claim from the user experience claim, which are different things.
Bullet 3: The PRD bullet
"Developed comprehensive PRDs to guide engineering and design teams, ensuring alignment with stakeholder expectations."
This is a job description bullet. It says you do a PM thing that all PMs do. Replace it with the feature or problem the PRD covered, the key trade-off or constraint you resolved in the spec, and the launch outcome. The PRD is the method. The feature decision and its result are the story.
The AI Bullet: Close But Not There
The DashQueries GPT-3 chatbot project is a genuinely interesting signal. A generative AI product built with user discovery, MVP definition, and external startup validation is substantively different from "familiar with LLMs."
But the bullet stops before the interesting part:
"Spearheaded the roadmap for a GPT-3 enabled Slack chatbot, allowing business users to ask data questions using plain text."
What a hiring manager wants to know: How did you handle bad answers? What could the chatbot not do, and how did you decide where to draw that boundary? What happened when a user asked something the model could not reliably answer? Did you measure answer quality? What did you learn about model behavior that surprised you?
AI product judgment is not about knowing that LLMs exist. It is about showing you understand the failure modes, made deliberate scope decisions, and built with the model's limitations in mind rather than around its best-case behavior. One sentence about evaluation criteria or quality constraints would turn this into a credible AI PM signal.
The Missing Summary
This resume has no professional summary, and at the senior IC level that is a meaningful gap.
The resume currently requires a recruiter to piece together the through-line: data analyst background, early-stage consumer startup, health and fitness growth PM, now regulated fintech. Those contexts are coherent and actually tell a strong story — data-grounded PM who has built in both consumer growth and regulated products. But that story is not stated anywhere; it has to be inferred.
A two to three sentence summary at the top would do three things: position the through-line explicitly, surface the most credible outcome (150k customers or $5M enrolled debt) before the recruiter has scrolled anywhere, and tell a hiring manager immediately where to categorize this candidate.
Dimension Scores
Leadership and Impact: 80%
The highest dimension and the clearest strength. Meaningful ownership at the current role — a compliance product serving 150k customers, a $5M launch outcome — and cross-functional execution evidence across both PM roles. The gap is that several outcomes are detached from the decision logic behind them, making individual judgment harder to assess from the page alone.
Domain Expertise: 72%
Exposure across consumer subscriptions, health and fitness growth, regulated fintech debt resolution, and a generative AI side project. The breadth is real but the resume does not position one as the primary hiring niche. A recruiter screening for a regulated fintech PM will not immediately recognize this candidate as a fintech specialist; a consumer growth recruiter will have the same problem. The current role's compliance context is the strongest domain evidence — lead with it more explicitly.
Skills and Tools: 73%
The experimentation evidence is strong: onboarding personalization, SQL-defined marketing cohorts, and A/B upsell tests each connected to measurable conversion outcomes. The gap is the AI bullet (covered above) and the fact that tools like Figma and Tableau appear only in the skills list without being anchored to a product decision. Connect at least one more tool to a concrete output.
Experience and Background: 75%
The career arc reads cleanly. Data analyst foundation to consumer startup to growth PM at a recognized health app to regulated fintech. The progression shows widening product contexts and increasingly material business stakes. The one structural gap: all three PM roles use the same "Product Manager" title, so scope progression is visible in bullets but not in role framing. A short scope line under each role (product area, customer type, team size) would make the seniority growth immediately readable.
ATS Readiness: 100%
A clean ATS score across all six checks. Standard headers, recognizable acronyms, consistent date formatting, no parsing issues. Keyword placement is particularly strong because the PM keywords appear in experience bullets and project descriptions, not just the skills section. This resume will rank well in keyword matching.
Key Takeaways
1. Outcomes without decisions are half a bullet. A number tells a recruiter something happened. The decision behind it tells them who caused it and how. For every metric on this resume, add one sentence identifying the problem insight, the product change, or the prioritization call that produced it.
2. Your best bullets already show the pattern. Apply it everywhere. The health and fitness app bullets demonstrate the tool-method-outcome structure. The current role has bigger outcomes but weaker framing. Rewrite the current role's bullets using the same causal structure already present in the earlier role.
3. A professional summary does real work at the senior level. Without one, a recruiter has to construct your positioning from scratch. With one, you control what they see first. Three sentences: your through-line, your most credible outcome, and the type of role you are targeting. That is all it needs to do.
4. AI PM bullets need to show failure-mode judgment, not just familiarity. The chatbot project is a real signal. Make it stronger by adding one detail about how you evaluated answer quality or handled model limitations. That one sentence separates "I built with an LLM" from "I understand what it means to own an AI product."
5. Scope lines under each role make progression visible without changing any bullets. Adding "Compliance debt-resolution product, 150k customers, team of 4 engineers" under the current role title takes two seconds and answers the scope question every recruiter has before they read a single bullet.
The Pattern
This is a "metrics detached from decisions" resume from a PM who clearly has product judgment.
The career includes a 20% upsell conversion lift, a $5M launch outcome, 150k customers, and SQL-driven cohort analysis. These are credible, material results. The resume states them without showing the product thinking behind them, which leaves a hiring manager interested but uncertain.
The fix is not new work. It is adding the "why I made this call" layer to the outcomes that are already there. One sentence of decision context per major bullet would push this from conditional interest to confident phone screen.
Score your own resume to see how your product manager resume performs across all four dimensions.