Senior Full-Stack Engineer

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 what to escalate to the AU team or solution architects.
• Work with TechOps, Solution Architecture and InfoSec on reliability, security, governance and UK/EU data-residency requirements.
• Feed learnings from partners and incidents back into the AU roadmap.

Who this role isn't for

This is a broad, hands-on senior role in a lean, high-trust environment — for people energised by ownership, breadth and agentic leverage, not 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 — that sits with our engineering team in Australia; your remit is the UK end.
• You need greenfield to do your best work — most of what you build extends an existing platform, and the craft is reading it well and changing it safely.
• You want a fully specified ticket queue — partner requirements arrive ambiguous and commercial, and turning them into something buildable is the job.
• You want to stop writing code — most of your week is building, and that won't change as the team grows.
• You want to stay in one layer of the stack — in a lean team you'll be across the journey, the services behind it, the data, and occasionally the infrastructure.
• 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, 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 system, find the right seam, and extend it safely.
• Integration instinct — debugged failures across boundaries you don't control (someone else's API, payload or timeout), reasoning about contracts, retries and idempotency by reflex.
• Credible with a partner's engineers — you can run a technical conversation with an external team and land on a shared plan, not more questions.
• Strong in Python and modern AWS — you've owned production services, including what happens when they break at 3am.
• Modern frontend — TypeScript and a component framework, with real care for the customer experience.
• Genuinely AI-native — use agents daily, have shipped something agentic to production, and can say what changed as a result.
• End-to-end ownership — something you designed, built, shipped, ran on-call and then improved.
• Some experience leading engineers, formally or informally — setting direction, giving hard feedback, and helping someone level up.
• Modern delivery practices — trunk-based with strong CI/CD, valued culturally as well as technically.
• Confident communicator — design docs, PR descriptions and incident notes get written unchased, and non-technical colleagues know what to do.
• Judgment about scope — you ship the small useful thing now and keep the big rewrite in your back pocket.
• Bias for action — 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 alongside a core product team.
• Experience building or using configurable/no-code platforms (embedded insurance, white-label, partner-driven experiences).
• Worked alongside, or led, engineers building AI/ML systems, including AI safety practices — evaluations, red-teaming, guardrails, human-in-the-loop.
• Comfort with cloud-native data warehousing (e.g. Snowflake) and the analytics/AI data layer.
• Experience in a distributed team across time zones, with core engineering based elsewhere.
• Degree in Computer Science, Software Engineering or a related field — or equivalent practical experience.

Role location

This role is based in London, United Kingdom. We work in a hybrid model, with three days a week in the office. This rhythm supports collaboration and the 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?

It's an exciting time to join Open and be part of a tech scale-up. We provide our team with:

• Highly competitive compensation, including share options — we believe in paying people what they're worth and sharing our success.
• High autonomy and trust so you can do your best work.
• Growth opportunities internally — as you grow, your role can too.
• Flexible working — we are about impact, not time at your desk.
• Freedom and responsibility, including the ability to work from anywhere.
• Paid company parental leave, supporting all parents as they balance career and family.
• Personal development allowance — a flexible annual benefit for learning, wellbeing and growth.

We're proud to be a certified B Corporation, using business as a force for good, and an equal opportunity employer committed to an inclusive environment for all employees. If you need any adjustments to take part in our process fairly, at any stage, tell us and we'll make them — you don't need to explain why.

Open is a high