Product Engineer (all levels)

Today, we help manage six areas of household spending: Energy, Mobile, Broadband, Mortgage, Personal finances (e.g., managing subscriptions), and Insurance. But we’re just getting started. Behind the scenes, we’ve built the technology (we call it Blueprints) that acts as rails for us to quickly expand on the breadth and depth of our service lines.

The role

We need your help building a world-class product that will be used regularly by millions of people; and figuring out, together, what it really takes to absorb household complexity.

As a product engineer, we empower you with context to enable fast iterations, end-to-end ownership and lots of agency. You’ll be a hands-on technical leader on some of the highest-leverage areas of our codebase, from building out agentic capabilities to scaling our service logic.

Some examples:

• Anton led and shipped an entire product line around open banking and subscription management three months after joining. Yes, he had support from legal, design, commercial and his team (we even became FCA registered). But one product engineer still took it from idea to a best-in-class product in the category.
• Ed led the our latest Blueprint architecture, which now powers every service line. Changes to complex, long-running workflows that once took weeks can now sometimes take minutes. All safely, reliably and with full type safety.
• Tim led and shipped our car insurance product line, in less than 3 months. We built a journey where an agent performs the discovery and purchase journeys - something that's not been done before and needed problem solving at the intersection of engineering, product and regulatory.

As a team, we built our own agentic harness (we call it super-engineer); it’s enabled us to build faster, investigate complex cross-system issues effectively; and it self-improves.

Every week, we’re building tools for ourselves and evolving how we work, to make ourselves more effective. I strongly believe in the value of compounding gains, and much of our focus goes into investing in what results in exponential growth.

Although our stack is constantly evolving (and you can help shape that), here’s a current snapshot:

• Full-stack TypeScript, React, Postgres, and Temporal for long-running orchestration.
• Infra: AWS, Terraform, strong observability via Sentry and Datadog (full-stack, not just logs).
• Data: we lean heavily on Snowflake, Omni, dbt, Fivetran, Amplitude and Segment — and we’ve even built some of our own tooling to understand how well we’re helping our members.
• And we use Github, Linear, Graphite, and Blacksmith every day. We choose the best tool for the job, and don’t obsess around specific technologies.
• We also heavily rely on our wide range of agentic and tooling harness that we build and iterate on across the team. They’re part of the “secret” behind how we move fast, reliably.

You’ll report directly to the CTO (and we’ll work closely), so will be in the room for key architectural and product decisions. We’re deliberately light on layers of management: exceptional individual contributors shape direction by solving hard problems.

We organise around small product squads (around 5–7 people) with a single shared objective; and ship and learn fast.

You'll build in two modes

This is the bit that makes the role different, so it's worth being clear about.

Sometimes you build the product directly. That might mean a new product line, a core product improvement; or an exciting new idea to experiment on the product. You're usually working with one or two others, moving fast from a rough plan and jumping on problems as they surface.

Sometimes you build the multiplier. The safe surfaces and shared tooling that let a non-engineer ship without breaking things. Think the internal equivalent of what Lovable did for "anyone can put a website live", but for our problems: bills, switching, household admin at scale.

Both are hard engineering. And the two feed each other: the better the multiplier you build, the more the genuinely deep problems are the ones left for you. Leverage for the ops team is leverage for you.

What We Look For

You don't need to tick every box. If you read these and feel a mix of "this is me" and "this would stretch me", you're probably right for it.

• You own problems end to end. You're happiest going from fuzzy pain to shipped fix to the numbers that show it worked. You instinctively ask "what's the smallest thing we can ship to learn?" instead of waiting for a perfect spec.
• You think like a PM as much as an engineer. You care about the problem, the user, flow, UX, and even copy as much as correctness, because you've seen a small wording change flip confusion into action.
• You're a pragmatic builder. Clean, practical code others can extend. You know when to abstract and when to keep it brutally simple to go fast. You'll happily delete your own code when reality disagrees with it.
• You build leverage for other people. You explain complex things simply, you pair on gnarly problems, and you leave things clearer than you found them. You see a good tool that unblocks a teammate as real work, not a distraction from it.
• You're here for the problem. Fairness, money and complexity, made manageable for people who don't have time to fight the system themselves. You'd rather work hard on something that genuinely helps.

We hire across all levels (mid-senior, to staff+). The size and independence of your initial scope will reflect your experience, but the shape of the role is the same: you own outcomes. For earlier-career candidates, our assessment is primarily on your growth trajectory.