Product Owner

About the role

When someone dies, their family inherits a mountain of admin. A will is the single most useful thing that makes it smaller, but only if it’s correct, current and actually says what the person meant. Making sure we build the right thing to clear that bar is your job.

As a Product Owner, you’ll own the product for one of our product areas, assigned as the team fills out. You’ll talk to families, advisors and our legal specialists, decide what matters most, and write specs precise enough that an engineer, or an engineer with an agent, can build from them without guessing.

Then you’ll stay with it: in the PR, in the release, in the data afterwards. You’ll have real say over the roadmap, not just its order.

The team

Product is a small team working across engineering. You’ll be embedded with a team, side by side with its lead and engineers every day, and you’ll set direction with them rather than hand it over a wall.

We work in small, stable teams that own a product area end to end, from the first conversation with legal to the alert that fires if it breaks. Nobody hands you a ticket and walks away. Teams decide how to solve the problems in front of them, and often which problems are worth solving at all. Decisions are written down, reviewed kindly and revisited when we learn something new.

We’re AI-native. Frontier models, best-in-class agentic tooling, and nobody counts tokens. That pushes the job away from boilerplate and towards the parts that need a person: architecture, judgement, and getting the detail right. We ship to production 20+ times a day across 7+ services. Specs aren’t paperwork here. A precise one is what lets an engineer ship in a day; a vague one costs a week.

What you’ll do

Most weeks are a mix of listening, deciding and writing. Some of the work you’ll pick up:

• Own the roadmap for your area: what we build, what we don’t, and the reasoning, in writing.
• Write specs and acceptance criteria that leave nothing to guess. Here, the edge cases are the product.
• Spend real time with the people who use what we build: families, advisors and Estate Planning Consultants.
• Work with legal specialists to turn regulation and process into clear, testable rules.
• Measure what shipped, and be the first to say when something didn’t work.
• [ROLE-SPECIFIC RESPONSIBILITY]

What you’ll ship in your first 90 days

• [ ]Week one: sit in with advisors or Estate Planning Consultants and watch the product used for real.
• [ ]Own your team’s backlog and write the next 30 days of specs.
• [ ]Ship your first feature end to end, from problem statement to the numbers afterwards.
• [ ][90-DAY OUTCOME]

What we’re looking for

We care more about how you approach problems than a list of keywords. That said, here’s what tends to make someone successful in this role.

What you’ll work with

planning  = "linear"
design    = "figma"
comms     = "slack"
docs      = "google workspace"
analytics = "posthog"
agents    = ["claude", "whatever you're fastest in"]
cadence   = "20+ prod deploys / day"            # your specs ship fast

The honest bits

Every role has them. Better you hear it from us.

ratio

There are more teams than product people right now. You may own more than one area while we grow.

specs

Engineers here move quickly with agents. A gap in your spec turns into a gap in production faster than you’d expect.

regs

Regulated, sensitive data. Some changes need a second pair of eyes from legal, and that’s on purpose.

pace

We ship often, but “move fast and break things” isn’t an option when the thing is someone’s will.

You’ll probably enjoy this if

• +You’d rather understand the problem properly than ship the first idea.
• +You enjoy saying no, and explaining why.
• +You can talk about death plainly. Our users are planning for it or living through it.

Don’t tick every box? Apply anyway. We hire for how you think, not a checklist.

What we offer

Listed, not teased. If something matters to you and isn’t here, ask in your first call.

holiday

27 days + bank holidays + your birthday

pension

3% contribution

working pattern

Hybrid. In the office Tuesday to Thursday at Monument, London

contract

Permanent

learning

Time carved out for it, plus budget agreed case by case

a will, on us

A free will for you, and a discount for friends and family

tools

Whatever makes you fastest. Frontier models, agentic tooling, no token budget.

ownership

Real decisions from week one. You’ll be trusted with the call and backed when it’s hard.

1. 1

   Intro call30 min · video

   A relaxed conversation with the hiring manager about what you’ve worked on and what you’re looking for. Ask us anything.

   you’ll meet the hiring manager · nothing to prepare

2. 2

   Meet our People team30 min · video

   A conversation about how you like to work, what you need from a team to do your best work, and the practical stuff: start dates, adjustments, anything you’re unsure about.

   you’ll meet our People team · nothing to prepare

3. 3

   Product case and spec session~2 hours · on site

   Two parts. First, work through a real problem from our world: a messy process, a regulatory constraint, more requests than capacity. We care how you frame it, not whether you land on our answer. Then turn a rough feature idea into a spec alongside one of our engineers, asking the questions you’d ask on day one.

   you’ll meet the team · nothing to prepare

4. 4

   Final conversation45 min

   Meet our founder. Talk about where Octopus Legacy is going, where you’d fit in it, and anything you still want to know. It runs both ways.

   you’ll meet our founder · bring your questions

5. ✓

   Decisionwithin 48 hours

   A clear yes or no, with written feedback either way. If it’s a yes, we’ll talk through the offer on a call. No exploding deadlines.

   from the hiring manager