Resume Teardown #29: Data Engineer Calling Himself Technical PM but Every Bullet Is Infrastructure
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 data engineer with 5+ years across healthcare and fintech clients positions himself as a "Technical Product Manager" scored 66%. The resume has impressive scale (50M+ records, 500+ sponsor migrations, 2.5M+ members) and genuine cross-functional leadership (10-person international team). But every bullet describes data infrastructure work, not product decisions. The title claims PM. The content proves engineer. This mismatch is worse than honest positioning because it sets expectations the resume cannot deliver on.
The Resume
Background: Senior Data Engineer at a consulting firm (Client: a US digital health platform), Oct 2023 - Present. Previously Senior Software Engineer at a different consultancy (Client: a global bank's credit risk division), Mar - Sep 2023. Before that, Data Engineer at a third consultancy (Client: a US healthcare insurance company), Mar 2021 - Mar 2023. B.Tech in Information Technology. Side projects include an AI resume matching tool and a diagram generator.
What looked good on the surface: First data engineering hire for India operations (founding team signal). Scaled a team from 0 to 10 engineers across three countries. Processed 50M+ raw records in healthcare datasets. Migrated 500+ sponsors. Enabled 2.5M+ eligible members. Cross-functional bridge between client stakeholders and engineering.
Score: 66%
The Core Problem: The Title Lie
The summary opens with: "Technical Product Manager with 5+ years in data engineering, leading end-to-end data platforms."
This immediately creates a credibility problem. A hiring manager reads "Technical PM" and expects: roadmap ownership, user research, prioritization frameworks, shipping features to users. They get: Spark pipelines, AWS Glue jobs, data standardization.
Claiming a PM title you have not held is riskier than honest transition positioning. "Senior Data Engineer transitioning to PM" sets appropriate expectations. "Technical PM" sets expectations the resume fails to meet, which means rejection at the screen stage rather than an interview opportunity.
What Works: Scale and Team Leadership
Two bullets genuinely signal PM-transferable leadership:
"Joined as the first data engineering hire in India, helping establish and scale the India engineering team."
Founding team energy. Building from zero. This shows initiative beyond individual contribution.
"Led and scaled a team of 10 engineers across India, US, and Bosnia, conducted 100+ technical interviews and 20+ knowledge transfers."
International team leadership, hiring responsibility, and knowledge transfer ownership. These are real signals that transfer to PM roles, especially at companies where PMs work closely with distributed engineering teams.
The problem: Neither bullet shows a product decision. They show engineering leadership. The resume needs to connect team leadership to product outcomes.
The 90% Improvement Bullet: Impressive but Technical
"Owned first-touch ingestion and end-to-end onboarding of multi-source healthcare data, reducing onboarding and processing time by 90%."
90% reduction in processing time is a strong metric. But a PM hiring manager reads this and asks: "Processing time for whom? What user problem did this solve? Did this unblock a product feature? Did customers onboard faster because of this?"
The word "onboarding" here means data onboarding (ETL pipeline setup), not user onboarding. The resume needs to make the downstream product impact explicit.
Before: "Owned first-touch ingestion and end-to-end onboarding of multi-source healthcare data, reducing onboarding and processing time by 90%."
After: "Reduced new sponsor onboarding from [X weeks] to [Y days] by designing scalable data ingestion workflows, directly enabling the product team to launch [feature] for 500+ healthcare sponsors faster."
The Cross-Functional Bridge: The Hidden PM Bullet
"Acted as a cross-functional bridge between client stakeholders, product, and engineering teams, ensuring alignment and successful delivery of large-scale data integration programs."
This is the most PM-relevant work on the resume, and it is buried as the last bullet under the current role with zero specifics. What did "ensuring alignment" look like? Did you define requirements? Resolve conflicting priorities? Translate business goals into technical specs?
Before: "Acted as a cross-functional bridge between client stakeholders, product, and engineering teams..."
After: "Partnered with product managers and client stakeholders to define data integration requirements for 50M+ record migrations. Translated business needs (member eligibility validation, claims processing SLAs) into technical specifications, prioritizing delivery across 3 workstreams based on client revenue impact."
Side Projects: Underutilized
The resume lists two side projects:
- Delhi NCR Rent Map (live product)
- AI Resume Generator Bot (Telegram)
These are buried at the bottom with minimal detail. For a transition candidate, these could be the strongest PM evidence on the entire resume if framed correctly.
For the Rent Map: Who uses it? How many users? What problem does it solve? How did you decide what features to build? What did you learn from user behavior?
For the Resume Bot: Same questions. Did you do any user research? How did you evaluate output quality? What tradeoffs did you make?
Right now these read as engineering hobby projects. Reframe them as mini product case studies with user counts, decisions made, and lessons learned.
Dimension Scores
Domain Expertise: 77% Deep healthcare data exposure (US healthcare datasets, claims, eligibility, member data) plus credit risk experience. This is genuinely valuable for PM roles at healthtech or fintech companies. The domain knowledge is real.
Experience & Background: 68% Clear progression from Data Engineer to Senior Data Engineer with team scaling. But no formal PM title and all experience is delivery-focused engineering at consultancies, which raises the "did you own anything or just execute requirements?" question.
Skills & Tools: 63% Highly proficient in data technologies (AWS, Spark, Hadoop). Claims "Product Strategy" and "PRDs" in the skills section but demonstrates neither in work experience. The gap between skills-listed and skills-demonstrated is the largest issue.
Leadership & Impact: 62% Team scaling and cross-functional collaboration are genuine. But no direct product decision-making or outcome ownership is visible. All leadership is engineering leadership.
ATS Readiness: 81%
Clean structure, standard headers, consistent dates. PM keywords found but mostly in the skills section rather than experience bullets. Missing: A/B testing, OKR, backlog, go-to-market, KPI, retention, conversion, MVP, user research, prioritization. These are all PM-specific terms that the experience simply does not contain.
The 4 Changes That Would Move This Score
1. Drop the "Technical PM" title. Use honest transition positioning.
Before: "Technical Product Manager with 5+ years in data engineering, leading end-to-end data platforms."
After: "Senior Data Engineer with 5+ years building healthcare and fintech data platforms at scale (50M+ records, 10-person international team). Transitioning to Product Management, with hands-on experience bridging product, engineering, and client stakeholders. Shipped 2 consumer-facing products as side projects."
2. Expand side projects into proper product case studies.
Give each project 3-4 bullets covering: the user problem, your product decisions, launch metrics, and what you learned. For a transition candidate, these are your only evidence of product thinking. Treat them like your most recent PM role.
3. Add product context to infrastructure bullets.
For every infrastructure improvement, add the downstream product impact. "Reduced data processing time by 90%" becomes "Reduced data processing time by 90%, enabling the product team to launch sponsor self-service onboarding 3 months ahead of roadmap."
4. Make the cross-functional bridge bullet specific and prominent.
If you truly worked with product managers to define requirements and prioritize delivery, this is your strongest transition signal. Expand it into 2-3 specific bullets showing the decisions you influenced, the tradeoffs you navigated, and the product outcomes that resulted.
The Pattern
This resume represents a common and dangerous transition archetype: the engineer who claims a PM title without PM evidence. The instinct makes sense (you want to be seen as a PM) but the execution backfires (the resume cannot support the claim, so reviewers feel misled).
The underlying experience is genuinely strong for a data-to-PM transition. Healthcare domain depth, scale signals, team leadership, cross-functional communication, and shipped side projects are all real PM assets. The resume just needs to stop pretending it is already there and instead tell an honest, compelling transition story.
The path from 66% to 75%+:
- Honest positioning (transitioning engineer, not claiming PM)
- Side projects reframed as product case studies with user evidence
- Infrastructure bullets connected to downstream product impact
- Cross-functional work expanded with specific product decisions influenced
The technical depth is a strength, not a weakness. Own it as your differentiator. "I am an engineer who understands product" is a stronger pitch than "I am a PM who happens to have an engineering background" when the evidence only supports the first claim.
Score your own resume to see how your PM resume performs across all four dimensions.