The design seat behind
the biggest lever in insurance.
We make products for people who normally struggle to get them.
We started Marshmallow in 2017 for people like migrants and young drivers, who the market typically misjudges. Since then we have grown from 3 to 700+ people, turned profitable, insured millions of drivers and lent millions in car loans.
We are only just getting started. Over the next 10 years we want to become one of the largest financial services providers in the world, by scaling what we have and building what comes next.
That takes curious, commercially minded people who want autonomy and ownership, and who care more about winning together than being right alone.
Join the team that holds the biggest commercial lever in the business.
Three years ago we brought claims in-house. Not just the team, the tooling. Unlike most insurers we own our own tech stack. That means fast learning, tight feedback loops and quick build cycles. And the people you design for sit in the same office.
Worth over £10 million to the business.
That is what automating a single third-party workflow is worth.
Speed is money.
Getting to high-quality accident data faster directly cuts solicitor fees and courtesy car days. Every hour you save the customer saves the business too.
Our tech, our pace.
Unlike other insurers we build on our own stack, so what you design ships in days, not quarters, and you learn from it just as fast.
Real people, real problems. On both sides.
Nobody opens an app to start a claim with crying kids in the back seat.
The customer side is about meeting people at the point of distress, and capturing the signals they give off naturally instead of making them fill in forms. You need to be comfortable designing for someone's worst day.
A full SaaS-grade claims management system.
Tools for our claim handlers, balancing partners and workflows. The long game is deciding, case by case, whether AI is a co-worker for handlers or replaces the workflow entirely.
Where the work lands today.
The split shifts as you and your PM choose where the impact is each quarter.
What you will be doing.
Choose where the impact is.
Nobody hands you a roadmap. You and your PM decide what matters each quarter. Curiosity and a bias for action are the job.
Run your own research.
Internal and external. Gather feedback, run your own studies and use insight to inform design decisions.
Ship high-quality, clear design.
Use design principles, industry knowledge and best practice to make rational decisions that help customers when they interact with Marshmallow.
Build with AI, daily.
Design AI workflows that automate claim handling, and experiment with AI in your own process. Free rein with Claude, shipping internal tools straight to production.
Navigate stakeholders.
Claims is a costly area with a lot of attention on it. Take stakeholders on the journey and keep them in the loop.
Raise the bar.
Pair with peers, hold design reviews, facilitate workshops and contribute to the wider design system.
You will not be figuring it out alone.
A small, senior team that pairs on work, holds design reviews and runs its own research end to end.
And the people you will build with.
Your cross-functional partners in the claims team, plus an operations floor of 200+ claim handlers to do research with and gain insights from.
We celebrate the work, and each other.
Every Friday the team shares weekly wins, from hackathon medals to a test that moved cancellations by 4.2 points. And a few times a year we get out of the office for a team day: strengths, gaps, rituals and handwritten appreciation notes for each other.
What the work actually looks like.
A recent workshop: designing a claim snapshot that gets handlers up to speed in seconds. Everyone sketching, from engineers to handlers.
And when it ships, you hear about it.
The Slack moment our first AI agent went to production, and the handler feedback that landed the same day.
From workshop sketches to an AI agent live on real claims, with handler feedback landing the same day. That is the loop you will work in.