Resume Teardown #11: Mid-Level PM with Strong IVR Metrics but Delivery-Heavy Framing

This is part of our Resume Teardown series where we score real PM resumes (anonymized) and break down what the evaluation found. New teardown every day.

TL;DR: This mid-level PM with 6+ years across telecom, conversational AI, and enterprise SaaS scored 67%. The resume has genuine quantified outcomes in recent roles (15% containment increase, 10% payment containment) and shows clear product ownership. The gaps: too many bullets describe process participation rather than leadership, no evidence of strategic PM craft (GTM, user research, experimentation), and career progression reads as lateral moves rather than increasing scope.

The Resume

Background: Product Owner at a major cable operator (Oct 2024 – present). Previously PM II at a mobile carrier (Sep 2023 – Oct 2024), Software PM at a facilities management company (Jun 2022 – Feb 2023), and Global PM at an industrial instrumentation company (Aug 2019 – Jun 2022). BS in Chemical Engineering. PSPO certified, plus digital PM and design thinking certifications. Personal projects in RAG and Python tooling.

What looked good on the surface: Multiple PM-titled roles across different industries. Quantified outcomes in the most recent role. Technical depth in IVR/NLU/conversational AI. PSPO certification. Cross-functional collaboration mentioned repeatedly. Skills section well-organized by category.

Score: 67%

Mid-level calibrated scoring (weights: Leadership 30%, Experience 30%, Domain 15%, Skills 25%).

Leadership & Impact: 62%

What worked:

Two bullets stand out as genuinely strong:

• "Launched an update to a legacy IVR system to enable an NLU update, leading to 15% increase in containment" — clear ownership, specific technology, quantified outcome.
• "Released an update to a billing and payments flow to allow recent payment information playback, increasing containment for payments by 10%" — same pattern: feature, context, metric.

These show what good PM bullets look like: you shipped something specific, and here's the measurable result.

What held it back:

1. Process bullets outnumber impact bullets. "Drive roadmap execution aligned to customer experience, containment, and operational efficiency goals" — this describes intent, not achievement. What did you actually drive? What was the result? "Participate in UAT validation, defining test scenarios, validating outputs, and providing release sign-off" — this is QA participation, not PM leadership. Anyone on the team could write this bullet.

2. Metrics lack context. 15% increase in containment — from what baseline? Over what timeframe? For how many users? Without context, a hiring manager cannot assess whether this is impressive or incremental. "15% containment increase across 10M monthly IVR interactions within 6 weeks of launch" tells a completely different story than "15% containment increase."

3. The first-person framing weakens ownership. "As a Product Owner, I oversee delivery of development for an Enterprise IVR system" — this reads as a job description, not an achievement. Remove it entirely and let the bullets speak.

The core problem: The resume has 2-3 strong impact bullets buried among 15+ process descriptions. A hiring manager scanning in 7 seconds sees process, not impact.

Experience & Background: 69%

What worked:

• Four PM-titled roles across different company types (telecom, mobile, facilities management, industrial instrumentation)
• Both B2B and B2C experience
• Both customer-facing products (IVR, chatbot) and internal tools (workforce management)
• Engineering background (Chemical Engineering) adds technical credibility

What held it back:

1. Short tenures raise questions. The facilities management role lasted 8 months. The mobile carrier role lasted 13 months. The current role is a contract position. A hiring manager sees this pattern and wonders: were these layoffs, performance issues, or intentional moves? The resume doesn't address it.

2. No visible progression. Product Owner → PM II → Software PM → Global PM. The titles don't show a clear upward trajectory. The scope doesn't visibly increase across roles. A mid-level PM with 6+ years should be showing movement toward senior: larger products, more stakeholders, strategic influence, team leadership.

3. The industrial PM role is underutilized. Three years as Global PM with $1M+ revenue ownership and 10% YoY growth — this is the most senior-sounding role on the resume, but it has the weakest bullets. "Worked with engineering on creating new products" and "Supported digital communication systems" are vague. This role should be the anchor of the resume, not an afterthought.

Fix: Rewrite the industrial PM role with the same rigor as the current role. "Led product lines for industrial sensors ($1M+ annual revenue)" is a good start — now add what you did: what decisions you made, what you launched, what the customer impact was. "Drove 10% YoY growth" is strong but needs the how.

Domain Expertise: 70%

The resume shows breadth across IVR/telecom, conversational AI, enterprise SaaS, and industrial IoT. For a mid-level PM, this breadth is acceptable but not a differentiator.

What worked:

• Clear expertise in IVR and conversational AI (NLU, AWS Lex, intent architecture)
• Exposure to both legacy systems and modern AI-driven products
• Technical vocabulary demonstrates genuine understanding (call flow logic, API behavior, data mapping)

What held it back:

• Breadth without depth. Four different domains in 6 years means no single vertical where you're the expert. A hiring manager looking for a "conversational AI PM" would want to see deeper evidence: user research in the IVR space, industry benchmarks, competitive analysis, thought leadership.
• No customer empathy signals. The resume describes systems and integrations but never mentions talking to users, analyzing support tickets, or understanding customer pain points.

Skills & Tools: 64%

This dimension carries 25% of the weight for mid-level PMs.

What worked:

• Well-organized skills section (Product & Agile, Dev & APIs, AI & Data, Soft Skills)
• Real-world application of several tools visible in experience (AWS Lex, Jira, Python)
• PSPO certification demonstrates formal Scrum knowledge
• Personal projects (RAG tool, Mermaid diagram creator) show technical initiative

What held it back:

1. Delivery-focused, not strategy-focused. The PM craft demonstrated is: backlog management, user stories, sprint planning, UAT, release sign-off. These are execution skills. What's missing: product vision, go-to-market, user research, experimentation, OKRs/KPIs, prioritization frameworks beyond "business impact analysis."

2. Skills listed but not demonstrated. "Product Strategy" and "Lifecycle Management" appear in the skills section but nowhere in the experience bullets. If you cannot point to a bullet that proves you did product strategy, remove it from the skills list.

3. No evidence of data-driven decision making beyond ML collaboration. The Data Science collaboration bullet is interesting but positioned as a support function ("Collaborated with Data Science to improve intent recognition") rather than PM-led ("Used ML-driven intent clustering to reprioritize chatbot roadmap, focusing on the 5 highest-volume unresolved intents").

ATS Readiness: 81%

Good overall. Standard headers, clean formatting, consistent dates. The main issue: acronyms (IVR, NLU, UAT) not spelled out on first use. Missing keywords: A/B testing, OKR, go-to-market, KPI, retention, conversion, MVP.

The missing keywords are telling — they represent the PM craft that's absent from the resume itself, not just the skills section.

Key Takeaways

1. Lead with outcomes, bury process. For every role, the first 2 bullets should be your strongest quantified outcomes. Process bullets (backlog management, UAT, documentation) go at the end or get cut entirely. A hiring manager who sees "15% containment increase" first will keep reading. One who sees "Participate in UAT validation" first will move on.

2. Your strongest role has your weakest bullets. The industrial PM role (3 years, $1M+ revenue, 10% growth, global stakeholders) should be the centerpiece. Rewrite it with the same outcome-focused approach as your current role.

3. Show progression, not just breadth. 6+ years across 4 companies is breadth. What's missing is the story of growth. Did your scope increase? Did you go from feature-level to product-level? Did you start influencing strategy? Make this explicit.

4. Add one strategic bullet per role. "Shaped the 2024 IVR roadmap based on containment data analysis, prioritizing 3 high-impact NLU improvements over 12 feature requests" — this shows strategic thinking, not just execution. You likely did this work; the resume just doesn't say so.

5. Remove process-only bullets. "Participate in UAT validation" and "Define and document system requirements" are table stakes for any PM. They don't differentiate you. Replace them with outcomes or cut them to make room for stronger bullets.

The Pattern

This resume represents a common mid-level PM trap: strong execution skills, genuine product outcomes, but framed as a delivery manager rather than a product leader. The work is clearly PM work — shipping features, measuring containment, collaborating cross-functionally. But the resume reads like someone who executes a roadmap rather than someone who shapes one. At the mid level, hiring managers want to see the transition from "I shipped what was asked" to "I decided what to ship and here's why." That shift in framing — from delivery to decision-making — is the difference between 67% and 80%+.