Technical Delivery Manager

Newton’s Tree is looking for a Technical Delivery Manager to join an early-stage startup with proven product-market fit and exceptional growth prospects. You will shape the role as we grow, and we want people who relish that.

You will own how work moves from agreed to shipped, across product, platform and hospital deployments. If you've kept a kanban board honest for a team, whether as a Technical Project Manager, a Scrum Master, an engineer or a clinician, you're in the right place.

We build an AI monitoring, evaluation and governance platform. It runs inside hospital networks and in the cloud, and handles patient data in live clinical workflows, so our delivery surface is wide: product features, platform and SRE work, on-premise and cloud deployments into hospital estates, and commitments to customers and partners who need dependable dates. From late 2026 it grows again as we begin delivering at national scale.

Coordinating all of that sits today with our engineering and product leads, alongside their own work. We want a dedicated owner for it: someone who can say, at any moment and without digging, what is deployed, who owns it, what is blocked and when the next thing lands, so that engineers spend their time engineering and leadership has one current view of every project.

You will report to our VP Engineering and work closely with the CEO, who owns the product roadmap. You will also work across our engineering and customer success teams.

Typical responsibilities and duties

The delivery pipeline

• Own how work moves from agreed to shipped, and make it better quarter on quarter
• Make sure requirements, features and fixes land on time and to a high standard, and flag risk early to the people who need to re-plan
• Track the technical artefacts a piece of work needs, such as a software design document, so each has a named author and a date; writing them sits with the engineers
• Surface customer and regulatory deadlines (go-lives, information governance windows, change boards, grant milestones) into the planning window before they become mid-sprint interruptions

Boards and rituals

• Own the epic and issue boards in GitLab and the Delivery Hub in Notion, and keep them current enough to be the single source of truth for project status and governance actions
• Hold three streams with different rhythms without flattening them into one process: Product (sprint-based feature work with customer commitments), SRE (interrupt-driven platform, reliability and deployment work, run as kanban) and FDE (milestone-based work getting the product live in a specific hospital’s estate)
• Give every ticket and deployment milestone a definition of done that someone outside the team can recognise as finished
• Confirm completion: get the stakeholder who asked for the work to sign it off before it is marked done
• Run sprint planning and the preparation it depends on: a refined backlog, current and well-defined tickets, and priorities agreed with leadership and stakeholders beforehand, so the session commits to work rather than discovers it
• Run refinement, stand-ups and retros, and keep them focused and worth the team’s time

Communication and delivery data

• Keep stakeholders and the team aligned on status, ownership and timelines, and manage expectations proactively
• Track delivery metrics such as cycle time, blocked time and slippage by cause, so capacity and planning decisions rest on data

Quality system

• Keep issue, epic and deployment records consistent with the quality records they support under our ISO 13485 quality management system
• Make sure every production deployment has a complete deployment record and, where required, a change record before go-live
• Route delivery slippage and repeat blockers into the non-conformance and corrective action processes where they meet the threshold, working with the Head of AI Governance and Policy

Automating delivery tracking

• Automate the routine: flagging blocked items, unowned actions and at-risk dates, following up open actions and drafting weekly status
• Pilot it on your own boards first, and define what it may do unsupervised and what needs human review
• Keep the judgement calls: what to prioritise, what to escalate, and how and when to talk to customers

Qualifications and skills

This role touches everyone, every week, so how you work matters as much as what you know. You are organised and proactive: you follow through before deadlines are at risk and let nothing slip. You are a strong communicator and a stronger listener, because delivery risks often surface first as an aside in a stand-up. You are pragmatic: process serves delivery, not the other way round.

You read a room, give credit away and are not precious about being right. You know the limits of your remit and resist absorbing everything yourself. And you care about healthcare, because the dates you hold people to become scans reported faster and safer AI in front of clinicians.

Most candidates will come from delivery or project management in a small software company, but we also welcome people from programme management in healthtech or other regulated technology, from hospital IT or digital transformation programmes, and from engineering or clinical roles that have moved towards delivery. What matters is the combination below.

Essential

• Fluency in Agile, Scrum, Kanban and their variants: enough to pick the right one for the team in front of you rather than the one you know best
• Project management craft: planning, dependency tracking, risk and scope management, and reporting that people read
• Stakeholder management at every level, from senior leaders and hospital teams to individual engineers: keeping very different audiences informed, aligned and realistic, including when the message is difficult
• Startup delivery experience: you have shipped software in a small company, shaping the delivery process yourself rather than working within an established PMO
• Fluency with engineering tools: GitLab or equivalent boards and issues, and a work-management tool such as Notion, well enough to configure them yourself
• Technical fluency: you understand how engineers and SREs work and what their processes are for, and you can follow a conversation about a database migration, a release or an integration well enough to plan and report on it, so your involvement makes the work lighter rather than heavier
• You can describe a process precisely enough that an engineer, or an AI agent, can run it

Desired

• Healthcare experience, or delivering into hospital IT, information governance, clinical safety and procurement processes
• Experience shipping both on-premise and cloud products, and comfort with how differently those get delivered
• Experience in a regulated environment (ISO 13485, ISO 27001, SOC 2 or similar) where the board is also the audit trail
• Hands-on use of LLM tools or workflow automation to remove your own administrative work

Not required

• A formal engineering background. Architecture, deployment approach and engineering trade-offs sit with the VP Engineering and the engineering leads; you need to be conversant, not expert
• Product management experience. The CEO owns the product roadmap and its priorities; you make it happen and flag early when delivery and plan diverge
• Customer account experience. Customer relationships sit with the Head of Strategy and Delivery and the Forward Deployed Engineers; you are their internal counterpart, making sure every commitment to a hospital has an owner, a date and a place on a board
• Experience of managing people. This is an individual contributor role today

Compensation & benefits

• A full-time, permanent role
• Base salary of £50,000 to £60,000 depending on experience
• Remote working within the UK, with regular in-person team days and occasional hospital site visits
• Participation in shared company bonus scheme
• Equity through our share option scheme
• Health and wellbeing package
• Professional development opportunities
• 28 days holiday (+ 8 statutory bank holidays)

Our interview process

We aim to complete the process within two weeks and to give you a decision within 48 hours of the final conversation.

1. Introductory conversation (30 minutes) with the VP Engineering or Lead Product Engineer. Mutual fit, how we deliver today and where we want to strengthen it, your questions
2. Competency assessment (60 minutes). Scenario based, testing how you would run and improve the three boards, how you would balance a customer deadline against planned platform work, how you would define “done” for a hospital deployment, and how you would report status to leadership
3. Cross-functional interview (30 minutes) with colleagues from other parts of Newton’s Tree, such as the Product Engineering and SRE leads or the Head of Strategy and Delivery. A chance for the wider team to get to know you and how you work, and for you to ask about working with them
4. Final interview with the CEO (60 minutes). Mutual fit check

About Newton’s Tree

Newton’s Tree is a health technology company that enables healthcare providers to procure, integrate, govern and continuously monitor third-party AI products as part of routine care.

We believe safe and effective AI adoption at scale is essential to delivering healthcare sustainably. We are vendor-neutral, evidence-led and research-active. We work with healthcare organisations in the UK and the United States, and with AI developers across the world throughout the product lifecycle.

How to apply

Please send your CV and a short note to info@newtonstree.com. We would like to hear about one delivery you ran that landed well, and one that did not, and what you took from each.

We can only consider candidates who already hold the right to work in the UK. We are not working with recruitment agencies on this role.

‍