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. That’s the bar every screen we ship has to clear, and it has to feel calm while it does.
As our design engineer, you’ll work across every team rather than inside one. You’ll own the component library and design tokens, take features from rough idea to shipped interface, and decide what good looks like.
Nobody will hand you a pixel-perfect mock to implement. You’ll make the mock, then make it real, then watch how people use it and change it.
You’ll work with every team: the engineers building Ollie, the tools our advisors and Estate Planning Consultants use every day, and our web presence. You’ll be closest to Product and the team leads, and the design system is yours to shape.
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. Families come to us for a will or for probate, not for software, so we’re not racing the models. Every time they improve, so does the service families get. We ship to production 20+ times a day across 7+ services.
Most weeks are a mix of designing, building and unblocking other teams. Some of the work you’ll pick up:
- Design flows and interfaces in Figma, then build them in React. Same person, same week.
- Own the component library and design tokens, and keep Figma and code saying the same thing.
- Make hard things feel calm. Someone planning for their own death shouldn’t have to fight a form.
- Hold the line on accessibility. Our users span every age and ability.
- Prototype fast, so Product and engineers can react to something real instead of a paragraph.
- [ ]Week one: ship a UI change to production, paired with someone who knows the codebase.
- [ ]Audit the component library against Figma and fix the worst of the drift.
- [ ]Take one feature from rough idea to shipped interface, designed and built by you.
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.
- A portfolio that shows both the design and the code behind it.
- Strong Figma/ Paper experience: components, variables, auto layout, the unglamorous structure that makes a system scale.
- Production React and TypeScript.
- Taste, and the ability to explain it to an engineer in terms they’ll act on.
- Vue. Some of our estate still uses it.
- A pipeline from Figma variables to code tokens, built by you.
- Motion and micro-interactions that earn their place.
- Next.js or another server-rendered React setup.
Don’t tick every box?Apply anyway. We hire for how you think, not a checklist.
- figma / Paper for components, variables, auto layout
- Typescript
- React
- Next.js
- vue parts of the estate still use this
AI
Claude code + Whatever you're fastest in
Every product has them. Better you hear it from us.
- You can’t leave a misaligned label alone, and you know how to fix it in code.
- You’d rather ship something simple and kind than impressive and confusing.
- You can talk about death plainly. Our users are planning for it or living through it.
Listed, not teased. If something matters to you and isn’t here, ask in your first call.
Octopus Legacy London, England Office
Work.life, Hawley Crescent, London, United Kingdom, NW1 8NP
