ATS KEYWORD ANALYSIS 1. Product Manager — primary title keyword, must appear in headline, summary, and first job title 2. Product Roadmap — core deliverable keyword, appears in 2+ experience bullets 3. Agile — methodology keyword, ATS filters heavily for this in tech PM roles 4. Stakeholder Management — soft skill that is hard-coded into most PM job descriptions 5. Go-to-Market — strategic keyword separating senior from junior PM profiles 6. User Research — shows customer-centricity, critical for product roles 7. OKRs — 2026 standard framework keyword for goal-setting in tech companies 8. Cross-functional Teams — appears in 90% of PM job descriptions 9. A/B Testing — data-driven decision making signal 10. Product Strategy — senior-level keyword that elevates the profile above execution-only candidates RESUME REWRITE [Full Name] | London, UK | [Phone] | [Email] | linkedin.com/in/[profile] PROFESSIONAL SUMMARY Product Manager with 6 years of experience driving B2B SaaS product development from concept to launch. Led the redesign of a core workflow feature that increased user retention by 34% and reduced churn by 18% within one quarter. Specialised in translating complex user research into prioritised roadmaps that align engineering, design, and commercial stakeholders. Seeking a senior product management role where deep customer empathy and data-driven prioritisation drive product strategy. WORK EXPERIENCE Senior Product Manager | [Company Name] | 2023 — Present - Owned the end-to-end product roadmap for the core dashboard feature serving 12,000 daily active users, delivering 3 major releases on schedule across 4 quarters - Led a cross-functional team of 8 engineers, 2 designers, and 1 data analyst to redesign the onboarding flow, reducing time-to-first-value from 14 days to 3 days - Increased user retention by 34% and reduced monthly churn by 18% through a data-driven feature prioritisation process grounded in 60 user interviews and quantitative cohort analysis - Introduced OKR framework across 2 product squads, improving sprint goal achievement rate from 61% to 84% in 2 quarters - Collaborated with the sales and marketing teams on go-to-market strategy for 2 product launches, contributing to 22% growth in new ARR in H2 2024 Product Manager | [Company Name] | 2021 — 2023 - Managed the product roadmap for a B2B invoicing feature used by 4,200 SMB customers, delivering 4 quarterly releases against business and user requirements - Conducted 40+ user interviews and 12 usability testing sessions to identify the top friction points in the payment flow, resulting in a 28% increase in payment completion rate - Partnered with the engineering team to reduce average bug resolution time by 40% by introducing a structured triage process - Defined and tracked product KPIs including activation rate, feature adoption, and NPS, presenting monthly performance reports to the C-suite Associate Product Manager | [Company Name] | 2019 — 2021 - Supported 2 senior PMs across a fintech platform serving 85,000 retail users - Wrote 30+ detailed product specifications and user stories for the development team - Ran A/B tests on 4 key conversion points in the onboarding flow, improving 30-day activation rate by 19% SKILLS Product Strategy, Roadmap Prioritisation, Agile and Scrum, User Research, A/B Testing, OKRs, Stakeholder Management, Go-to-Market Planning, Data Analysis, Jira, Figma, Mixpanel, SQL (working knowledge) EDUCATION BSc Computer Science | [University] | 2019 COVER LETTER Dear Hiring Manager, [Company Name] shipped three major product updates in Q1 2026 that collectively addressed the two pain points cited most frequently in your public user reviews — and reading the changelog, I recognised the same prioritisation thinking I use every day. I am a Product Manager with 6 years of B2B SaaS experience and a track record of improving retention and reducing churn through research-led product decisions. In my current role, I led a cross-functional team to redesign the core onboarding experience for a SaaS platform with 12,000 daily active users. The work started with 60 user interviews, narrowed to a clear problem statement, and ended with time-to-first-value dropping from 14 days to 3 — alongside a 34% improvement in user retention and an 18% reduction in monthly churn in the following quarter. That outcome came from saying no to 11 other roadmap items while the team focused entirely on one problem. The Senior Product Manager role at [Company Name] specifically calls for someone who can balance technical complexity with commercial outcomes while managing multiple stakeholder groups simultaneously — which is exactly the environment I have operated in for the past 3 years across engineering, design, sales, and executive teams. I would welcome the opportunity to discuss how I approach product strategy and what I would bring to this role. I am available for a conversation at your convenience. [Full Name] LINKEDIN PROFILE REWRITE HEADLINE OPTIONS Option A: Senior Product Manager | B2B SaaS | Retention and Growth | 6 Years Building Products Users Actually Keep Option B: Product Manager → Senior PM | Turning User Research Into Roadmaps That Reduce Churn | B2B SaaS ABOUT SECTION 34% retention improvement. 18% churn reduction. One product decision. I am a Product Manager with 6 years of experience building B2B SaaS products that people actually keep using. My work sits at the intersection of deep customer empathy and rigorous data analysis — I run user interviews, analyse cohort data, and use both to make prioritisation decisions that engineering, design, and commercial stakeholders can align behind. In my current role I own the roadmap for a core product feature serving 12,000 daily active users. The work I am most proud of is not a feature — it is the decision to stop building features for one quarter and instead fix the onboarding experience based on 60 user interviews. Time-to-first-value dropped from 14 days to 3. Retention went up 34%. Churn went down 18%. I am currently exploring senior product management opportunities at companies where product strategy is taken seriously and the team has the autonomy to say no to the wrong things. If you are building something in B2B SaaS and want to talk about product — connect with me. EXPERIENCE SECTION (Most Recent Role) Senior Product Manager | [Company Name] | 2023 — Present - Owned product roadmap for core dashboard feature serving 12,000 daily active users across 4 quarterly release cycles - Reduced time-to-first-value from 14 days to 3 days through a research-led onboarding redesign — improving retention by 34% and reducing churn by 18% - Introduced OKR framework across 2 product squads, improving sprint goal achievement from 61% to 84% - Partnered with sales and marketing on go-to-market strategy for 2 product launches contributing to 22% ARR growth in H2 2024 INTERVIEW PREPARATION Question 1: Tell me about a time you had to make a difficult prioritisation decision. WHY THEY ASK: Testing whether you have a structured prioritisation framework and whether you can defend decisions under pressure from stakeholders. YOUR ANSWER FRAMEWORK: Situation — competing roadmap requests from sales, engineering capacity constraints, and user research pointing in a different direction. Task — needed to align 3 stakeholder groups on a single Q3 priority. Action — ran a prioritisation workshop using RICE scoring, presented the data alongside 5 direct user interview quotes to make the human cost of the alternative visible. Result — aligned all 3 groups on the onboarding redesign, delivered the project, achieved 34% retention improvement. WHAT NOT TO SAY: Never say you made the decision alone. Interviewers want to hear stakeholder alignment, not unilateral decision-making. Question 2: How do you decide what not to build? WHY THEY ASK: Testing strategic thinking and whether you understand that product management is primarily about saying no. YOUR ANSWER FRAMEWORK: Describe your framework — user impact score, business value, development effort, strategic alignment. Give a specific example of a feature you killed and why. Show the outcome of that decision. WHAT NOT TO SAY: Never say you build what the customer asks for. This signals you do not have a prioritisation framework. Question 3: Walk me through a product you launched end to end. WHY THEY ASK: Testing whether you can own the full product development lifecycle, not just one phase of it. YOUR ANSWER FRAMEWORK: Use the onboarding redesign story. Discovery through user interviews, definition of the problem statement, roadmap prioritisation decision, collaboration with engineering and design, launch metrics, and the retention outcome. Cover every phase without being asked. WHAT NOT TO SAY: Do not make the story feature-focused. The interviewer wants to see process, not output. Question 4: How do you work with engineers who push back on your requirements? WHY THEY ASK: Testing collaboration style and whether you create psychological safety for engineering teams. YOUR ANSWER FRAMEWORK: Describe treating engineers as product partners not implementation resources. Give an example where engineer pushback led to a better solution. Show the outcome. WHAT NOT TO SAY: Never say you escalate to management when engineers push back. This is a red flag for senior PM roles. Question 5: Where do you want to be in 3 years? WHY THEY ASK: Testing ambition alignment with the role and company trajectory. YOUR ANSWER FRAMEWORK: Head of Product or VP Product at a company where you have built something meaningful from the ground up. Connect this directly to what this role would teach you. Show you have thought about your career trajectory, not just the next step. WHAT NOT TO SAY: Never say you want to be a founder. This tells the interviewer you are using this role as a stepping stone. SALARY NEGOTIATION SCRIPT When they make the offer: Thank you — I appreciate the offer and I am genuinely excited about this opportunity. Before I respond formally, can I take 24 hours to review the full package? Counteroffer delivery: I have reviewed the offer carefully. Based on my research into the market rate for this role in this location and the scope of what we discussed, I was expecting something closer to [10-15% above their number]. Is there flexibility in the base to get to that range? If they push back: I understand there are budget constraints. If the base is fixed at [their number], could we discuss an accelerated review at 6 months tied to specific performance targets? That would give me confidence that the compensation will reflect the impact I am expecting to make. The close: I appreciate you working through this with me. I am committed to making this role a success and I am looking forward to starting. Can we confirm the start date and get the offer in writing by [specific date]?