Platform resilience

• Help keep the platform healthy in region: availability, incident response and engineering health, alongside the Senior Full-Stack Engineer.
• Join the on-call rotation once you're up to speed. 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 bring to your Senior Full-Stack Engineer, the AU team or our solution architects rather than make alone.
• Work 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 to the team, so the platform gets better rather than just patched around.

Who this role isn't for

This is a broad, hands-on 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 a fully specified ticket queue. Partner requirements arrive ambiguous and commercially loaded. You'll have help turning them into something buildable — but you'll be part of doing it, not handed the result.
• 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 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 already restructuring how they work around agents, not someone who plans to "start exploring" GenAI.
• You want to be shielded from partners. You won't own the commercial relationship, but you will be in technical conversations with external engineers, and expected to hold your own.
• You want a large team to sit inside. For a while, UK engineering is a handful of people. What you don't do doesn't get done by someone else.

What you'll bring

Required

• 3+ 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 experience — you've worked against an API you don't control and debugged what happens when it misbehaves. You think about contracts, retries and idempotency.
• Solid in Python and working knowledge of modern AWS — you've had services of your own in production and understand what it takes to keep them up.
• Modern frontend — TypeScript and a component framework, with real care for what the customer at the other end actually experiences.
• Genuinely AI-native — you use AI agents in your own work every day, and you can say specifically what changed as a result.
• Ownership of what you ship — something you built, released and then supported. You can talk credibly about all three parts.
• Modern delivery practices — you've worked with strong CI/CD and understand why small, frequent, reversible changes win.
• Clear communicator — the pull request description, the design note and the incident write-up get written without being chased, and non-technical colleagues come away knowing what to do.
• Judgment about scope — you ship the small useful thing now and flag the bigger problem rather than quietly starting it.
• Bias for action — you spot issues early, fix root causes and keep pushing for simpler, faster, safer ways of working.

Preferred

• Exposure to the insurance, fintech, or regulated financial services sector.
• Experience in a partner-facing, solutions or integration engineering role sitting alongside a core product team.
• Experience building or consuming configurable or no-code product platforms (embedded insurance, white-label sales flows, partner-driven experiences).
• Having shipped something agentic to production, or worked alongside engineers building AI or ML systems.
• Comfort with cloud-native data warehousing (Snowflake or comparable) and the analytics or AI data layer.
• Experience working in a distributed team across distant time zones, where the core engineering team is in another region.
• Familiarity with AI safety practices — evaluations, red-teaming, guardrails, human-in-the-loop.
• Degree in Computer Science, Software Engineering or a related field — or equivalent practical experience.

Role location

Where you'll work

This role is based in London, United Kingdom. We work in a hybrid model, with three days a week in the office. We've found this rhythm genuinely supports collaboration and the kind of fast, high-trust culture we've built. You'll have flexibility on the other two days to work in a way that suits you.

You'll work closely with colleagues in Sydney, including the engineering team that owns the core platform. In practice that means writing decisions down properly and an early call once or twice a week — not a permanently shifted working day.

You'll need the right to work in the United Kingdom.

Why Open?

Open is on a mission to make it easy for everyone to get the most from their insurance. Insurance is one of the world's least digitally mature industries — for years it's remained confusing, paper-based and heavily intermediated. We launched in