Resume Teardown #65: Head of Product in Healthtech, $18M Revenue Scope, 72% Score
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 Head of Product with 8 years across digital health, insurance platforms, and clinical software in India and Indonesia scored 72%. The Halodoc section is the strongest on the resume: 3x insurance growth, $1M+ revenue target exceeded, and a midwife digital health app built for a global health foundation. The current Head of Product role has six bullets covering $18M in revenue and 9 PMs, and almost no outcomes. The resume also has no summary. Both are fixable.
The Resume
Background: Head of Product at a B2B healthtech platform serving corporates with outpatient care benefits (current, 2022-present). Previously Senior Product Manager at a leading digital health marketplace in Indonesia. Before that, Product Manager at a clinical practice management software company. B.Tech in Electronics and Communications from a technical university. 8+ years in product management.
What looked good on the surface:
- Clear progression: PM to Senior PM to Head of Product
- Real organizational scale: 9 PMs managed, $18M revenue scope across 4 platforms
- Quantified outcomes in prior role: 3x insurance growth, $1M+ revenue target exceeded
- Healthcare domain depth across India and Indonesia: insurance, claims, EHR, corporate benefits, digital clinics
- Cross-functional leadership across sales, operations, legal, compliance, finance, and insurer/TPA partners
Score: 72%
The Highest-Leverage Fix: Add a Summary
The resume opens directly with the first job title. No summary. No positioning statement. At Head of Product level, the absence of a summary is the single most costly structural decision on this resume.
A recruiter opening a senior PM resume needs to calibrate within the first 10 seconds: what kind of PM is this, what scale have they operated at, and what have they achieved? When the document goes straight to job titles and bullet points, that calibration happens slowly and incompletely.
At 8 years in healthcare product management — with $18M in revenue scope, a 9-person PM team, and 3x growth at a prior role — there is more than enough material for a two-line summary that immediately signals level and domain.
What the summary should contain:
"Head of Product with 8 years building digital health platforms across India and Indonesia. Managed $18M in annual revenue across 4 product lines and led a team of 9 PMs at a B2B healthtech company. Previously drove 3x growth for a micro health insurance product and exceeded $1M revenue target at Indonesia's leading digital health marketplace."
That summary tells a hiring manager: tenure (8 years), domain (digital health, India and Indonesia), current scope ($18M, 9 PMs), and a signature prior achievement (3x growth, $1M). A recruiter reading this knows within 15 seconds whether to continue. Currently, they have to read three job descriptions to get the same information.
The Current Role: Scope Without Outcomes
The Head of Product role is the most important section on the resume. Six bullets. $18M revenue. 9 PMs managed. And a recruiter still cannot tell what changed because of this person's leadership.
"Driving the Product Charter under the direct supervision of the CPO, managing 4 product platforms that collectively generated $18 million USD in annual revenue for FY2324."
Revenue scope is good context. But "driving the product charter" is a process description. What did the charter produce? What did the company do differently because this PM defined and owned it? Revenue attribution to the platforms is interesting — what specific product decision contributed to that revenue holding or growing?
"Leading and Mentoring a team of 9 PMs focused on developing Consumer Platform, Internal Tools, Claims Management, and Partner Platform."
Team scope is clear. What improved through this leadership? Did delivery cadence improve? Did the team ship more reliably? Were PMs promoted? Did the team structure change? Did a previously blocked platform unblock? Mentoring 9 PMs is significant organizational work. The bullet needs to show what that work produced.
"Leading strategic integrations with top healthcare insurers, TPAs, and corporate benefit platforms in India."
The "Strengths" sidebar is more useful here than this bullet: "Implemented viable strategic integrations with insurers and TPAs resulting in retention of over 80% of the business." That outcome — 80% business retention — belongs in the main experience section, not in a sidebar.
Move it. "Led strategic integrations with insurers and TPAs across the corporate benefits network, retaining over 80% of existing business through seamless claims and benefits connectivity." That one line transforms this bullet from a responsibility statement into a business outcome with a number.
The Halodoc Section: Your Resume's Strongest Evidence
The Indonesia role has the best bullets on this resume:
"Orchestrated the Product Strategy for a Micro Health Insurance product achieving 3x growth in sales and annual revenue target exceeding $1 million."
3x growth and a named revenue milestone. Specific, credible, and domain-relevant. A hiring manager reading this understands the scope and the result.
"Led the Product charter of the first ever digital app for Primary Healthcare Professionals (Midwives) in Indonesia as part of a strategic partnership with a global health foundation."
"First ever" is a strong 0-to-1 claim. A strategic partnership with a recognized global foundation adds external validation. This bullet shows both product ownership and stakeholder complexity in a regulated healthcare environment.
The gap in this section: neither bullet shows the product decision that drove the result. 3x growth on a micro health insurance product — what did you change? Was it pricing, distribution, the benefit structure, the claims workflow, the activation funnel? One additional sentence per bullet would close the "how" that hiring managers will ask about in interviews.
The "Products Handled at CNH Care" Sidebar
The resume includes a separate section listing the four products managed at the current company with short descriptions. This creates two problems:
First, it competes with the experience section for the recruiter's attention. A reader scanning the document is not sure whether to read the experience bullets or the product descriptions first, or whether they overlap.
Second, the product descriptions describe what the products are, not what this PM did with them. "A claims management platform for insurers to settle cashless and reimbursement policy claims" is a product definition. "Launched a claims settlement platform serving 15+ insurers, reducing average settlement turnaround from 7 days to 3 days" is a PM achievement.
The fix: fold the most important product context into the experience bullets directly. One line of product context per initiative, followed by the PM decision and outcome. Remove the sidebar section. The experience bullets should do both jobs.
The EHR Bullet: Incomplete and Potentially Strong
"Leading the development of an Electronic Health Records Platform with an ML based Differential Diagnosis module to recommend relevant Diagnosis to Doctors."
This is potentially the most interesting technical initiative on the resume. An ML-based differential diagnosis module used by doctors inside a corporate health system is a real AI product problem. But the bullet describes the feature, not the outcome.
Who are the users? Doctors at which type of facilities? What problem did clinicians have before this? What did the recommendation module change about their workflow? What accuracy or adoption metric validated the approach?
One additional sentence transforms this from a feature description into a product story: "Shipped an ML-based differential diagnosis module to 200+ doctors across occupational health centers, reducing average diagnosis documentation time by 40% and improving ICD coding consistency for claims submission."
Whether those numbers are right is less important than the structure: user, problem, decision, measurable outcome.
The Skills Section: Generic at Staff+ Level
Skills: Strategic Thinking, Market Research, Product Ideation, User Experience, Agile Development, Product Analytics, Product Life Cycle Management
"Product Ideation" and "Strategic Thinking" are not PM skills. They are traits. At Head of Product level, the skills section should name: what this PM builds, what leadership scope they operate at, what domain they specialize in, and what craft they bring to platform and team decisions.
The existing bullets in the experience section implicitly demonstrate: healthcare platform strategy, insurance product growth, EHR product development, PM team leadership, and cross-functional stakeholder management across legal, compliance, and finance. Those belong in the skills section, not "Product Ideation."
ATS Readiness: 58%
One of the lower scores in the series, with a formatting fail. The resume was built in a visual template (Enhancv, based on the watermark in the source) that does not parse cleanly in ATS systems. The extracted text shows broken symbols, orphaned characters, bullet artifacts, and disrupted line breaks throughout.
This is not a cosmetic issue. ATS systems reading this document may not correctly extract role titles, dates, or bullet content. A hiring manager at a large company who receives this through their ATS may see garbled text rather than clean bullets.
The fix is non-negotiable before any application: export to a plain single-column Word or Google Doc format. Remove sidebar columns, remove the product listing section, remove graphical elements. The content is strong enough to stand without a designed template. An ATS-safe format will let the content do its job.
PM keywords in experience bullets are also weaker than the seniority would imply: discovery, launch, user research, go-to-market, trade-off, adoption, retention, experimentation, requirements, and backlog are all absent or weakly placed in recent bullets.
Dimension Scores
Leadership & Impact: 74% — The weakest dimension relative to the actual scope of the role. The current role has real organizational leadership ($18M revenue, 9 PMs, insurer integrations) but the bullets read as scope rather than impact. The prior Halodoc role is better-evidenced. Rebalancing the current role toward outcomes would move this score meaningfully.
Domain Expertise: 84% — Strong. Healthcare across India and Indonesia, insurance and TPA workflows, claims management, EHR, corporate benefits, and digital health marketplace. Domain language is used naturally and specifically throughout. The gap is one or two domain-specific constraint bullets showing how you navigated compliance, benefit design complexity, or clinical workflow requirements.
Experience & Background: 78% — Coherent progression from PM to Senior PM to Head of Product across credible healthtech companies. The Indonesia experience adds geographic and domain breadth. The gap is the missing summary that ties the arc together for a recruiter scanning quickly.
Skills: 58% — Generic at this level. Traits listed rather than craft. Experience bullets carry more evidence of PM skill than the skills section does. Rebuild the skills section to reflect actual expertise: healthcare platform strategy, insurance product growth, PM team leadership, cross-functional stakeholder alignment across regulated environments.
Key Takeaways
1. At staff+ level, no summary is a structural error. A Head of Product managing $18M in revenue and 9 PMs should be positioned in the first 10 seconds of a recruiter's read. Without a summary, the calibration happens slowly through job descriptions. Two lines would change the first impression of this resume entirely.
2. Your sidebar is hiding your best outcome. "Retained over 80% of business through insurer and TPA integrations" is a significant business impact statement. It is currently in a strengths sidebar. Move it into the main experience section where it will be read.
3. The current role needs outcomes, not just scope. Managing 4 platforms and 9 PMs is impressive context. What improved because of your leadership? What did the team ship that moved a metric? What business problem did the charter address? Two or three outcome bullets in the current role would close the gap between the role's evident importance and its current evidence density.
4. Template design is actively hurting this resume. The visual template that makes the resume look polished on screen is causing ATS parsing failures. Broken characters and orphaned symbols in extracted text mean a hiring manager may see garbled content. Switch to a plain single-column format before any application. The content does not need visual design help — it needs to be readable by machines.
5. The best bullets in the prior role still need a decision layer. 3x growth on the insurance product is a strong outcome. What drove it? The hiring manager will ask this in a screen. Adding one sentence per key metric — what you changed and why — closes the gap between a result and a PM story.
The Pattern
This resume represents the "strong career, current role under-evidenced" archetype. The candidate has genuine Head of Product credentials: $18M revenue scope, multi-platform ownership, PM team leadership, and a prior role with measurable growth outcomes in a complex cross-border healthcare market.
The problem is that the resume's most important section — the current role — reads like a job description instead of an impact statement. A recruiter who reads the Halodoc section sees a PM who drove 3x growth. A recruiter who reads only the CNH section sees a PM who led teams and managed integrations.
The current role almost certainly has outcomes worth stating. The insurer integration work retained 80% of the business. The EHR platform went live in occupational health centers. The claims management platform handles real settlements for real insurers. Those outcomes need to be in the bullets, not in a sidebar or implied from context.
A focused editing session — add a summary, move the 80% retention outcome, add one result per current-role initiative, fix the template — would push this score into the low 80s.
Score your own resume to see how your PM resume performs across all four dimensions.