Resume Teardown #31: US-Based Mid-Level PM with IVR and Chatbot Experience but No Summary and No Strategy
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 US-based Software Product Manager with 6 years across IVR systems, conversational AI chatbots, enterprise workforce tools, and industrial sensors scored 67%. The resume has real product metrics (15% IVR containment increase, 10% payment containment, $1M+ product line). But there is no summary, no evidence of strategic PM thinking, lateral moves across 4 companies in 5 years with no visible progression, and some bullets are pure process descriptions. A mid-level PM resume needs to show product judgment, not just delivery execution.
The Resume
Background: Product Owner at a telecom company via contracting (Oct 2024 - Present). Previously Product Manager II at a mobile carrier (Sep 2023 - Oct 2024). Software Product Manager at a facilities management company (Jun 2022 - Feb 2023). Global Product Manager at an industrial instruments company (Aug 2019 - Jun 2022). BS in Chemical Engineering. PSPO certification. Side projects in RAG and diagram generation.
What looked good on the surface: Quantified IVR containment improvements. AWS Lex chatbot launch. $1M+ product line ownership. Cross-functional work with data science (ML for intent recognition). Clear technical fluency across API integration, NLU, and call flow design.
Score: 67%
The Missing Summary: A Critical Omission
This resume has no professional summary. The reader goes straight from the title "Software Product Manager (PSPO)" into work experience. This means a hiring manager has to read 3-4 bullets before they can piece together: what does this person do, at what level, in what domain?
For a mid-level PM with 6 years, the summary should communicate in 3 seconds:
- Total PM years and level
- Product type (conversational AI, enterprise SaaS, IVR)
- Signature achievement with a number
- What kind of role you are targeting
Without it, the resume forces the reader to do assembly work. Most will not bother.
The IVR Bullets: Good Metrics, Missing Judgment
"Launched an update to a legacy IVR system to enable an NLU update at the top of the IVR, leading to 15% increase in containment."
This is the strongest bullet on the resume. It names the product (IVR), the change (NLU at top of call flow), and the outcome (15% containment increase). A hiring manager can see: this person shipped something and it moved a metric.
"Released an update to a billing and payments flow to allow recent payment information playback in the IVR, increasing containment for payments by 10%."
Also solid. Named feature, clear outcome.
What is missing from both: Why this feature? What user data or business case drove the prioritization? What alternatives did you consider? At mid-level, a hiring manager expects to see product judgment, not just delivery competence.
Before: "Launched an update to a legacy IVR system to enable an NLU update at the top of the IVR, leading to 15% increase in containment."
After: "Prioritized NLU integration at the top of the IVR call flow based on analysis showing 40% of callers dropped before reaching the right menu. Launch increased containment by 15%, reducing live agent transfers by [X] calls/month."
The Process Bullets: Telling, Not Showing
Several bullets describe PM activities without outcomes:
- "Owned Backlog and translated Business Cases into usable User Stories using an If, When, Then style."
- "Define and document system requirements including call flow logic, API behavior, and data mapping."
- "Participate in UAT validation, defining test scenarios, validating outputs, and providing release sign-off."
At mid-level, these are table stakes. Every PM does backlog grooming, requirements writing, and UAT. Listing them without an outcome adds no value and takes space from stronger bullets.
The fix: Delete process-only bullets. If you must keep them, attach an outcome. "Defined call flow requirements across 12 IVR paths, reducing development rework by [X%] compared to previous releases."
The Lateral Move Problem
Four companies in 5 years (Aug 2019 - Present), all with similar titles:
- Global Product Manager (3 years)
- Software Product Manager (8 months)
- Product Manager II (13 months)
- Product Owner (current, contract)
No visible promotion. No increasing scope. A hiring manager sees lateral moves and asks: "Is this person growing, or job-hopping at the same level?"
The fix is not to remove roles. It is to show progression within the bullets. If scope increased (from one product line to multiple), say so. If responsibility grew (from feature delivery to roadmap ownership), make it explicit. Without these signals, the career reads as flat.
The Industrial Sensor Role: Underexploited
"Led product lines for plastic industrial pressure, temperature, and level sensors ($1M+ annual revenue)." "Drove 10% YoY growth through product and market strategy execution."
This is the most strategic-sounding work on the resume, and it gets the least attention (only 6 bullets, several generic). A Global Product Manager owning $1M+ in revenue should show: pricing decisions, competitive positioning, market expansion, feature roadmap driven by customer feedback.
"Directed ANSYS (CFD) innovation for an ultrasonic low flow sensor project" suggests R&D-level product work, but it reads as a technical task rather than a product decision. Why that project? What customer need drove it? What was the market opportunity?
Dimension Scores
Domain Expertise: 70% IVR, telecom, conversational AI, and enterprise SaaS exposure is visible. But no single domain goes deep enough to signal expertise versus exposure. The resume covers 4 different product types in 5 years.
Experience & Background: 69% 6+ years of direct PM experience across B2B and B2C. Clear titles. But short tenures and lateral moves without visible progression weaken the narrative. No single company shows deep impact built over time.
Skills & Tools: 64% Hands-on backlog management, roadmapping, UAT, API integration, and technical tools (Jira, AWS Lex, Postman, Python, Twilio). But no evidence of go-to-market, A/B testing, user research, or structured prioritization frameworks. Execution-heavy, strategy-light.
Leadership & Impact: 62% Real product outcomes (15% containment, 10% payment containment, $1M product line). But many bullets describe process without outcomes, and there is no evidence of strategic product thinking (setting vision, choosing what NOT to build, influencing company direction).
ATS Readiness: 81%
Standard headers, consistent dates, clean formatting. Warning on unexpanded acronyms (IVR, NLU, UAT). PM keywords present but missing: A/B testing, OKR, go-to-market, KPI, retention, conversion, MVP. The keyword gap reflects the actual gap in the resume: it is delivery-focused, not strategy-focused.
The 5 Changes That Would Move This Score
1. Add a professional summary.
"Software Product Manager with 6 years owning conversational AI, IVR, and enterprise products. Shipped NLU-powered call flow updates that increased containment by 15%. Experience spans AWS Lex chatbots, enterprise workforce tools, and industrial sensor product lines ($1M+ revenue). PSPO certified."
2. Delete all process-only bullets.
Remove "Participate in UAT validation," "Owned backlog and translated business cases," and "Define and document system requirements." These describe job responsibilities, not achievements. Replace with outcome-driven bullets.
3. Add product judgment to the top 3 bullets.
For each strong metric, add the "why" context: what data informed the decision, what alternatives existed, why you chose this approach. This shifts the resume from "delivery PM" to "strategic PM."
4. Show progression across roles.
Add a sentence or context line showing how each role expanded your scope: "Moved from single-product ownership (sensors) to platform-level IVR strategy serving millions of subscribers."
5. Expand the industrial sensor role with strategic bullets.
Pricing decisions, competitive positioning, customer research, market expansion, product-market fit signals. This role had the most strategic PM responsibility and currently gets the least attention.
The Pattern
This resume represents a common mid-level PM plateau: strong execution skills, real shipped features with metrics, but no visible strategic growth. The resume reads as "reliable delivery PM" rather than "PM who shapes product direction."
At mid-level (2-5 years), hiring managers expect to see the transition from "I ship what the roadmap says" to "I decide what goes on the roadmap." This resume shows the former clearly but the latter not at all.
The path from 67% to 75%+:
- Add a summary that positions the strongest work immediately
- Cut process bullets and replace with strategic decisions
- Show why you chose features, not just that you shipped them
- Connect the lateral moves into a deliberate progression story
- Expand the most strategic role (industrial sensors) with business judgment evidence
The technical fluency and real metrics are there. The resume just needs to stop describing PM activities and start showing PM decisions.
Score your own resume to see how your PM resume performs across all four dimensions.