Head of Delivery

Hero Health | Oxford, UK | Full time | On site

About Hero Health

Hero Health has built a patient facing platform used by NHS primary care, bridging the gap between patients and their electronic healthcare records. GP practices, PCN hubsites and community providers use Hero for online triage, appointment booking, and patient messaging, all deeply integrated with the NHS clinical systems EMIS Web and SystmOne. Hundreds of practices and thousands of clinicians and administrators rely on Hero every day, and our platform sits inside a growing ecosystem of NHS technology partners who build on our API.

We are a small, senior team of 13 people. Everyone here carries real responsibility, ships real work, and sees the effect of that work on the NHS front line within days, not quarters.

Why this role, why now

Hero is at an inflection point. Our customer base has grown multi-fold over the last 12 months, and usage is growing exponentially across every product area: triage, booking, messaging, and our partner API. At the same time, AI has changed how we work internally, enabling smaller, more modular units of the business to build and ship independently.

Growth and modularity are both good problems, but they share a cost: far more now moves between functions than ever before. Work crosses commercial, product, and engineering constantly, and the coordination load has outgrown a team of stretched specialists. We need someone whose actual job is to orchestrate that flow, and who can materially leverage AI and automation to do it at a level a headcount of 13 could not otherwise reach.

The role

You will own how work moves at Hero: from the moment something is decided to the moment it is confirmed done, whether it is technical, commercial, or somewhere in between. Concretely, that means:

• Orchestrating cross-functional work. You are the single front door for work that crosses teams. You make sure everything is captured, specced, sequenced, and driven to completion, with status flowing to the right people without being chased.
• Running delivery for the engineering team. You run the planning and delivery cadence for a team of six developers working across multiple simultaneous projects, keeping work well defined before it starts and closed properly when it ends.
• Owning the automation agenda. You are the person who keeps asking 'have we automated this yet?', who spots the manual process eating someone's morning, and who makes sure the fix actually happens.
• Solving problems yourself. This is not a pure coordination job. Where a problem can be solved directly, with a script, an automation, an AI workflow, or an afternoon of focused work, you solve it rather than routing it.
• Designing the processes between teams. You decide how delivery runs here: the tooling, the templates, the meeting cadence, the definitions of ready and done. You redesign processes when they stop working.