Resume Teardown #27: Fintech BA With Real Product Ownership but Still Reads Like a Business Analyst

Madhava Narayanan·June 8, 2026·8 min read

resume teardownproduct managementresume tipsBA to PMcareer transition

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 Business Analyst at a fintech company with 4 years of product-adjacent work scored 66%. The resume has real product ownership signals: shipped KYC journeys, a business rule engine POC that won a client, 7% growth from new loan features, and 12% efficiency gains from CRM enhancements. But it still reads like a BA resume rather than a PM resume. Bullets describe what was implemented rather than what product decision was made, the Responsibilities section is generic filler, and there is no clear PM transition narrative tying the experience together.

The Resume

Background: Senior Business Analyst at a fintech/lending company (Aug 2024 - Present). Previously Business Analyst (Product Management) at a credit marketplace (Dec 2023 - May 2024). Project Associate at an engineering research institute (Apr 2023 - Nov 2023). Business Analyst at a low-code/no-code startup (Mar 2022 - Nov 2022). Brief sales trainee stint at an edtech company (Feb 2022 - Mar 2022). B.Tech in Computer Science.

What looked good on the surface: Deep fintech domain exposure across lending, KYC, collections, CRM, and business rule engines. Real shipped features with metrics (7% growth, 12% efficiency, 60% more audits, 50% manual reduction). A Japanese client POC win. Clear progression toward product-adjacent work.

Score: 66%

The Core Strength: You Have Real Product Ownership

This is not a BA who only wrote documents and attended meetings. The resume shows genuine end-to-end feature delivery in a complex fintech environment:

"Drove 7% growth by implementing 'Pay to Co-Applicant' and 'Top-Up' features via structured APIs for unsecured loans."

This bullet works. It names the features, shows the delivery mechanism (APIs), and quantifies the business outcome. A PM hiring manager reading this thinks: "This person shipped lending products and moved a metric."

"Secured a Japanese client by delivering a successful POC and onboarding process for the Business Rule Engine product."

This shows product judgment beyond just execution. You identified an opportunity, delivered a POC that won the deal, and onboarded a new market. That is product ownership.

These signals are what make the BA-to-PM transition credible. The problem is that they are buried among weaker bullets that dilute the PM narrative.

The Core Problem: Implementation Language, Not Product Language

Most bullets on this resume describe what was built rather than what decision was made and why. The resume consistently answers "what did we ship?" but not "why did I choose this approach?" or "what user or business problem was I solving?"

"Revamped the entire customer primary Information and KYC screens across all businesses, by implementing a system-driven KYC journey, utilizing API-based fetching to minimize manual data errors."

This bullet describes the technical approach (API-based fetching, system-driven journey) but not the product problem. What was wrong with the old KYC flow? Were users dropping off? Were agents spending too much time on manual entry? Did error rates cause compliance issues?

The fix pattern for every bullet: Add the problem or outcome. "Reduced KYC completion time by X% by redesigning the journey from manual data entry to API-based fetching, eliminating [N] manual steps across all business lines."

Same work. But now it reads like a product decision rather than a system change.

The Responsibilities Section: Delete It

The resume has a standalone "Responsibilities" section that lists generic activities:

"Analyzing competitor products and implementing the similar features for existing products"
"Collaborating with a cross functional team for product discovery, solution discovery, delivery, and for distribution"
"Facilitating Sprint planning, Scrum Meetups, and Sprint retrospective meetings"
"Performing UAT and reporting bugs"

Every line here weakens the resume. These are activities that any BA/PM does. They take space from specific, outcome-driven bullets that would actually differentiate the resume. A recruiter reads this and thinks "job description copy-paste."

The fix: delete the entire section. If any of these activities led to a specific outcome worth mentioning, fold that outcome into a role bullet. "Competitive analysis" becomes "Identified [feature] from competitor analysis, drove implementation, resulting in [metric]." Generic ceremony facilitation adds zero value.

The CKYC Bullet: Good Work, Missing Judgment

"Integrated the CKYC 'No-Fetch' process using mobile number OTP verification and OVDs to obtain customer consent and seamlessly retrieve CKYC numbers."

This shows solid execution in a regulated fintech environment. But a PM hiring manager will ask: Why this approach? Was there an alternative? What was the conversion rate for consent capture? How many customers were previously blocked because CKYC fetch failed?

For BA-to-PM transitions, the key differentiator is showing product judgment, not just delivery competence. You can delivery scope. The question is: can you make product decisions?

Before: "Integrated the CKYC 'No-Fetch' process using mobile number OTP verification and OVDs to obtain customer consent and seamlessly retrieve CKYC numbers."

After: "Designed the CKYC consent flow using OTP verification over alternative approaches [X and Y] because of higher completion rates. Achieved [N%] consent capture rate, unblocking CKYC retrieval for [N] customers previously stuck in manual processing."

The AI Call Audit Bullet: Metric Without Context

"AI-powered call audit integration, enabling 60% more audits."

60% more audits is a strong number. But a hiring manager cannot tell what your role was. Did you:

Define the audit rules the AI would check?
Select the vendor from multiple options?
Redesign the reviewer workflow around AI outputs?
Identify that audit coverage was a problem in the first place?

Any one of these would make this a PM-quality bullet. Without that context, it reads as "I was on the project that integrated an AI tool." Integration work is BA territory. Product decisions about how and why to use AI are PM territory.

Before: "AI-powered call audit integration, enabling 60% more audits."

After: "Identified that manual audit coverage reached only [X%] of calls. Evaluated AI audit vendors, defined audit quality criteria, and drove integration. Increased audit coverage by 60%, improving QA visibility across the collections team."

The Missing PM Transition Narrative

The resume opens with: "Product-minded Business Analyst with 4 years shipping B2B fintech products." This is a decent positioning statement. But the rest of the resume does not support the "product-minded" claim consistently.

A strong BA-to-PM resume tells one story: "I started in BA roles, but I consistently took on product ownership. Here is the evidence."

Right now, the resume reads as a chronological list of BA roles with some PM-adjacent highlights mixed in. The reader has to hunt for the PM signals. They should be unmissable.

Three structural changes that would fix this:

Summary: Add your strongest metric. "Product-minded Business Analyst with 4 years shipping B2B fintech products. Drove 7% growth through new lending features, won a Japanese client through a BRE product POC, and improved agent efficiency by 12% through CRM automation."
Role framing: Each role should open with a one-line product ownership statement, not a product name list. "Owned the KYC and onboarding product experience across all business lines" rather than "Product Name: BRE, KYC, LOS, Unsecured Loans."
Consistent PM language: Replace "Integrated" with "Defined requirements and drove integration." Replace "Implemented" with "Identified [problem], designed [solution], shipped [feature]." The underlying work is the same. The framing makes the difference.

Certifications: Undated Means Uncredited

The certifications section lists:

Product Management: Building a Product Roadmap (LinkedIn Learning)
Professional Diploma in Pricing Analysis and Management (Udemy)
Enterprise Design Thinking Practitioner (IBM)

These are good PM-readiness signals for a transition candidate. But without completion dates, a recruiter cannot tell if these were done last month or three years ago. Recent PM learning is a signal of intent. Undated certifications carry almost no weight.

Add the year to each certification. If they are recent (within the last 12 months), move them higher on the resume or reference them in the summary.

Dimension Scores Breakdown

Domain Expertise: 78% The strongest dimension. Clear, demonstrated fintech depth across KYC, CKYC, V-KYC, LOS, BRE, CRM, collections, unsecured loans, and lending workflows. Domain terminology is used naturally, not just listed. The gap is breadth: all experience is in lending operations and workflow design. Broader fintech product exposure (pricing, risk models, funnel conversion, portfolio metrics) is not shown.

Leadership & Impact: 68% Real shipped features with outcomes (7% growth, 12% efficiency, 50% manual reduction, Japanese client win). But many bullets describe implementations without the product decision or problem that was prioritized. The Responsibilities section pulls this score down by signaling "process participant" rather than "owner."

Skills & Tools: 65% Solid PM-adjacent craft: requirements gathering, API integrations, UAT, wireframing, stakeholder alignment, vendor coordination. Relevant tool stack (SQL, Postman, Figma, Jira, Confluence, Power BI). But most PM skills are asserted in the skills section rather than demonstrated in bullets. Roadmap ownership, prioritization decisions, and user research are listed, not shown.

Experience & Background: 64% Forward momentum is clear (most recent role is the strongest and most relevant). But title history is BA-heavy, with multiple shorter stints that are not clearly connected into a deliberate PM progression. The very brief edtech sales role and the research institute stint create noise in the narrative.

ATS Readiness: 70%

Passes: Standard section headers, consistent date formatting.

Warnings:

Multiple unexpanded acronyms on first use (LOS, BRE, CRM, LMS, UAT, CKYC, V-KYC, OVDs, PTP)
Inconsistent spacing and capitalization; fragments like "Conception & Integration" read awkwardly
PM keywords found in the skills section but weakly placed in experience bullets. Keywords like prioritization, strategy, metrics, launch, go-to-market, trade-off, adoption, retention, experimentation are either missing or only in the skills list

The keyword placement issue is critical. ATS systems weight keywords in experience bullets 2-3x higher than keywords in a standalone skills section. This resume has PM-relevant keywords, but they live in the wrong place.

The 5 Changes That Would Move This Score

1. Rewrite the summary with a proof point.

Before: "Product-minded Business Analyst with 4 years shipping B2B fintech products - LOS, BRE, KYC, CRM, Calling, Low-Code, No-Code. Proven ability to design digital journeys that put the human at the center."

After: "Product-minded Business Analyst with 4 years shipping B2B fintech products across lending, KYC, and CRM. Drove 7% unsecured loan growth through new payment features, won a Japanese enterprise client through a successful BRE product POC, and improved collections agent efficiency by 12% through CRM automation. Comfortable owning the full product lifecycle from discovery and wireframing to API integration, UAT, and stakeholder alignment."

2. Delete the Responsibilities section entirely.

It adds no value. Fold only the strongest items into specific role bullets with outcomes. "Analyzing competitor products" becomes a real bullet only if you can name what you found and what it led to.

3. Add the product problem to every implementation bullet.

Pattern: [Problem you identified or were solving] + [What you shipped] + [What changed].

Before: "Integrated a third-party V-KYC solution across lending and investment journeys to automate low-risk classification."

After: "Reduced manual verification load by automating low-risk KYC classification through a third-party V-KYC integration across lending and investment journeys, cutting processing time by [X%] for [N] daily applications."

4. Add dates to certifications and consolidate the early roles.

Date every certification (year of completion)
The edtech sales trainee role (1 month) adds noise. Either remove it or compress to a single line: "Business Development Trainee (1 month): Full-cycle sales pipeline management for K-12 products, 7 conversions."
The research institute role could be one line: "Project Associate: Data operations using Python web scraping, reducing manual entry by 50%."

Use the recovered space for richer bullets in your current fintech role.

5. Reframe the current role opening around product ownership.

Before: "Product Name: BRE, KYC, LOS, Unsecured Loans"

After: "Owns the KYC onboarding experience, Business Rule Engine product, and unsecured lending features across all business lines. Serves internal lending operations and external clients (including a new Japanese enterprise client won through POC delivery)."

This immediately signals scope and ownership rather than reading as a product list.

The Pattern

This resume represents the most common BA-to-PM transition archetype: someone doing genuine product-adjacent work (requirements to release, stakeholder management, feature delivery) but writing about it in BA language instead of PM language.

The underlying work is strong for a transition candidate. You are not just writing BRDs and attending ceremonies. You are shipping lending products, winning clients, moving metrics, and coordinating across engineering, compliance, and operations. That is real product work.

The gap is purely framing. Every bullet needs to shift from "what was implemented" to "what problem I identified, what I decided to build, and what changed." The 7% growth bullet proves you know how to write a strong product bullet. Apply that same structure to every other line.

The path from 66% to 75%+:

Add outcome context to every implementation bullet
Delete the generic Responsibilities section
Strengthen the summary with your best metric
Add certification dates
Consolidate early roles to make space for richer current-role content
Use PM language (defined, prioritized, identified, shipped) instead of BA language (integrated, implemented, mapped)

The fintech domain depth and real shipped outcomes give you a strong foundation. The resume just needs to stop reading like a BA and start reading like a PM who happens to have a BA title.

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