👋 Hi, I’m Sina, CTO at Nous. 

I’ve spent my entire career in startups, starting my first company when I was a teenager, and navigated many 0→1 journeys (including starting the largest social network of its time in my home country).

The common thread that led me here is finding complexity that wastes people’s time or money, then solving for making them disappear. And that’s exactly what Nous aims to do.

If this problem space resonates, please read on. 

PS: I’ve actually written this page with my hands; this is not AI-written content!

About Nous

Roughly 90% of UK households are overpaying on their bills. Nous is an agent to absorb complexity out of households, saving them money and time. Our mission is to make people’s lives simpler and fairer, starting with the 30 million households here in the UK, and soon far beyond.

Nous is 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 novel new products (on top of our current service lines). 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 started with bills because ‘change begins at home’ - it’s a naturally low-interest, messy area of our lives which most of us don’t want to think about. Similar to how Amazon started with books as their first category to go after.

‘Talk is cheap. Action is what really matters’. What we’re building is an agent to take some of the load of life, make good decisions and act for us in areas we can’t or don’t want to act on our own. For an agent, advice is cheap. Action is the product. And action means solving problems in the messy real world.

A note on product

There’s ‘product’ as in the web application that guides our users through the complex world of bills and household admin. It acts as their interface to our management service, as well as all the behind the scenes capabilities needed to orchestrate and deliver that service - actually saving our users money and time. Try it here: app.nous.co/signup (it’s free!)

Then there’s ‘product’ as experienced by our users - which is a service which makes life simple and fair. To deliver this we’ve built a set of powerful capabilities that let us run and improve the service efficiently at scale: agentic communication, multimodal data extraction, orchestration for long-running operational processes, recommendations, our own agentic harness, and more. We compose these into executable workflows that deliver real outcomes for members, like switching someone to a better energy deal without the hassle.

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; which means figuring out, together, what it really takes to absorb household complexity.

As a product engineer, we'll 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 of the types of problems you'll solve:

• 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.

There are also so many interesting problems we are in the infancy of solving. Just as an example - user’s trust us with their Open Banking data - but it’s just lists of transactions. How can we use that stream of information and combine it with all the other data we have, to reduce friction from their lives?

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 work. 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+), with a minimum 2 years of professional experience. 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.

This probably isn't for you if…

• You want a clear remit handed down before you can move. Here you get lots of context and invested colleagues, not a manager translating the work into tickets for you.

• You believe nothing should ship unless it routes through a gate you personally control. The control we care about is structural: guardrails in the tools, not who's allowed to type. If that sounds too loose, we'll probably frustrate each other.

• You want to specialise narrowly and stay in one layer. The role is broad by design.

What to expect

As CTO, and the person hiring for this role, you can hold me to these promises:

• You’ll never be bored. You’ll continuously have difficult and interesting challenges to solve

• The rest of the team and I will empower you with context, and will involve you as a co-founder

• You’ll be learning every day, solve new challenges, and sometimes find yourself running while simultaneously learning how to run

• You’ll have the space and support to grow your AI engineering skills, whether through harness engineering, trying new approaches, or even going as far as inventing new ways of solving problems. We’re building at the edge of what is possible, and we are conscious that there’s trial and error and first principles thinking involved in figuring it out

• You’ll work closely with a caring and highly intelligent team. It’s ok, stalk us on Linkedin and check for yourself

Remuneration and benefits

Compelling packages, including meaningful share options with life-changing upside. We’ve raised enough money to pay real salaries. We're building something great together and we all share in the upside. If we win, we win together.

An environment where you can do your best work:

• 🏢 A great office set up for lots of collaborative working. We already need more whiteboards

• 💻 The equipment / setup / training you need to do your best work (and of course, AI subscriptions, including Claude Code Max tier)

• 🤝 A high-context environment with lots of exposure to the big decisions - be in the room when it happens (literally)

• 🏡 Flexibility around remote work. If you sometimes just need to get your head down, that's fine

• ☕ Very good coffee

• 🍽️ A well-stocked kitchen (featuring a wildly popular toastie maker) so you can always make yourself a breakfast or light lunch on the house

• 🎉 Informal social every week, something bigger every month, plus a set-piece event in the summer and again at Christmas - we're not robots!

• ✈ 33 days paid holidays (including bank holidays)

• 💊 Health and dental cash plans, including an employee assistance programme

• 🚴 Travel benefits, (e.g., the cycle-to-work scheme)

• 💰 A generous cash referral bonus if you introduce us to someone who joins the team

Nous has an office-first culture (i.e., at least 3 days a week, more context on it here). That means we encourage in-person working, and most people do work from the office in Farringdon most of the time. We do a lot of brainstorming, problem-solving and interaction within the team and presence makes this more effective. It also helps ensure people have good peripheral awareness and high context. But we are pragmatic not doctrinal about this, and recognise that some types of work can sometimes be done remotely.