> Markdown version of [/jobs/ext/3707204-full-stack-engineer](https://www.wearedevelopers.com/jobs/ext/3707204-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). --- # Full-Stack Engineer - **Company:** Open Technology Services AU Pty - **Location:** London, UK - **Experience:** Experienced - **Salary:** £63,628.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Cyber Security, Continuous Integration, Software Debugging, Python (Programming Language), Log Analysis, Cloud Services, Software Safety, Software Engineering, Systems Integration, TypeScript, Snowflake, Agentic-AI, Data Layers, Information Technology, Production Code, Enterprise Integration, Machine Learning Operations, Front End Software Development, Human in the Loop - **Published:** October 13, 2026 - **Apply:** https://www.adzuna.co.uk/jobs/details/5925556161 ## About the Role * 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. ## Description 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. The UK team's 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 the region. You'll be hands-on in the same codebase, shipping changes yourself. Reporting to the Senior Full-Stack Engineer, you'll work alongside our partner-facing colleagues, Product, TechOps and Solution Architecture, and day to day with the engineering team in Australia. You're joining a small UK team early, which means more scope than a role like this usually carries - and more support to grow into it. This is a hands-on role, and the majority of your week is building and debugging: writing production code across the stack, working through integration problems, and helping keep what runs in the UK healthy. You'll take work from ambiguous to shipped with a senior engineer close by, and we'll expect that distance to grow shorter over time. You'll be measured on driving up three things: Partner delivery * Build and ship UK partner integrations - taking pieces of a partner journey from requirement to live, with support on the shape of the whole. * Get close to what a partner actually needs: what our platform already does, what can be configured, and what genuinely needs building. * Turn that into working software - configuration and extension where our platform allows it, and a clear write-up of the gap where it doesn't. * Join the technical conversations with a partner's engineers, and own the follow-ups that come out of them. * Give your team an early, honest read on how your work is tracking - no surprise slips. * Keep cutting the time from partner signature to live journey, using the best of modern software delivery and agentic development. AI-native ways of working * Work paired with agents across your own workflow - design, code, review, test, ops and integration debugging - and keep raising your own bar for how fast you can ship well. * Use agents to take the repetitive weight out of partner support: triage, log analysis, first-line diagnosis and the reporting that goes with it. * 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. * Form your own view on which problems an agent should own end to end versus assist on, and back it with evidence from your own work. * Bring what you find back to the team. In a small group, one person's better workflow becomes everyone's within a week. 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.