Senior Full-Stack Engineer

Open; Greater London; On-site; GBP 110,000 - 150,000; Full time

Job summary

Open Embedded is our flagship product that lets brands offer insurance inside their customer journeys. In the UK, you’ll own the partner integrations, configure the platform for local needs, and keep the service running in region, hands-on in the same codebase as the AU team.

Reporting to the Senior Engineering Manager, you’ll work with Product, TechOps and Solution Architecture, help grow UK engineering, and mentor a mid-level engineer.

Qualifications

• 5+ years building and operating production software.
• Full-stack capability across frontend and backend.
• Comfortable reading and modifying large existing codebases.
• Strong integration experience with partner APIs and services.
• Proven collaboration with product, ops and external engineers.
• Proficient in Python and modern AWS tooling.
• Modern frontend skills with TypeScript.

Responsibilities

• Develop and operate Open Embedded in the UK, aligning with partner requirements.
• Ship changes in the same codebase as AU team and coordinate with AU.
• Own UK partner integrations end to end from initial discussion to live journey.
• Troubleshoot integrations and participate in incident response.
• Contribute to platform reliability and governance in region.

Skills

Production software ownership

Full-stack development

Reading large codebases

Integration with partner APIs

Team collaboration

Frontend proficiency (TypeScript)

Python and AWS

Tools

Python

AWS

TypeScript

Job description

At Open, we exist because we believe that insurance does not have to be seen as complicated or costly. We’re an AI-powered platform transforming insurance globally — making it more transparent, cost-effective, and customer friendly. Since launching in 2016, we’ve grown into a certified B Corporation, operating across ANZ and the UK, and building modern infrastructure that brings wonder into insurance.

Engineering is how we earn the trust of our partners and customers, and where we turn Open’s strategy into shipped product. The UK is where our next chapter happens, and this role sits at the centre of it: you’ll be the senior engineer our UK partners deal with, turning their requirements into live integrations and keeping the platform they depend on running.

What you’ll do

You’ll work on Open Embedded, our flagship product. It lets brands offer car, home, travel, landlord and purchase-protection insurance inside their own customer journeys, so their customers can buy cover in the same place they buy the core product — configured no-code by our partners, and run end to end by us from quote through to claim.

Where this role sits.

Core feature development and major platform uplifts are owned by our engineering team in Australia. Your remit is the UK end: working with partners on their requirements and integrations, configuring and extending the platform to meet them, and keeping it running in region. You’ll be hands-on in the same codebase — shipping changes yourself. The roadmap for the core product is set and built in AU and you’ll work closely with this team..

Reporting to the Senior Engineering Manager, you’ll work with our partner-facing colleagues, Product, TechOps and Solution Architecture, and day to day with the engineering team in Australia. You’ll also help us build out UK engineering as we grow — starting with a mid-level full-stack engineer joining under you.

This is a hands-on role. Most of your week is building and debugging: writing production code across the stack, working through integration problems with a partner’s engineers, and on incident calls for what runs in the UK. The lift is technical first, with real ownership of the team as it grows.

You’ll be measured on driving up three things:

• Own UK partner integrations end to end — from the first technical conversation through to a live, reliable embedded journey.
• Get into partner requirements early: work out what they actually need, what our platform already does, and what genuinely needs building.
• Turn that into work that ships — configuration and extension where our platform allows it, and a clear, well-argued case into the AU team where it doesn’t.
• Cut the time from partner signature to live journey, quarter on quarter, using the best of modern software delivery and agentic development.
• Give Product and partner-facing colleagues an early, unvarnished read on sequencing, risk and trade-offs — no surprise slips in front of a partner.
• Help us hire well, then set direction for the engineers who join you and own their growth.

AI-native ways of working

• Work paired with agents across your own workflow — design, code, review, test, ops and integration debugging — and set the bar for how fast a small team can ship.
• Use agents to take the repetitive weight out of partner support: triage, log analysis, first-line diagnosis and the reporting that goes with it.
• With Product and the AU team, bring Open’s agentic capability for sales, claims and support to UK partners.
• Build with the evaluations, guardrails and human-in-the-loop patterns that let us deploy GenAI safely in a regulated industry — anywhere a decision affects someone’s cover or their claim.
• Hold a view on which problems an agent should own end to end versus assist on, and defend it with evidence from your own work rather than from a conference talk.

Platform resilience

• Be the UK’s technical line of defence for the platform: own availability, incident response and engineering health in region.
• Join the on-call rotation. Debug production across a partner boundary you don’t control, then write the honest post-incident note.
• Write code others can change without fear: tested where it counts, observable in production, and documented where the reasoning isn’t obvious.
• Make sound design calls within your remit, and know which ones to elevate to the AU team or our solution architects rather than make alone.
• Work hand-in-hand with TechOps, Solution Architecture and InfoSec on reliability, security and governance — including the UK and EU data-residency considerations that shape what we build and where it runs.
• Feed what you learn from partners and incidents back into the AU roadmap, so the platform gets better rather than just patched around.

Who this role isn’t for

This is a broad, hands-on senior engineering role in a lean, high-trust environment. It rewards people who are energised by ownership, breadth and agentic leverage, not those looking for a defined lane or a large organisation to sit inside.

Specifically, it’s probably not the right fit if:

• You want to own the core product roadmap. Feature development and major platform uplifts sit with our engineering team in Australia. Your remit is the UK end — partners, integrations, and running the platform in region.
• You need greenfield to do your best work. Most of what you build extends a substantial existing platform. The craft here is in reading it well and changing it safely.
• You want a fully specified ticket queue. Partner requirements arrive ambiguous and commercially loaded. Turning them into something buildable is the job, not a precursor to it.
• You want to stop writing code. Most of your week is building, and we expect the role to stay that way as the team grows.
• You want to stay in one layer of the stack. In a lean team you’ll be in the partner-facing journey, the services behind it, the data that proves it works, and occasionally the infrastructure it runs on.
• You see AI as autocomplete. This role is for someone who has already restructured how they work around agents, not someone who plans to “start exploring” GenAI.
• You want a purely advisory remit. This role owns delivery outcomes — what goes live for a partner, when, and at what quality — not just recommendations.

What you’ll bring

Required

• 5+ years building and operating production software — shipped, maintained and run by real users, not just delivered.
• Full-stack range — strong on one side and genuinely competent on the other. You can build the customer journey and the service behind it.
• Comfortable in someone else’s codebase — you can read a large existing system, find the right seam, and extend it safely.
• Integration instinct — you’ve debugged failures across a boundary you don’t control: someone else’s API, someone else’s payload, someone else’s timeout. You reason about contracts, retries and idempotency by reflex.
• Credible with a partner’s engineers — you can run a technical conversation with an external team and come out of it with a shared plan, not a longer list of questions.
• Strong technical credibility in Python and modern AWS — you’ve owned services in production, including what happens when they break at 3am.
• Modern frontend — TypeScript and a component framework, with real care for what the customer at the other