Sample resume · fictional candidate
Product Manager Resume Example
A sample resume for a product manager with six years of experience, two in engineering and four in product. Each bullet follows problem, what shipped and the metric that moved, and a short "Products shipped" section shows judgement as well as output.
The sample, with notes
Karthik Reddy
Product Manager, B2B Payments
Bengaluru, India · karthik.reddy@example.com · linkedin.com/in/your-profile
Summary
Product manager with 4 years in B2B fintech after 2 years as a backend engineer. Owns the invoicing and collections product for a payments company serving about 9,000 small businesses. Strong in SQL and experiment design; works with design and engineering from discovery to launch.
Experience
Product Manager, Invoicing
Feb 2023 – PresentB2B payments company (about 1,200 employees) · Bengaluru
- Own the invoicing and collections product (2 engineering squads, 1 designer); set the quarterly roadmap with sales, support and finance.
- Shipped UPI payment links on invoices after 30 customer interviews showed bank-transfer reconciliation was the main pain; median days-to-paid fell from 19 to 12 for invoices using the links.
- Dropped a planned recurring-billing feature after a fake-door test drew interest from under 2% of eligible customers, and moved the team to payment reminders.
- Launched automated WhatsApp payment reminders; 41% of businesses switched them on within 3 months, and overdue invoices among them fell by about a quarter.
- Write a PRD with success metrics for every launch and review results at 30 and 90 days in a shared dashboard.
Associate Product Manager
Jun 2021 – Jan 2023Accounting software startup · Pune
- Owned the GST e-invoicing integration: turned schema changes into user stories and shipped before the compliance date for affected customers.
- Ran A/B tests on the onboarding checklist; activation (first invoice sent within 7 days) improved from 38% to 46%.
- Set up product analytics events with engineering and started the weekly product metrics review.
Software Engineer
Jul 2019 – May 2021IT services company · Pune
- Built Java backend services for a banking client; moved to product after leading requirement discussions with the client team.
Products shipped
- UPI payment links: Problem: slow, hard-to-reconcile bank transfers. Result: median days-to-paid 19 to 12 on invoices with links.
- Payment reminders: Problem: manual follow-ups by owners. Result: 41% adoption in 3 months.
- GST e-invoicing: Problem: a new compliance requirement. Result: shipped before the date with no launch-week escalations.
Skills
- Discovery: Customer interviews, fake-door tests, usability testing
- Delivery: PRDs, user stories, Jira, design reviews in Figma
- Data: SQL, Mixpanel, Metabase, A/B test design
- Domain: Payments, UPI, GST invoicing
Education
- B.Tech, Computer Science · 2019
Where the numbers in a resume like this come from
The figures above are made up, but each is a kind of number you can look up. Before you put one on your resume, find it in one of these places. If you cannot, describe the scope instead.
| Number | Where to find it |
|---|---|
| Adoption and activation | Product analytics events. |
| Business outcome (days-to-paid, conversion, retention) | Data-team dashboards. Note the comparison group. |
| Discovery volume | Your interview notes or research repository. |
| Delivery | Release notes and Jira. Avoid "shipped 40 features" unless the count means something. |
Adapting this example
- Moving from engineering, consulting or analysis: lead with product-like work you already do, such as requirements, experiments and customer calls.
- Consumer products: use retention cohorts, daily and monthly active users, and funnel conversion.
- Do not claim revenue for a whole product you did not own. Say what your feature changed and how it was measured.
- One discovery-to-result story per role is worth more than a list of features.