Resume Teardown #35: 8 Years in BFSI Operations, Now Shipping AI Products, but the Resume Still Reads Like a Transformation Lead
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 Product Manager with 8 years across TCS, Standard Chartered, and Marsh McLennan plus recent AI product launches scored 74%. The resume has genuine strengths: deep BFSI domain knowledge, quantified operational wins (30 FTE reclaimed, 3 FTE freed, 30% efficiency gains), and real builder credibility from launching a live consumer product. But it still reads more like a process transformation lead than a clearly positioned PM. The skills gap is not in what was done, but in how it is framed.
The Resume
Background: Co-Founder at a consumer product startup (Apr 2026 - Present). AI Product Management cohort graduate (Feb 2026 - Apr 2026). Senior Manager, Business Analysis at Marsh McLennan India (Mar 2025 - Dec 2025). Manager, Process Standardization at Standard Chartered GBS (Jun 2023 - Mar 2025). IT Business Analyst at TCS for 5+ years (Mar 2017 - Jun 2022). MBA from XLRI Jamshedpur. B.Tech in Information Technology.
What looked good on the surface: Clear BFSI domain expertise with recognizable brands. Quantified outcomes in recent roles. A live consumer product launched from scratch. AI products built with full PRD discipline. MBA from a top-tier school.
Score: 74%
The Core Strength: Domain Depth That Cannot Be Faked
This is not surface-level BFSI exposure. The resume uses domain language naturally across banking and insurance workflows:
"Reclaimed ~30 FTE of manual capacity by leading discovery and requirements for client-communication workflow automation across CDD and Servicing & Transactions"
This bullet works because it names the specific domain area (CDD, Servicing & Transactions), shows the problem (manual capacity being consumed), and quantifies the outcome (30 FTE). A hiring manager for a BFSI PM role reads this and thinks: "This person understands regulated operations deeply enough to diagnose where automation would actually work."
"Strengthened risk and compliance controls on the mass-upload invoicing system by designing and rolling out a role-based access-authorization framework to 500+ users across EU regions"
Here, the domain expertise is demonstrated through the product decision, not just listed as a skill. You did not just say "I know compliance." You showed that you identified a risk, designed a controls framework, and rolled it out at scale.
The Core Problem: Transformation Language, Not Product Language
The resume consistently uses process transformation vocabulary rather than product management vocabulary. Bullets describe efficiency gains and workflow changes rather than product decisions, user problems, and shipped features.
Look at the framing across roles:
- "Drove a ~30% processing-efficiency gain by leading discovery and harmonisation..."
- "Freed ~3 FTE of broker capacity by centralising Placement Data Capture..."
- "Standardised core CDD and Servicing & Transactions workflows..."
- "Reclaimed ~30 FTE of manual capacity by leading discovery and requirements..."
These are all strong outcomes. But they read as process transformation, not product management. A hiring manager scanning quickly will classify this resume as "strong BA/ops transformation lead considering PM" rather than "PM with transformation background."
The fix is not changing what you did. It is reframing around the product lens:
- What user problem did you solve?
- What did you ship (feature, workflow, tool)?
- What decision did you make between alternatives?
- What happened after launch?
Before: "Freed ~3 FTE of broker capacity by centralising Placement Data Capture into a Warsaw Center of Excellence"
After: "Shipped a centralised data capture workflow for 200+ brokers across 20 markets, eliminating 30-40 min/week of manual entry per broker. Designed the target operating model and secured multi-market leadership buy-in for the migration."
Same work. But now it leads with the shipped artifact and the user impact rather than the FTE savings.
The Skills Section: Asserted, Not Demonstrated
The Skills section lists PM craft extensively: product discovery, problem framing, PRD authoring, roadmapping, experimentation, A/B testing, north-star and guardrail metrics, product analytics.
But most of these skills are not demonstrated in the experience bullets. The experience section shows discovery and requirements, but not roadmapping decisions, experimentation results, north-star metric definition, or analytics-driven iteration.
This creates a credibility gap. When a recruiter sees "A/B testing & experimentation" in skills but zero mention of an experiment in any role bullet, they discount it. Skills that are listed but never shown in action are nearly invisible to hiring managers.
The fix: For each PM skill you list, ask yourself: "Which bullet proves I did this?" If no bullet proves it, either add a bullet that does or remove the skill from the list. A shorter, fully-evidenced skills section is stronger than a comprehensive but unsupported one.
The Founder Work: Builder Credibility With a Framing Gap
The Gal Pal section is the strongest PM-signal block on the resume:
"Launched a hand-verified women's-friendship PWA from zero to a live Bangalore beta with 154 sign-ups"
"Designed and run a human-verification gate (video or phone call before access) that blocked 34 fake male accounts"
"Led a 6-person team through a 4-day buildathon from blank page to Product Hunt launch"
This is real 0-to-1 product work. You defined the problem, made product decisions (human verification over automated), launched, and have early traction numbers.
But the bullets emphasize the sprint more than the product thinking. A hiring manager reading the buildathon bullet will think: "Fast execution." That is good. But they will not think: "Good product judgment." That requires showing what you prioritized, what you cut, and what signal validated the launch.
Before: "Led a 6-person team through a 4-day buildathon from blank page to Product Hunt launch (Next.js, Supabase, custom brand system)"
After: "Led a 6-person team through a 4-day MVP sprint. Prioritized the verification gate and matching flow over chat and events features because trust was the top user need from 20+ discovery interviews. Launched on Product Hunt within the sprint."
Before: "Shipped 5 AI products in 6 weeks with full PRD discipline (discovery, problem framing, adaptive AI-scoring, working prototype), each grounded in real user research"
After: "Shipped 5 AI products in 6 weeks. Strongest example: [name one], where discovery with [N] users revealed [problem], leading to [specific product decision] that [outcome or early signal]."
The Featured AI Products Section: Too Many, Not Deep Enough
The resume lists 6 AI products with one-line descriptions. This breadth creates two problems:
- No single product has enough depth to be convincing. A hiring manager cannot tell which one was serious product work versus a weekend hack.
- The section looks like a project portfolio rather than product experience. PMs are judged on depth of ownership, not number of things shipped.
Pick your 2-3 strongest products and give them proper bullet structure. For each: what user problem, what product decision, what outcome or signal. The rest can go on a portfolio site.
The strongest candidates from this list:
- Gal Pal (already in Experience, good)
- Plan Karo Chalo (132 survey responses + 24 interviews shows research rigor, 91.7% activation is a real metric)
- PMPathfinder (44-person research base, solves a real problem)
The others (Bhojan, StoreOps, Signal) are interesting but dilute the narrative. They show speed but not product depth.
The Summary: No Proof, All Positioning
"Product Manager with 8 years across global financial services who now ships AI products end to end."
This is decent positioning. But it makes two claims with zero proof in the summary itself:
- "Ships AI products end to end" - which one? What outcome?
- "Strongest where regulated complexity, data, and user friction meet" - show one example in the summary.
Your summary is the one line a recruiter reads before deciding whether to keep reading. Generic claims get skipped. One specific proof point forces them to continue.
Before: "Product Manager with 8 years across global financial services...Strongest where regulated complexity, data, and user friction meet."
After: "Product Manager with 8 years across banking and insurance (TCS, Standard Chartered, Marsh McLennan) who now builds consumer and AI products. Reclaimed 30 FTE at Standard Chartered by automating CDD workflows. Launched a women-only community product from zero to 154 beta users with a human-verification model that blocked 100% of fake accounts. Strongest where regulated complexity and user trust intersect."
Dimension Scores Breakdown
Domain Expertise: 88%
The strongest dimension by far. Clear BFSI depth across banking and insurance with domain language used naturally: CDD, servicing, invoicing controls, compliance frameworks, regulatory workflows. The domain signal is earned through problem-specific bullets, not just listed. The gap: newer consumer and AI side projects broaden the story but dilute the BFSI anchor unless you frame BFSI as your core hiring advantage.
Leadership & Impact: 76%
Real ownership of operational problems with quantified outcomes. The founder work adds genuine end-to-end product signal. But most evidence is process transformation and business analysis rather than repeated ownership of product decisions, roadmap choices, or user-facing outcomes in a full-time PM role. The AI program bullets show speed and discipline but not yet durable product impact beyond coursework-style shipping.
Skills & Tools: 72%
Strong transferable PM craft is shown through discovery, requirements, backlog translation, process mapping, and engineering collaboration. Side projects make the tools section credible (Next.js, Supabase, PostHog, prototyping). The gap: several PM skills are listed more strongly than they are evidenced, especially roadmapping, experimentation, and analytics-driven iteration. The transition narrative is not explicit enough.
Experience & Background: 72%
The background tells a coherent story from insurance delivery to banking operations to transformation to product building. Recognizable brands help credibility. But you are still positioned as a transition profile because full-time titles are BA, process, and operations oriented. The mix of founder work, cohort program, and featured products creates ambiguity about what the primary PM experience actually is.
ATS Readiness: 88%
Passes: Standard headers, consistent date formatting, clean document structure, good keyword coverage for PM terms.
Warnings:
- Several acronyms without first-use expansion: BFSI, PWA, CDD, BAU, PRD, FTE
- PM keywords found in skills and projects but fewer are reinforced in recent full-time experience bullets. Keywords like roadmap, strategy, data-driven, go-to-market, iteration, trade-off, adoption, retention appear in the skills section but not in the Marsh or Standard Chartered bullets.
The keyword placement gap matters. ATS systems weight keywords in experience bullets more heavily than standalone skills sections. Your most PM-relevant terms need to appear in the context of your recent full-time roles, not only in projects and skills lists.
The Transition Candidate Paradox
This resume faces the classic transition_over_5yr challenge: you have more total experience than most PMs at your target level, but less PM-titled experience. This creates a positioning problem.
A 3-year PM with shipped features at a product company will often beat an 8-year operations leader with recent PM pivot work, not because they are better, but because their resume reads as PM from the first line to the last.
The fix is not hiding your operations background. It is reframing it as the foundation that makes your PM work better:
- "8 years understanding how complex regulated systems actually work" becomes an asset, not a liability
- "Discovery in banking operations" is the same skill as "user research for internal tools products"
- "Process standardization across 5 markets" is "multi-market product rollout" in PM language
The candidate who wins the PM role is not the one who erases their operations history. It is the one who makes that history sound like it was always building toward product ownership.
The 5 Changes That Would Move This Score
1. Rewrite the summary with one proof point from each world.
Add your strongest BFSI metric and your strongest product-builder metric. Give the recruiter two reasons to keep reading in the first 3 seconds.
2. Reframe Standard Chartered and Marsh bullets as product decisions.
For each bullet, add: what user problem, what you shipped (workflow, tool, framework), and what the user experienced differently afterward. Keep the FTE/efficiency metrics, but lead with the product artifact.
3. Cut Featured AI Products from 6 to 2-3 with structured bullets.
Pick the products with the strongest research base and real user signal. Give each one 2-3 bullets with the problem-decision-outcome structure. Move the rest to your portfolio site.
4. Make the transition narrative explicit in the document.
Add a headline or summary line that directly positions you: "Operations and transformation leader who now builds products. Moving from understanding how systems break to deciding what to ship next."
5. Evidence 3-4 PM skills from the skills section in experience bullets.
If you list "roadmapping," show a bullet where you made a roadmap decision. If you list "experimentation," show where you ran one. Unsubstantiated skills are invisible to both ATS and hiring managers.
The Pattern
This resume represents a strong variant of the operations-to-PM transition: someone with deep domain expertise and real builder energy who needs to reframe their narrative from "I improved processes" to "I made product decisions."
The underlying credentials are solid. BFSI domain depth that cannot be faked. Quantified outcomes at recognizable companies. A live product launched from zero. Genuine research-first habits. MBA from a top school.
The gap is not in what you have done. It is in how the resume tells the story. Right now, a hiring manager reading quickly would lean toward a phone screen for domain-heavy or transition PM roles, but not an automatic shortlist for mainstream PM openings. Closing that gap requires the resume to stop reading like a transformation lead and start reading like a PM who happens to bring transformation expertise.
The path from 74% to 82%+:
- Lead every bullet with the product decision or user problem, not the process change
- Prove PM skills in experience bullets, not just the skills section
- Cut breadth in the AI products section in favor of depth in 2-3 strongest examples
- Make the transition narrative explicit rather than leaving the recruiter to infer it
- Keep BFSI as your anchor advantage but frame it through the PM lens
Score your own resume to see how your product manager resume performs across all four dimensions.