> Markdown version of [/jobs/ext/4096140-digital-delivery-manager](https://www.wearedevelopers.com/jobs/ext/4096140-digital-delivery-manager). 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). --- # Digital Delivery Manager - **Company:** Digital Dynamite Ltd - **Location:** UK (Remote available) - **Experience:** Expert - **Salary:** £45,000.0 - £50,000.0 - **Contract:** Temporary to permanent - **Skills:** Contentful, Artificial Intelligence, Asana, JIRA, Spreadsheets, Drupal, Umbraco, Web Platforms, WordPress, Zapier, Agentic-AI, Production Code, Virtual Agents, Veeva - **Published:** October 16, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=8c6dc3ae8b6c5af4 ## About the Role * Clear written English and a collaborative way of working with engineers, designers and clients Desirable * A background as a developer or engineer * An AI agent you built and ran for a team * Delivery in Pharma, healthcare or another regulated sector, for example MLR review, the ABPI Code or Veeva PromoMats; we train you on these in your first two weeks * Linear, our project tracker (Jira, Asana or similar is fine) * A delivery process you built where none existed * Experience with more than one delivery methodology, and knowing when each fits, * Do you have experience working in digital agency, studio or software house as Delivery Manager, Digital Project Manager or Producer? ## Description You are accountable for delivering every client project on time, in full and to the agreed scope. You run delivery day to day and are our clients' main contact for project progress, so that our Managing Director can focus on client relationships and new business. You'll also help shape how we use AI and agents to run delivery., * On-time, in-full delivery. Every client project delivers what was sold, by the date agreed with the client. Out-of-scope requests and overruns are flagged and measured. When a date is at risk, we discuss options together. * Plans and requirements. Every signed proposal becomes a delivery plan and a Linear project within three working days. Every ticket has clear requirements and acceptance criteria before work starts, and MLR (medical, legal and regulatory) review rounds sit in the timeline. Nothing reaches a client until its review and MLR sign-off are done. * Capacity. Everyone's time is planned across projects and overload is raised before it causes a slip. The need for a contractor is spotted early. * Product workstreams. Our own products, from AI tools for clients to our internal platform, have a roadmap, milestones and protected time, so a busy month of client work doesn't stall them. * Team rhythm. Everyone knows what they're working on this week and what's in their way. You run the delivery check-ins and clear or escalate blockers within a day. Every decision leaves the room with an owner and a date, and check-ins ask for evidence, not a status word. * Reporting and priorities. Our Managing Director always knows where every project stands. Every Monday you present the status, hours used against budget, risks and an on-track or off-track call for each project, then agree the week's priorities in a 30-minute session. When client and product work compete for the same people, you bring the trade-off, with options, to that session. * The delivery system. How we run projects is defined, documented and right for a team our size. Agile and Waterfall have not fitted us as they are, so you shape the approach that does and run it in Linear. All live work sits in Linear with an owner, status and due date, and each quarter brings one measured improvement to a process or automation. What you will do * Lead client calls with our Managing Director as the delivery owner, gather requirements and send follow-ups. * Take part in technical discussions with our Senior Web Engineer and Design Lead and bring ideas; they own how things are built and designed. * Build and improve the automations and AI agents that run our delivery. * Run a short retro after each milestone and turn what we learn into how we work. You don't manage people in this role. Shaping the estimates behind new proposals is the next step once you're settled. What success looks like Our five values are how we all judge good work. In this role, they look like this. * Own the outcome. Projects land on time without anyone chasing them. If something slips, you already know why and what happens next. * Relentless standards. Every project is planned, ticketed and reported to the same standard, whoever is working on it. * Craft that matters. Plans and tickets are clear enough that an engineer can start work without a call. * Truth over comfort. We say early when a date or the scope is at risk, and that goes both ways. When something goes wrong, we discuss it, fix it together and learn from it. * Curiosity as discipline. Staying sharp is a choice we make every day. You grow your own skills, with the time and budget to back it, and bring what you learn into how we plan and deliver. In your first 90 days: a clear picture of every live project, its proposal and the people on it. Every project is in Linear with an owner, a milestone and a next action. The Monday report is running, and we've agreed together how we run projects from here. In your first year: new proposals are estimated with your input before they go out. Agents handle triage, status drafts and health checks, with you approving what they do. Client dates are met or reset early, never missed without warning. Together, that means we can take on more clients and more projects without the delivery effort growing at the same rate. Beyond that: as we grow, you grow into our Delivery Lead and shape any delivery hires that follow. Essential * Delivery of several website, portal or web platform projects at once for external clients, in a digital agency, studio, software house or product team: you've planned them, delivered them and recovered them when they slipped * Scope and budget control: you've handled change requests, scope creep and estimates against actuals, and raised them early * Capacity planning across a team and contractors, in a tool or a spreadsheet * A technical background, or equivalent fluency from working closely with engineers. You know how content management systems differ (for example WordPress, Drupal, Umbraco, Craft, Contentful or Sanity) and what headless means. You can follow how code gets from a pull request through staging to production * You hold your own in technical discussions: you speak the language, challenge an estimate and bring technical ideas of your own, without writing production code yourself * Requirements and acceptance criteria that engineers can build from without a call * AI tools in your own daily work, and at least one automation you built that a team used (a no-code workflow in Zapier, Make or n8n counts)