> Markdown version of [/jobs/ext/2009620-senior-full-stack-engineer](https://www.wearedevelopers.com/jobs/ext/2009620-senior-full-stack-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Full-Stack Engineer - **Company:** Open Technology Services UK Ltd - **Location:** London, UK - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Cyber Security, Continuous Integration, Software Debugging, Software Design Documents, Python (Programming Language), Log Analysis, Cloud Services, Software Safety, Software Engineering, TypeScript, Snowflake, Data Layers, Information Technology, Production Code, Enterprise Integration, Machine Learning Operations, Front End Software Development, Software Coding - **Published:** August 10, 2026 - **Apply:** https://www.totaljobs.com/job/senior-full-stack-engineer/open-technology-services-uk-ltd-job107817302 ## About the Role * 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. ## Description 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: Partner delivery * 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 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. ## Related Videos - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [How Cisco embraced a DevOps culture within its network engineering team](https://www.wearedevelopers.com/videos/99-how-cisco-embraced-a-devops-culture-within-its-network-engineering-team) - [Do TypeScript without TypeScript](https://www.wearedevelopers.com/videos/327-do-typescript-without-typescript) - [How to govern Vibe Coding for the Enterprise](https://www.wearedevelopers.com/videos/100290-how-to-govern-vibe-coding-for-the-enterprise) - [Hacking AI at the Edge of the Indian Ocean](https://www.wearedevelopers.com/videos/100177-hacking-ai-at-the-edge-of-the-indian-ocean) - [Agentic employees in world's most downloaded FinTech app](https://www.wearedevelopers.com/videos/100123-agentic-employees-in-world-s-most-downloaded-fintech-app) ## Related Articles - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [The 12 Best Jobs for Software Engineers](https://www.wearedevelopers.com/magazine/401-the-12-best-jobs-for-software-engineers) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [7 Most Popular Web Developer Jobs in Europe](https://www.wearedevelopers.com/magazine/163-7-most-popular-web-developer-jobs-in-europe)