Resume Teardown #22: Senior PM with 11 Years Across Payments, Banking, and Enterprise SaaS

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 product manager with 11+ years across payments, banking, and enterprise platforms scored 73%. The brand names are strong and the recent bullets have real quantified outcomes. But overlapping role dates create confusion, older roles are filled with generic process bullets, and a 30+ item skills section lists capabilities never demonstrated in the work experience. A hiring manager will spend 6 seconds on this resume and walk away unsure what story it tells.

The Resume

Background: Senior Product Manager at a telecom enterprise (via consulting firm), Dec 2024 - Present. Previously Senior PM at a B2B SaaS broker platform (Apr 2024 - Dec 2024, 8 months). Product Manager at a global payments company (Dec 2020 - Apr 2025, 4+ years). Product Owner at a global bank (May 2020 - Dec 2020, 7 months). Product Owner at an IT services firm working onsite at the same bank (Apr 2018 - May 2020, 2 years). Senior Systems Engineer at a large IT services company (Dec 2014 - Apr 2018). B.Tech in IT. 11+ years total, ~7-8 years in PM/PO roles.

What looked good on the surface: Strong brand-name companies on the resume. BNPL scaling across 300K+ merchants. Authentication success rates improved from 76% to 85%. Platform modernization. Enterprise-grade work in regulated environments.

Score: 73%

Tier Detection: Senior/Staff+ (Borderline)

The evaluation classified this at the staff+ level based on ~8 years of PM/PO experience (Apr 2018 onward). This is borderline. The first two roles (onsite at a global bank via an IT services firm, then at the bank directly) are Product Owner titles with delivery-focused bullets rather than product strategy. If you count only roles with clear product ownership (Dec 2020 onward), it's closer to 5 years, which is senior tier.

This matters because staff+ expectations are significantly higher: vision-setting, org-level influence, multi-year strategy. The resume's strongest bullets (BNPL scaling, enterprise auth) demonstrate senior-level execution excellence, not staff+ strategic leadership. The tier classification may be slightly generous here.

Weights applied: Leadership 40%, Experience 20%, Domain 30%, Skills 10%.

Leadership & Impact: 75%

What worked:

The recent roles have genuinely strong bullets. "Owned product strategy for enterprise authentication (SSO + passwordless), improving success rates from 76% to 85%, with a roadmap targeting 95%+" shows ownership, a North Star metric, and a forward-looking target. "Scaled BNPL ecosystem across 300K+ merchants, driving 28% increase in payment volume and 1.85x user growth" is a strong outcome at meaningful scale.

The resume also shows cross-functional influence in regulated environments (compliance, risk, engineering alignment) and people development (mentoring and scaling teams).

What held it back:

At staff+ level, the evaluation expects vision-setting and multi-year strategy articulation. Every bullet on this resume describes execution outcomes, never strategic decisions. There is no bullet that says "Defined the 3-year platform strategy for..." or "Made the decision to invest in X over Y because..." or "Set the product vision for the authentication platform."

Experience & Background: 80%

What worked:

Clear career progression from systems engineer to product owner to product manager to senior PM. Strong brand-name companies across fintech, banking, telecom, and B2B SaaS. The trajectory is upward and the scope increases with each role.

What held it back:

The most significant issue is overlapping dates. The payments company role is listed as "Dec 2020 - Apr 2025" but the broker platform role runs "Apr 2024 - Dec 2024" and the telecom role starts "Dec 2024 - Present." This means either:

• The payments role was concurrent with the broker and telecom roles (moonlighting? part-time? consulting?)
• The payments end date is wrong and should be earlier

A hiring manager scanning this resume will notice the overlap immediately. It raises questions: Were you doing two PM roles simultaneously? Did you leave the payments company earlier than stated? Is this a resume error? None of these questions have good answers if left unexplained.

Additionally, the two most recent roles are very short: the broker platform (8 months) and the telecom role (5 months so far). Combined with the date confusion, this creates a narrative of instability at the top of the resume, right where first impressions are formed.

The 80% score is generous given these issues. Overlapping dates and short recent tenures are not minor polish items.

Domain Expertise: 75%

What worked:

Genuine depth across two related verticals: payments/fintech (BNPL, broker platform payments) and enterprise identity/authentication (SSO, passwordless). The banking experience adds a third related domain. These verticals share common themes: regulated environments, security-sensitive flows, high-reliability requirements.

The BNPL work demonstrates real domain expertise: "Balanced risk, compliance, and growth trade-offs, enabling scalable BNPL adoption in regulated environments." This shows understanding of domain-specific tensions, not just generic PM work.

What held it back:

The resume mentions "AI-driven automation" and "AI-driven support bot" but these are operational AI usage (deploying chatbots, automating support), not AI product management. There is no evidence of product decisions about model behavior, confidence thresholds, or AI-specific metrics. The skills section lists "AI product strategy (not just feature)" but no bullet demonstrates this.

The domain story is also fragmented. Payments, authentication, broker platforms, banking modernization. A hiring manager might ask: "What is your domain?" The resume answers "enterprise platforms in regulated environments" but never states this explicitly. The thread connecting these roles exists but is invisible.

Skills & Tools: 65%

What worked:

The resume demonstrates hands-on PM craft in the recent roles: defining North Star metrics, using telemetry and Voice of Customer data, establishing observability frameworks (SLA/SLOs), and working with engineering on high-concurrency systems. These are real skills demonstrated through bullets.

What held it back:

The Skills section lists 30+ items, many of which are never demonstrated in the work experience. "Marketplace thinking," "A-B testing strategy," "Org design / operating model," "Customer acquisition strategy," "Trade-off decisions (what NOT to build)" all appear as skills but have zero supporting bullets. The prompt's evaluation rule is clear: skills listed without supporting evidence in work experience carry minimal weight.

At staff+ level, the evaluation expects vision-setting, org-level process design, and hiring/team-building outcomes. The only staff+ skill signal in the actual bullets is "Mentored and scaled engineering teams, driving a culture of ownership." One bullet is not enough to demonstrate staff+ skills depth.

The certifications (CSPO from an online learning platform, a generative AI leadership certificate from a MOOC) are process-oriented and lack completion dates. The evaluation cannot determine if these are recent investments or years-old credentials.

ATS Readiness: 93%

The resume performs well on ATS fundamentals. Standard headers, consistent date formatting, PM keywords present throughout (product strategy, roadmap, stakeholder, metrics, North Star, cross-functional). The high score reflects solid structural formatting and keyword density.

The 5 Changes That Would Move This Score

1. Fix the overlapping dates.

This is the single most confusing element on the resume. If the payments role was a concurrent consulting engagement, say so: "Product Manager (Contract/Part-time)." If the end date is wrong, correct it. If the broker platform was a short engagement while transitioning, add a one-line explanation. A hiring manager should never have to guess about your employment timeline.

2. Add a strategy bullet to the most recent role.

Before: "Owned product strategy for enterprise authentication (SSO + passwordless), improving success rates from 76% to 85%, with a roadmap targeting 95%+"

After: "Defined the 2-year authentication platform vision: Phase 1 (SSO consolidation, shipped, 76% to 85% success), Phase 2 (passwordless-first for SMB, in progress), Phase 3 (zero-trust adaptive auth). Secured executive alignment by demonstrating Phase 1's impact on billing completion rates."

Same work. But now it shows multi-year thinking and executive influence.

3. Cut the skills section by half.

Remove every skill that has zero supporting evidence in the work experience. "Marketplace thinking" with no marketplace bullet is a liability, not an asset. A hiring manager who sees "Org design / operating model" in skills and then finds no org design bullet will question your self-awareness.

Keep: tools you actually used (JIRA, Figma, SQL, analytics platforms), domains you demonstrated (identity/auth, payments, platform architecture), and 3-4 strategic skills that ARE supported by bullets.

4. Rewrite the banking and consulting-era bullets.

The older roles are filled with generic process descriptions:

• "Directed product delivery across large-scale banking programs, ensuring cross-functional alignment"
• "Streamlined processes and integrations, improving delivery efficiency and system reliability"
• "Improved delivery efficiency through process standardization and cross-team collaboration"

These could describe any project manager at any company. At staff+ level, every bullet should show a product decision or outcome. If the work was genuinely delivery-focused (which is fine for a PO role), condense to 2-3 bullets max and add one line of context about what the platform did and who it served.

5. State your domain thread explicitly in the summary.

The summary currently reads as a generic senior PM description. Add one sentence that names your domain: "Specialist in high-reliability, regulated platforms: payments infrastructure, enterprise authentication, and financial services." This gives a hiring manager an immediate mental model for your career and makes the diverse company list feel intentional rather than scattered.

The Pattern

This resume has a common problem among experienced PMs who have worked across multiple companies and domains: it reads as a collection of roles rather than a coherent career story. Each role section is individually decent, but the resume as a whole does not answer the question every hiring manager asks in the first 6 seconds: "What is this person's thing?"

The overlapping dates compound this problem by introducing confusion at the exact moment the reader is trying to form a first impression. The bloated skills section adds noise. The generic older bullets add length without value.

The path from 73% to 82%+ requires:

• Fix the timeline confusion (dates, short tenures)
• State the career narrative explicitly (domain thread in summary)
• Add one strategy/vision bullet to demonstrate staff+ thinking
• Cut the noise (skills bloat, generic older bullets)

The underlying experience is strong. BNPL at scale, enterprise authentication, regulated environments. The resume just needs to tell that story clearly instead of making the reader assemble it from fragments.

Score your own resume to see how your PM resume performs across all four dimensions.