About Nous

Nous is an AI agent that takes some of the load of life; making good decisions and acting for our users in areas where they’re not the experts or aren’t paying enough attention. We've started with optimising bills, where we're already saving households thousands, and are now expanding into new categories. Similar to how Amazon picked books as its first category and grew from there.

We’re growing fast, and it's working. 20x YoY growth makes us one of the fastest scaling startups in the UK. And NPS of +70 (higher than Apple) shows that our users love it.

We've just launched two more novel new products (on top of our existing bill optimisation). Insurance: we're the first to get the regulatory approval and build the tech to actually do the full insurance discovery and purchase journey as an agent for the user (not just give them a link to the best deal). Subscription management: lots of companies use Open Banking to draw pretty graphs – we're the first to use it to actively save people money starting by cancelling unwanted subscriptions for them.

It would be easy to look at this and think we've got it all figured out. But we've only scratched the surface; our ambitions are SO much higher.

We’re building a new category of product which is hard, so we’ve stacked the deck in our favour: an experienced founding team with multiple exits, and investors including the founders of Monzo, Wise, Booking.com, lastminute.com, Onfido, Funding Circle, Tide, Habito and more.

Still - the problems we’re solving are hard. ‘Talk is cheap’ applies to agents too. To have REAL impact, agents need to break out of the sandbox and take action in the real world where there are consequences. This means solving all the hard, thorny, interesting, frustrating problems the real world has to offer.

Open positions

Product & engineering

Product Engineer

Staff Product Engineer

Commercial & growth

Operations & Automation Associate

Growth Associate

<aside> ✉️ Can't see your role? If you're the person this page is describing, we still want to hear from you. Email us at [email protected].

</aside>

The role

We already have strong Product Engineers who think in products, not tickets, and own problems end-to-end.

As a Staff Product Engineer, your job is to multiply that: to pick and lead the big, often cross-team bets that change how well we help members — how quickly a new household goes from “I think I’m overpaying” to “Nous is handling it”, how many people actually get tangible value through Nous, and how little human effort it takes behind the scenes.

This is a hands-on individual contributor role, not a people-management role. You’ll spend most of your time in code, system design and product thinking - but at a scope that cuts across teams and directly shapes company direction. If you desire, there is also space and opportunity for growing into a people-management role down the line, as we grow.

How we build

We try to keep our stack simple & modern, while safe & boring in the right ways:

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 members.
AI: we work with messy billing and usage data, and have been building “agentic” brains that can read, reason and safely act on behalf of 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 ship to production daily, favour small, reversible changes, and keep a close eye on the user impact of what we ship.

What you’ll do

You will:

Own 2–3 high-leverage bets per year, not just projects.
Turn fuzzy problems into clear plans.

Start from messy reality — confusing renewal letters, half-complete data, stressed households — and define the problem, the metrics that matter, constraints, and a concrete technical approach.
Ship small, end-to-end slices every 1–2 weeks.

Design work so that real members feel the benefit often: a new flow, a clearer explanation, a safer orchestration. Each slice has a before/after we can actually look at.
Be a domain owner in one or more critical areas (e.g. front-end, workflows/Temporal, infrastructure, agentic-AI core, data modelling).

You’ll set and evolve the patterns and primitives others build on, and keep them simple, understandable and teachable.