📍LONDON/ HYBRID
£115,000 - £135,000 + £50,000 SHARE OPTIONS +
Our stack
is primarily C# on the backend, TypeScript and React on the frontend, running on Azure. ML/AI work uses Python. We don't expect you to know all of it - we expect you to follow a problem wherever it leads.
WHAT YOU'LL BE DOING
- Owning features end-to-end: from refining the problem with clinicians and product managers through to architecture, implementation, rollout, and long-term evolution
- Engaging directly with NHS GPs, practice staff and patients to build a genuine understanding of the problems you're solving — research sessions, visiting practices
- Designing architecture and API boundaries with the broader system in mind, not just the immediate surface
- Holding the quality bar for what you ship: not just that the code works, but that the product is reliable, intuitive and safe in a clinical context
- Making the architectural calls that keep our codebase sustainable — improving system health alongside shipping features, not instead of it
- Pushing back constructively when something is wrong, and committing fully when a decision has been made
WHAT EXPERIENCE YOU NEED TO BE SUCCESSFUL
- Comfortable building production software across the stack - you might be strongest in backend or frontend, but you can follow a problem across both to own a feature end-to-end
- Proven ability to reason about systems - breaking ambiguous problems into tractable pieces, spotting trade-offs and second-order effects before they become incidents
- Comfortable with ambiguity and early-stage problem definition; you shape the work rather than wait for a finished spec
- You treat engineering quality as part of the job - managing technical debt pragmatically, reviewing AI-generated output critically, and pushing for the right architectural decisions under real constraints
- Curiosity about AI tools and how they change the way you work, with the judgment to know when to rely on them and when not to
What we’re looking for
to demonstrate as a Product Engineer at Accurx
- You start from the user problem, not the technology. You know what to build, what not to build, and why. In the AI era, that also means knowing what to delegate, what needs human judgment, and what shouldn't exist at all.
- You can break ambiguous problems into tractable pieces and see how those pieces connect across boundaries. You spot seams, trade-offs, and second-order effects — thinking both from big to small and small to big.
- You can pick up unfamiliar code, systems, and assess AI-generated output. You spot flaws before being told, and you understand why something is wrong.