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 which ones to escalate 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 end actually experiences.
• Genuinely AI-native — you use AI agents in your own work every day, you’ve shipped something agentic to production, and you can say specifically what changed as a result.
• End-to-end ownership — something you designed, built, shipped, ran on-call and then improved. You can talk credibly about all five parts.
• Some experience leading engineers, formally or informally. You’ve set direction for other people’s work, given hard feedback, and helped someone level up.
• Modern delivery practices — you’ve worked trunk-based with strong CI/CD and know why it matters culturally, not just technically.
• Confident communicator — the design doc, the pull request description and the incident note 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 keep the big rewrite in your back pocket.
• 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 worked alongside — or led — engineers building AI or ML systems in production.
• 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’