What you're walking into:

• Product runs as two lean squads, each led by a PM, with the Head of Product across both. You'd own one of them outright.
• Your squad: seven engineers and a dedicated designer, with data science and analytics specialists sitting alongside you rather than in another building. There's no BAs, no delivery managers, no analyst producing your morning report.
• You set the direction, write the requirements and drive the build; with a fellow PM running the other squad as a peer to collaborate with, not a layer above you.
• Five or six initiatives run in parallel, on a sprint cadence. The rhythm: start in the numbers you pulled yourself. Spot what moved, work out why, size the upside, write the requirements, ship it this sprint, measure it next. Go again.

Who this suits:

• A PM currently operating at pace, several initiatives on your plate right now, shipping on sprint timelines, and specific about what's live this week
• Someone who has owned a consumer journey end to end, application, onboarding, checkout or activation, and carried the numbers, not just the delivery
• Self-sufficient in data: SQL or equivalent (Python, Looker, Tableau, Power BI), you interrogate your own numbers before anyone briefs you
• A doer by habit: you write the requirements, sit with the engineers, test the edge cases, make the call
• Commercially fluent: you can say what your work did to revenue, margin or quality, not just to a conversion rate
• Someone who drives a squad by creating momentum, collaborative, never passive
• Domain background in credit, fintech or payments helps, but pace and ownership beat domain here, people have joined without it and learned fast
•