resume & cv for pm roles

A recruiter at Flipkart told me she screens 50 resumes a day. She spends six seconds on each one in the first pass. Six seconds. That is not enough time to read your summary paragraph. It is barely enough time to scan your last two roles and decide whether to keep reading.

Your resume is not a document. It is a filter. And most PM resumes fail the filter — not because the candidate lacks experience, but because the resume is structured for the writer, not the reader.

I have reviewed thousands of PM resumes through Pragmatic Leaders. The failure modes are remarkably consistent. This page covers exactly what works, what does not, and why.

The 6-second scan

Here is what actually happens when a hiring manager opens your resume:

1. Name and current title — Are you a PM or something adjacent?
2. Last company — Do I recognize it? Is it relevant?
3. Last two bullet points — Did you ship something measurable?
4. Education — Quick credibility check (especially in India, where college brand still matters more than it should).

That is it. If those four elements do not create interest, the resume goes into the reject pile. Your carefully crafted third-page section on “hobbies and interests” never gets seen.

One page. No exceptions.

Keep your resume to one page. This is not arbitrary. It forces prioritization — which is the single most important PM skill. If you cannot prioritize what goes on your own resume, why would I trust you to prioritize a product roadmap?

I hear every objection:

• “But I have 12 years of experience.” — Great. Pick the best four years and make them count.
• “But my MBA projects are relevant.” — Maybe one of them is. Not all six.
• “But I worked at five companies.” — Then give the first two companies one line each and the last two companies real estate.

The only exception is if you are applying to companies outside India where a two-page CV is the cultural norm (parts of Europe, some government roles). For every Indian tech company, every startup, and every US-based company: one page.

The structure that works

Here is the exact layout, top to bottom:

Header (2 lines)

Name — make it large enough to be an identifier. Your name is the one thing the recruiter uses to remember you during debrief.

Contact line — Email, phone, LinkedIn URL. That is it. Skip your postal address. Nobody is mailing you a letter. Skip your date of birth (Indian resumes still do this — stop). Skip your photograph unless the company specifically asks for one.

Summary (2 lines maximum — or skip entirely)

If you include a summary, it must be two lines of specific impact, not a generic objective statement.

Bad: “Result-oriented product manager with 7+ years of experience in driving product strategy, leading cross-functional teams, and delivering customer-centric solutions in fast-paced environments.”

That sentence describes every PM on earth. It tells the reader nothing about you.

Good: “PM with 7 years in fintech (Razorpay, PayRight). Shipped a merchant onboarding redesign that cut activation time from 3 days to 4 hours. Currently building lending products for 200K+ SMBs.”

The good version has a domain, specific companies, a specific achievement, and a specific current focus. In two lines.

If you cannot write a summary this specific, skip the section entirely. A missing summary is better than a generic one.

Experience (the bulk of the page)

This is where most resumes fail. People write their experience section as a list of responsibilities. Responsibilities are the job description. The company already knows what PMs do. What they want to know is: what did you do that someone else in the same role might not have?

Structure each role as:

Company Name — Role Title                      Duration

Then three to five bullet points, each following the XYZ format:

Achieved [X outcome] by [Y action], resulting in [Z metric].

This is not optional. This is the format that works. Every bullet point should answer: “What changed because this person was in the room?”

XYZ bullets: good vs bad

Bad bullet points (activity-based):

• Managed the product roadmap for the payments vertical
• Collaborated with engineering, design, and QA teams
• Conducted user research and presented findings to stakeholders
• Owned the sprint planning and backlog grooming process

Every one of these describes a process, not an outcome. The reader learns what you did every day. They do not learn what you achieved.

Good bullet points (outcome-based):

• Reduced payment failure rates from 12% to 4.5% by identifying and fixing a retry logic gap in the UPI flow, saving approximately Rs 3.2 crore in monthly failed transactions
• Launched a merchant self-serve dashboard used by 14,000 merchants in the first quarter, reducing support tickets for settlement queries by 40%
• Designed and shipped a dynamic pricing engine for subscription plans, increasing average revenue per merchant by 22% within six months
• Cut onboarding drop-off from 34% to 11% by replacing a 14-field form with a progressive disclosure flow validated through 20 merchant interviews

Each bullet has a number. Each bullet has a specific action. Each bullet has a measurable result. The reader can see judgment, execution, and impact in every line.

What if you do not have metrics?

This is the most common excuse: “My company did not track metrics” or “I was not given access to analytics.”

Here is the thing — you still had impact. You just need to reframe:

• Cannot quantify revenue impact? Quantify effort saved: “Reduced manual reporting time from 8 hours per week to 45 minutes by automating the dashboard.”
• Cannot share exact numbers due to NDA? Use percentages or relative terms: “Improved conversion by 2.3x” instead of “Improved conversion from 1.2% to 2.8%.”
• Worked on internal tools? Quantify adoption: “Built an internal tool adopted by 85% of the operations team within two weeks of launch.”
• Early in your career? Quantify scope: “Led the integration of 3 payment gateways serving 50,000 daily transactions.”

There is always a number. You just have to look harder.

Education (2-3 lines)

College, degree, year. If you are from an IIT, NIT, BITS, or IIM, the brand does work in your favor in the Indian market — put it there. If you have a PM certification (Pragmatic Leaders, ISB, or similar), include it. If your graduation year is more than 10 years ago, the education section should be the smallest section on your resume.

Do not list your 10th and 12th board scores. Nobody cares after your first job.

Skills / Tools (1 line)

A single line: SQL, Amplitude, Mixpanel, Figma, Jira — whatever is true. Do not list “leadership” or “communication” as skills. Those are demonstrated through your bullets, not listed in a section.

The mistakes that get you rejected

After reviewing thousands of resumes, these are the patterns I see most often in Indian PM resumes. Each one is a filter failure.

Mistake 1: The responsibility dump

Listing what your job description says you do. “Responsible for product roadmap” is not an achievement. It is the minimum expectation of any PM. If you are listing responsibilities, you are telling the recruiter you showed up to work. That is not enough.

Mistake 2: Keeping metrics separate from roles

Some resumes have a “Key Achievements” section separated from the work experience section. This forces the reader to mentally map “which achievement came from which role?” Do not make the reader do work. Put your achievements inside each role, as bullet points.

Mistake 3: The two-page-plus resume for less than 10 years

If you have under 10 years of experience and your resume is two pages, you have a prioritization problem. Cut. Be ruthless. That internship from 2014? Gone. That college project? Gone. The three-line description of your first job? One line.

Mistake 4: Generic summary that could be anyone

“Passionate product manager with experience in agile methodologies.” That describes 50,000 people on LinkedIn. If your summary does not mention a specific domain, a specific company, or a specific outcome, delete it.

Mistake 5: Poor grammar and formatting in India-specific ways

This is uncomfortable but true: I have rejected resumes based on grammar alone. If the role requires clear written communication — and every PM role does — then your resume is the first writing sample. Misplaced commas, inconsistent tense, “handled” in one bullet and “handling” in the next — these signal carelessness. In India specifically, watch for: mixing British and American spellings, using “the same” as a pronoun (“I worked on the project and improved the same”), and the word “utilize” where “use” works perfectly.

Mistake 6: The “tech stack as identity” trap

Engineers transitioning to PM often list every technology they have worked with. Your resume is not a stack trace. The hiring manager does not need to know you worked with Kafka, Redis, PostgreSQL, React, and Kubernetes. They need to know what you built with those tools and what outcome it produced. One line of tools in a skills section is sufficient.

Tailoring for the role

A single resume sent to 30 companies is a strategy for getting ignored by 30 companies. Tailoring does not mean rewriting your entire resume for each application. It means adjusting emphasis.

If you are applying to a growth PM role, lead with your growth bullets — activation, retention, funnel optimization. Push your infrastructure or platform bullets down.

If you are applying to a B2B SaaS company, emphasize enterprise metrics — ARR impact, churn reduction, customer adoption. Your consumer metrics (DAU, engagement) are less relevant.

If you are applying to an early-stage startup, emphasize speed and breadth — “launched in 6 weeks with a team of 3” matters more than “managed a team of 12 across three pods.”

Read the job description. Find the three skills they emphasize most. Make sure your top three bullets demonstrate exactly those skills.

The resume-to-interview pipeline

Your resume does not get you the job. It gets you the interview. And every line on your resume should serve one of two purposes:

1. Pass the filter — Give the recruiter a reason to move you to the next stage.
2. Seed the conversation — Plant specific achievements that the interviewer will ask about.

That second purpose is underrated. If your resume says “Reduced checkout abandonment from 34% to 19% by redesigning the address capture flow for Tier 2 users,” the interviewer will ask about it. And when they do, you are now telling a story you have already rehearsed, on territory you have chosen.

This is resume-as-strategy. You are not documenting your past. You are designing the interview conversation in advance.

A note on ATS and keywords

Large Indian companies — Flipkart, Swiggy, PhonePe, Meesho — use applicant tracking systems that scan for keywords before a human ever sees your resume. This does not mean you should stuff your resume with buzzwords. It means you should use the exact language from the job description where it naturally fits.

If the JD says “product discovery,” do not write “user research” — write “product discovery.” If the JD says “merchant lifecycle,” do not write “client journey” — write “merchant lifecycle.” Same concept, different words. The ATS matches strings, not meanings.

But never sacrifice clarity for keyword matching. A bullet point that reads naturally and contains the right terms will always beat a bullet point that sounds like it was written for a robot.

The uncomfortable truth about PM resumes in India

The Indian PM job market has a specific dynamic that nobody talks about openly: there are more aspiring PMs than there are PM roles. The supply-demand mismatch means hiring managers can be ruthless with the filter. A resume that would get a callback in a less competitive market gets rejected in India simply because 200 other people applied to the same role.

This is not a reason to inflate your resume. It is a reason to be precise. Every word earns its place or gets cut. Every bullet demonstrates judgment, not just activity. Every section is structured for the six-second scan, because that is the reality of how your resume will be read.

The people who get interviews are not always the most experienced candidates. They are the ones whose resumes make it easy for a tired recruiter, at 4 PM on a Friday, scanning their 47th resume of the day, to see in six seconds that this person shipped real things that had real impact.

Make it easy for them. That is the entire game.

Where to go next

• Build your search system: Job Search System — the operational playbook for landing PM roles in India
• Optimise your LinkedIn: LinkedIn for PM — your profile is your second resume
• Prep your introduction: Tell Me About Yourself — the first 90 seconds of every interview
• Company-specific prep: Company-Specific Prep — Amazon, Google, Flipkart, and startup interviews each need different preparation