Resume Teardown #45: IAM Expert With 15 Years of Experience but Only 1 Year as PM
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 15+ years across enterprise IAM, banking security, and consulting scored 63% against a Staff Product Manager, Enterprise Security, IAM & Data Platform role. The IAM domain knowledge is genuine and rare. But the resume has only one year of PM-titled experience, and that year's bullets describe responsibilities without outcomes, PM craft artifacts, or data-driven decision-making evidence.
The Resume and the Role
Background: Senior Product Manager II at a large enterprise software company. Previously Assistant Vice President, IAM at a global banking institution. Senior IT Consultant at an IT solutions firm. Systems Engineer at a large IT services company. M.Sc. and B.Tech from top universities.
Target role: Staff Product Manager, Enterprise Security, IAM & Data Platform. The role is an experienced IC position requiring 8-12+ years of PM experience, ownership of complex PRDs, JTBD-style customer research, staff-level PM mentorship, and foundational AI/ML understanding. The JD explicitly requires a track record of "delivering high-impact, technically complex products" — not domain expertise alone.
Score: 63% match
What Genuinely Works: Domain Depth That Cannot Be Faked
The IAM domain signal on this resume is real and rare. Most PM candidates applying for IAM platform roles understand identity at a product surface level. This resume reflects someone who has lived inside enterprise IAM for eight years at a regulated financial institution:
"Led enterprise IAM strategy and identity governance initiatives."
"Drove audit, compliance, and access governance programs."
The use of Zero Trust, FedRAMP, NIST, and DISA STIG in the skills section reads as earned rather than keyword-stuffed. A hiring manager for an enterprise security platform role reads this and immediately recognizes the domain vocabulary as genuine. That is a real advantage over candidates who have done B2C identity work or surface-level enterprise integration.
The current PM role adds direct relevance:
"Own product strategy and roadmap for the Enterprise Identity Platform."
"Lead authentication, authorization, MFA, SSO, OAuth, and identity platform capabilities."
The scope is exactly right for this JD. The problem is not the scope. The problem is everything that comes after the scope description is missing.
The Core Problem: Scope Without Evidence
Every bullet in the current PM role states what the candidate owns. None of them say what changed because of that ownership.
- "Own product strategy and roadmap" — what shipped? What adoption metric moved?
- "Lead authentication, authorization, MFA, SSO, OAuth" — what capability did you define? What trade-off did you make?
- "Prioritize platform investments by balancing customer needs, compliance, and business impact" — how? What framework? What did you choose over what?
- "Partner with Engineering, Security, and enterprise customers" — what artifact did you produce? PRD? Technical spec? Architecture review?
For a staff-level PM role, scope claims without outcomes or artifacts are not evidence of staff-level work. The JD explicitly asks for complex PRD ownership, technical specification, backlog management, and measurable platform impact. None of those appear on the resume.
This is the dealbreaker the evaluation flagged. It is not that the work did not happen. It is that the resume does not show it happened.
The Seniority Gap: 1 Year of PM vs. 8-12 Required
The JD asks for 8-12+ years of progressive PM experience. The resume shows roughly one year with a PM title. The previous eight years were at a banking institution as an AVP-level IAM leader — not a PM role.
This is the hardest gap to close with resume rewrites alone. The domain expertise is deep. The PM tenure is not. A staff PM role at a product company is evaluating candidates who have spent a decade building products, managing backlogs, writing PRDs, running user research, and iterating based on metrics. One year of PM title experience, regardless of how strong, does not demonstrate that pattern.
The honest framing: this resume is a strong fit for a Senior PM in the IAM domain, not a Staff PM. A senior role would value the IAM depth and overlook the shorter PM title tenure. A staff role is looking for someone who can mentor Lead PMs on technical product management — which requires having done that craft at depth for many years.
The Banking IAM Role: Eight Years of Unframed PM Work
Here is what the banking role bullets currently say:
"Led enterprise IAM strategy and identity governance initiatives." "Drove audit, compliance, and access governance programs." "Partnered with Data & Analytics teams on identity telemetry and compliance reporting." "Modernized identity lifecycle processes across global banking platforms."
These bullets describe valuable work. But they are written as operational and governance leadership bullets, not product management bullets. The question worth asking: in eight years as an AVP running IAM strategy, did you ever define requirements for a platform change, prioritize a roadmap of identity capabilities, write a spec for an engineering team, or measure adoption of a launched capability?
If the answer is yes, those moments are product management work even without the PM title. And they should be on this resume.
Before: "Modernized identity lifecycle processes across global banking platforms."
After: "Defined requirements and prioritized the modernization of identity lifecycle workflows across 40,000+ employee accounts, working with engineering teams to ship automated provisioning that reduced onboarding time from 5 days to 4 hours."
That reframe does not claim a PM title. It shows PM-equivalent ownership. And it directly addresses the JD's requirement for a "track record delivering high-impact, technically complex products."
The Telemetry Bullet: Your Best Bridge to Data Platform
"Partnered with Data & Analytics teams on identity telemetry and compliance reporting."
This is the only bullet that touches the data platform half of this role. The JD combines IAM with data platform, and the evaluation found data platform depth almost entirely missing. This bullet is the seed of that story.
But "partnered" and "compliance reporting" describe adjacency, not ownership. What was the telemetry for? What decisions did it inform? What compliance reports did it power and for whom?
Before: "Partnered with Data & Analytics teams on identity telemetry and compliance reporting."
After: "Defined identity telemetry requirements with the Data & Analytics team to power real-time access anomaly detection and quarterly compliance reporting for 12 regulated markets. Telemetry data reduced time-to-detect unauthorized access events from days to hours."
Now the data platform work is visible, the product ownership is clear, and it directly addresses the JD's data platform requirement.
The Staff-Level Gaps That Cannot Be Rewritten Away
Two gaps the evaluation flagged as genuine dealbreakers that resume edits alone cannot fix:
PM mentorship: The JD explicitly requires coaching junior-to-lead PMs on technical product management. There is no evidence of this on the resume. If mentoring has happened informally, make it explicit. If it has not happened yet, this is a real gap.
AI/ML product work: The JD asks for "foundational AI/ML applications understanding" and the evaluation applied AI PM criteria accordingly. The resume has no AI/ML signal at all — no risk scoring, anomaly detection, intelligent policy recommendations, or AI-assisted security workflows. In 2026, enterprise security platforms are increasingly AI-adjacent. A staff PM at this company will be expected to have an informed PM perspective on where AI fits in the security product roadmap.
Neither of these is a blocker for a senior PM role. Both are genuine blockers for a staff PM role at this specific JD.
Dimension Scores Against This JD
Domain Expertise: 82% (strongest dimension)
IAM depth is real and directly aligned. Zero Trust, FedRAMP, NIST, DISA STIG fluency signals regulated enterprise familiarity. The gap: data platform depth is thin beyond the one telemetry bullet.
Leadership & Impact: 58%
Scope ownership is stated but not proven. No outcomes, no shipped capabilities, no adoption metrics, no mentorship evidence. For a staff-level role, leadership is measured by platform impact and organizational influence — neither is visible.
Experience & Background: 66%
Coherent career arc from IAM engineering to banking leadership to PM. The PM tenure is the mismatch — one year against an 8-12 year requirement.
Skills & Tools: 48% (dealbreaker flagged)
No PRD evidence, no backlog ownership, no JTBD research, no launch metrics, no AI/ML signal. The technical domain skills are strong. The PM craft skills are entirely absent from the evidence.
ATS Readiness: 61%
Fail — Formatting: Content appears interleaved, with contact information, education, skills, and experience fragmenting in a way that suggests a multi-column PDF layout causing ATS extraction problems. The resume likely looks polished as a PDF but scrambles for automated parsers. Single-column reformatting is the highest-urgency fix before any content work.
Warnings:
- "Hindii" is a typo (should be "Hindi") — small but visible
- Security acronyms (FedRAMP, DISA STIG, OIDC, SAML) are not spelled out on first use, which may limit broader recruiter readability
- PM keywords heavily concentrated in summary/skills rather than experience bullets
PM keyword gaps: metrics, prioritization, cross-functional, discovery, launch, user research, data-driven, trade-off, outcome, adoption, retention, experimentation, requirements, backlog — most of these are absent because the bullets don't show PM craft.
The 5 Changes That Would Move This Score
1. Add outcomes to every current PM role bullet.
For each capability you own, add what shipped and what moved: adoption, security posture improvement, support ticket reduction, enterprise deal enablement. One metric per bullet changes the read from responsibility to ownership.
2. Reframe three banking IAM bullets as product-equivalent work.
Find the moments where you defined requirements, prioritized a platform change, or measured an outcome. Write those as PM-shaped bullets. Eight years of IAM strategy contains product work — surface it.
3. Expand the telemetry bullet into a data platform signal.
Name the data model, the decision it powered, and the outcome it produced. This is currently your only bridge to the data platform half of the JD.
4. Add one PM craft artifact explicitly.
Name a PRD, technical spec, architecture review, or launch plan you owned. Even one line showing you produced a formal PM artifact changes the evaluation from "no craft evidence" to "some craft evidence."
5. Fix the formatting before anything else.
ATS formatting fail means the resume may not parse correctly for automated systems. Single-column layout is a 30-minute fix that improves every other dimension.
The Pattern
This resume represents a deep domain expert making the transition into product management who has not yet translated eight years of IAM leadership into PM-language evidence. The domain knowledge is the strongest asset and is genuinely rare for this type of role. The PM craft is the gap — not because the work was not done, but because it is not on the resume.
The honest recommendation: this is a strong fit for a Senior PM, IAM role at an enterprise software company. The Staff PM bar at this JD requires PM craft depth that a one-year title and hollow bullets cannot currently demonstrate, regardless of domain expertise. Build the PM evidence over the next 12-18 months in the current role, and this profile becomes a strong Staff PM candidate.
Check your job fit to see how your resume matches against a specific role.