In short
Most product managers' resumes read like release notes: launched this, shipped that. A head of product reading one wants something else. What did the product do for the people using it, what did that mean for the business, and what did you decide not to build? Below is a senior Product Manager's resume, what each section is doing and why, then his headline, a letter opening and who he'd message.
Daniel is an invented product manager. His resume follows FutureDay's rule: every outcome is one his product actually had, and nothing is dressed up to look bigger. Watch for the line about the app he stopped. It's the one most product managers' resumes leave out.
A product manager's resume, start to finish
DANIEL KOWALCZYK
Senior Product Manager | Civic & Government Platforms | 64 councils, 2.3M transactions a year
Canberra ACT · daniel.kowalczyk@email.com · 0400 000 000 · linkedin.com/in/danielkowalczyk
Summary
Product manager for a platform residents use to book, apply and pay their local council: 64 councils, 2.3 million transactions a year, and a team of 14 engineers and designers. Took online completion of permit applications from 41% to 68%, which took around 30,000 phone calls a year off council phone lines.
Spends as much time deciding what not to build as what to build. Stopped a mobile app that research showed few residents would install, and put the money into the web forms nine in ten residents actually use.
Career highlights
- Lifted online completion of permit applications from 41% to 68% in a year by cutting the form from 14 steps to 6 after watching 30 residents try to finish it, removing around 30,000 phone calls a year from council customer service teams.
- Stopped a planned native app after research showed only 4% of residents would install it for a once-a-year task, moving $900K into accessibility and the web forms; the platform met WCAG 2.1 AA for the first time.
- Took a pet registration and payments module from first interview to 22 councils in 18 months, now earning $1.6M a year in recurring revenue.
Experience
Senior Product Manager, Parkline Civic Software 2021 to now
Resident bookings, permits and payments. 64 councils, 2.3M transactions a year, $11M revenue. Two squads, 14 people. Reports to the Head of Product.
- Cut payment failure at checkout from 6.2% to 1.8% by adding saved payment methods and automatic retry, recovering $1.1M a year in council fees that used to need a follow-up letter.
- Moved the team from quarterly to fortnightly releases, with council-reported defects down 45% in the first year.
- Set up an advisory group of 12 councils who review every major change before release; renewals across the customer base have held at 97% since.
- Wrote the product case behind a $2.4M state-wide contract covering 18 regional councils.
Product Manager, Moorhen Insurance 2017 to 2021
Online claims for home and motor insurance, 180,000 claims a year.
- Rebuilt online claim lodgement, lifting the share of claims lodged online from 22% to 57% and cutting time to first contact from three days to four hours.
- Ran around 40 experiments a year on the claims journey; claim satisfaction rose from 6.8 to 8.1 out of 10.
- Retired three old claim forms that cost $380K a year to maintain, after showing fewer than 2% of claims used them.
Earlier career
Business analysis and user research roles in financial services and consulting, including Senior Business Analyst at Coppins Advisory and UX Researcher at Ferncastle Digital.
Education and training
Bachelor of Information Technology
Graduate Certificate in Human-Centred Design
Tools and skills
Jira, Productboard, Amplitude, Figma · Discovery and usability research · Accessibility (WCAG) · Payments · Government procurement · Prioritisation and roadmaps
- HeadlineProduct and scale, no tech. What he owns, who it's for, and how much it's used. The technology belongs on an engineer's resume. A product reader wants the people and the volume.
- SummaryWhat changed for users. 41% to 68% is what changed for residents. 30,000 fewer phone calls is what it meant to the customer paying for the product. The second paragraph shows judgement, which is what a senior product hire is really for.
- HighlightsA decision not to build counts. The second highlight is something he stopped, and what the money did instead. Saying no well is one of the hardest product skills to prove, and it's rare to see it written down.
- Scope lineSize the product. Customers, volume, revenue, team, and who he reports to. A reader can tell the weight of the role before the first bullet.
- BulletsShipping is not the result. Fortnightly releases only earns a line because defects fell. Every bullet says what the change did, not just that it went out.
- Earlier careerThe research roots. Business analysis and research show where his habit of watching users comes from, and no year is given.
- ToolsPractices as well as tools. The tools a product job description names, plus the practices that matter for this kind of product. Accessibility carries real weight with a government buyer.
What does a head of product look for in a product manager?
A head of product is asking: do you know who uses this, did their behaviour change because of you, and can you say no? A resume that's a list of launches answers none of those. One that shows a number moving for users, and one thing you chose not to build, answers all three.
Before: "Owned the product roadmap and worked with engineering to deliver new features."
After: "Cut payment failure at checkout from 6.2% to 1.8% by adding saved payment methods and automatic retry, recovering $1.1M a year in council fees that used to need a follow-up letter."
How should a product manager's LinkedIn headline read?
Role, the product or domain, then what it does at scale. For Daniel, that's:
"Senior Product Manager | Civic & Government Platforms | 2.3M resident transactions a year"
Not "Product leader | Agile | Customer obsessed". It describes how half the profession talks, and says nothing about what he's built.
How should a product manager's cover letter open?
With a decision and what it led to:
"Your residents are still ringing to ask where their application is up to. On a platform used by 64 councils, I cut the permit form from fourteen steps to six after watching thirty residents try to finish it, and online completion went from 41% to 68%."
Then close on the problem you'd want to take on in their product, and why that one.
Who should a product manager talk to first, and what do they say?
Senior product roles often go to someone the head of product or an engineering lead already knows. The resume earns its keep in the second conversation. The first one is down to you.
The people a Product Manager should talk to first:
- Engineers and designers you've built with. When a team they're on needs a product manager, they're often asked who they'd want. A lead engineer who says your name carries a lot of weight.
- Your customers. The people on Daniel's council advisory group talk to every vendor in their market. They know who's building what, and who's struggling to.
- The Head of Product or Chief Product Officer at software companies selling into the same kind of customer. At a smaller company, it's the founder or CEO.
Make the first message short, with a small ask. To an engineering lead he used to work with:
"Hi Anjali, congratulations on the new role, the payments work your team shipped looks great. I'm starting to look at what's next after five years at Parkline, ideally a senior product role on something people use every day. If your team or anyone you know is hiring for product, I'd love a quick chat. Happy to help with anything on your side too."
Many of these roles are never advertised at all. Here's what the hidden job market actually is.
Where FutureDay fits in a product manager's search
FutureDay builds your resume from your own history, as it would Daniel's, and tailors it to every job description without adding anything you didn't do. Each day it also shows you who to contact, what to say, and what to do next.
In summary
Lead with what changed for users, then what it meant for the business.
A launch is only a line if you say what it did.
Show one thing you decided not to build.
Leave the tech stack to the engineers.
Most of the search is starting conversations. The resume is what follows one.