You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
hyperexponential

Senior Staff Product Engineer

  • Hybrid
  • 6+ years

Salary

Not stated

Similar roles pay £90K - 130K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company is building an AI platform that helps insurers decide which risks to accept and how to price them, in an industry worth $7 trillion.

Insurers still make large decisions with dated tools. The platform combines data, AI and expert judgement to shorten the route from submission to decision.

Backed by a16z, Highland Europe and Battery Ventures, the company is expanding worldwide. Nearly 50 of the largest insurers already use it, with zero churn and billions in premiums passing through it.

The product started as a single offering in one market and is now several products across multiple territories, covering pricing and underwriting end to end.

AI sits at the centre of the work, from a domain-specific AI coding assistant for insurance to agentic workflows that change how the industry operates.

Engineering builds and scales the product so insurers can model complex risk and price faster. Product teams are cross-functional, with frontend and backend engineers working alongside designers and product managers. Engineers take part in design, architecture, implementation and testing.

Responsibilities

  • Take a customer problem from discovery to production within a pod. Talk to customers directly, frame the problem, and ship in small steps based on real customer feedback.
  • Direct AI agents to draft code, tests and migrations, then review, integrate and harden the output. Write briefs clear enough for a teammate or an agent, and own correctness and maintainability whatever produced the first draft.
  • Design and deliver production systems where correctness, performance and resource use matter, with tests and observability that keep complex behaviour safe to change.
  • Work anywhere in the codebase a problem leads, including areas your pod does not own. Bring in the owners in proportion to the risk instead of passing work off.
  • Move between pods, problems and streams as priorities shift. Get up to speed quickly in new domains and keep what you built running well.
  • Own outcomes, not just your code. Raise risks early and make decisions rather than escalating them.

Requirements

  • Have built and shipped production systems end to end, from design through rollout, monitoring and iteration, where correctness, performance and resource efficiency mattered.
  • Have designed testing and observability that make complex behaviour easy to understand, debug and change safely.
  • Work well across mixed-language stacks, choosing the right tool and learning new languages, domains and codebases quickly. Strong systems experience, for example in Rust, C/C++ or Python, is valued, and gaps can be filled through upskilling.
  • Have shipped work beyond your strongest layer when a problem needed it, such as the frontend, data layer or infrastructure, without waiting for someone else.
  • Use AI tools as a core part of how you build, with the judgement to direct, review and stand behind their output.
  • Bring product and design judgement to engineering. Shape the solution rather than only building to spec, and make sensible calls when things are unclear.
  • Take ownership of outcomes beyond your immediate task, deciding rather than escalating.
  • Also sought at Level 5:
  • Have set technical direction on a hard problem that other engineers built on, and been judged on whether you made them faster and safer rather than on team size.
  • Have held a quality bar across other people's work without becoming the gate they wait on.
  • Have led cross-cutting or decoupling work that teams adopted because it was the best path, not because it was mandated.
  • Less likely to thrive if you prefer detailed instructions to experimenting, are uncomfortable working directly with non-technical stakeholders, or avoid open-ended problems without an obvious answer. If the Culture Document leaves you neutral rather than energised, the role may not suit you, as it asks for commitment and conviction.

Conditions

The company is changing how it builds. Everyone in product development is a Builder, and the Product Engineer is the default unit of work.

Work is organised around problems rather than permanent teams. Pods of two to four Product Engineers form around the highest-value problem, own it from discovery to production, and re-form as priorities change. Pods sit within value streams, each owning a customer outcome and led by a Stream Lead who chooses the problems and sets the shipping bar. A Career Mentor owns your development and progression, so you can move to the most important problem without your career following the org chart.

You are hired as a Product Engineer into the company, not into a fixed team, domain or layer of the stack. You start where your strengths meet the highest-value problems and move as those problems move.

Product Engineers are T-shaped, with deep software engineering skills plus enough product and design judgement to make routine calls. An embedded PM or designer raises a pod's ceiling on the hardest problems but never stands between you and the customer. The role is AI-native and among the areas moving fastest.

A pod of three owns its problem end to end, which can mean frontend, backend, data or infrastructure. You do not need to be full-stack by trade, but you must be comfortable outside your strongest layer.

The role is the same at every level. What changes is the size of the problem you own, how costly your decisions are to reverse, and how far your judgement reaches beyond your pod.

The office is at The Ministry.

Pay details are shared early in the process by the Talent Partner during initial conversations. The company is working towards publishing salary information for all roles globally. Compensation is designed to be competitive in the market, fair across teams and aligned with impact, since these roles do not map neatly onto traditional benchmarks.

Interview process: an initial chat with the Talent team, a Lead Hirer interview, a live AI skills assessment, a values interview with the CPTO, and a meeting with the CEO.

The company welcomes applicants from all backgrounds and aims to be genuinely inclusive.

Benefits

  • £5,000 training and conference budget for individual and group development.
  • 25 days of holiday plus 8 bank holidays, 33 days in total.
  • Company pension scheme through Penfold.
  • Mental health support and therapy through Spectrum.
  • Individual wellbeing allowance through Juno.
  • Private healthcare through AXA.
  • Income protection plus life cover.
  • Cycle to Work Scheme.
  • Top-spec equipment, including a laptop, screens and adjustable desks.
  • Regular remote and in-person hackathons, lunch and learns, socials and game nights.
  • Team breakfasts and lunches, snacks, a drinks fridge, and a relaxed office at The Ministry.
  • Opportunities for personal development and growth while building something ambitious with the team.

Where you’d work

Part of the week in the office

You can work from

  • United Kingdom

About the company

hyperexponential

  • Industry: FinTech

Office in London, United Kingdom

Also hiring in Warsaw, Poland and New York, United States

8 of their 16 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 1 red flag

Still hiring?

13 checks

1 red flag

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • Python
  • C++
  • Rust
Seniority
Staff
Type
Full-time
Industry
FinTech
Specialty
Backend
Region
United Kingdom
Show 7 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Staff
Experience
6+ years
Tech stack
  • Python
  • C++
  • Rust

Location

Work model
Hybrid
Region
United Kingdom
Office
  • London, United Kingdom
Remote from
  • United Kingdom

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Company

Industry
FinTech

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason