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 Product Engineer

  • Remote
  • 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 builds an AI-powered platform that helps insurers make pricing and underwriting decisions, covering questions like which risks to accept and how to price them, across more than one product and territory.

Backed by a16z, Highland Europe and Battery Ventures, it already serves nearly 50 of the world's largest insurers, reports zero churn, and has billions in premiums flowing through its platform.

The team is building a domain-specific AI coding assistant for insurance and is shaping agentic workflows for the industry.

The company organises work around problems rather than fixed teams. Pods of two to four Product Engineers form around the highest-value problem, own it from discovery through to production, and re-form as priorities shift. Pods sit inside value streams led by Stream Leads, and each engineer has a Career Mentor who manages growth and progression.

Product Engineers are hired into the company rather than a specific team, domain or layer of the stack, and start where their strengths meet the most important problems.

Responsibilities

  • Take a customer problem from discovery to production within a pod, talk to customers directly, frame the problem, and ship small increments based on real customer feedback.
  • Direct AI agents to draft implementation, tests and migrations, then review, integrate and harden the output, owning its correctness and maintainability however it was produced.
  • Write clear enough intent to brief both a human teammate and an agent.
  • Design and deliver robust production systems where correctness, performance and resource efficiency matter, with tests and observability that keep complex behaviour safe to change.
  • Work across the codebase wherever the problem leads, including areas your pod does not own, bringing in owners in proportion to the risk.
  • Move between pods, problems and streams as priorities change, learn unfamiliar domains quickly, and keep what you built running well after you leave it.
  • Take full ownership of outcomes beyond your code, raising risks early and making decisions rather than escalating them.

Requirements

  • You have built and shipped production systems end to end, from design through rollout, monitoring and iteration, where correctness, performance and resource efficiency mattered.
  • You have designed testing and observability that made complex behaviour easy to understand, debug and evolve safely.
  • You have worked effectively across several languages, chosen the right tool for each problem, and picked up new languages, domains and codebases quickly.
  • Strong systems experience, for example in Rust, C/C++ or Python, is valued, and gaps can be closed through upskilling.
  • You have shipped work outside your strongest layer, such as the front end, data layer or infrastructure, without waiting for someone else.
  • You use AI tools as a core part of how you build, with the judgement to direct, review and take responsibility for their output.
  • You bring product and design judgement to engineering, shape solutions rather than only implementing specs, and make sound calls under ambiguity.
  • You take ownership beyond your immediate task and make decisions rather than escalating them.
  • You are unlikely to thrive here if you prefer detailed instructions to experimenting and finding your own approach.
  • You are unlikely to thrive here if you are uncomfortable working directly with non-technical stakeholders to understand their challenges.
  • You are unlikely to thrive here if you avoid ambiguous or open-ended problems where the answer is not obvious.
  • You are unlikely to thrive here if reading the culture document leaves you neutral rather than energised, since the role asks for commitment and conviction.

Conditions

The company is shifting how it builds, and every person in product development is a Builder, with the Product Engineer as the default unit of work.

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 Level 3 scope includes the duties listed above.

Product Engineers are T-shaped, with deep software engineering skills plus enough product and design judgement to make routine calls alone. An embedded PM or designer can help on the hardest problems but never stands between you and the customer.

This is a deliberately AI-native role in an area the company is moving on quickly.

A pod of three owns its problem end to end, which means working on the front end, back end, data or infrastructure as needed. You do not need to be full-stack by background, but you must be comfortable outside your strongest layer.

Pay is discussed early with the Talent Partner in initial conversations, and the company is working toward publishing salary information for all roles globally.

Because the company sits between technology and insurance, roles do not map neatly onto standard benchmarks. Pay is designed to be competitive in the market, fair across teams and matched to the impact people make.

The interview process has five stages: 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 promises feedback to every applicant, whatever the outcome.

The company welcomes applicants from all backgrounds and is working to make its workplace 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.life.
  • Individual wellbeing allowance through Juno.
  • Private healthcare insurance through AXA.
  • Income protection and life insurance.
  • Cycle to Work Scheme.
  • Top-spec equipment, including a laptop, screens and adjustable desks.
  • Remote and in-person hackathons, lunch and learns, socials and game nights.
  • Team breakfasts and lunches, snacks, a drinks fridge and an office at The Ministry.
  • Opportunities for personal development and growth.

Where you’d work

Fully remote

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

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

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
Senior
Type
Full-time
Industry
FinTech
Specialty
Backend
Region
United Kingdom
Show 7 more factsShow less

Role

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

Location

Work model
Remote
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