Technical Delivery Manager - Agentic AI Engineering (Manager)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Apply today", "To make the most of your application experience..." etc. Also remove "EY | Building a better working world" etc. Also remove "EY provides equal employment opportunities..." etc. Also remove "If you have a disability..." etc. We need to parse the posting. Key sections: - Location: Anywhere in Country (maybe not needed? It's metadata; we can fold into short

maybe. It's location info. Could be included in a short paragraph under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So location can be a short

. - Intro paragraph: "At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world." That's about the company; could be part of About the role? Probably "About the role" section should contain description of the role and maybe intro. We'll include that. - "The opportunity We are seeking a seasoned Technical Delivery Manager to drive the day-to-day execution of the engineering teams building EY’s Agentic AI platform. This role owns delivery cadence across multiple development programs: running the Scrum process and its ceremonies, keeping work flowing, and holding engineers accountable for what they committed to and when. You will be the person who knows, at any moment, what is genuinely in flight, what is genuinely blocked, and what is quietly slipping. This is deliberately not a facilitation-only role; you must understand what is actually being built (Kubernetes and GPU infrastructure, CI/CD/CV pipelines, model serving and routing, agent orchestration, data and state layers) well enough to interrogate an estimate, tell a real dependency from a convenient one, and challenge scope and sizing with evidence. The role is ideal for an engineer-turned-delivery-lead who is credible with senior engineers because they have done the work themselves, who is comfortable being the person who asks the uncomfortable question in stand-up, and who measures success in working capability shipped against committed dates rather than in ceremonies run or boards kept tidy." That's about the role. - "Your Key Responsibilities" then list bullet points. Those are responsibilities. - "Skills And Attributes For Success" then bullet list. - "To qualify you must have Bachelor’s or Master’s degree in Computer Science, Engineering, or a related technical field, or demonstrably equivalent depth.7+ years in technical delivery, engineering project or program management, or Scrum Master roles supporting software engineering teams, with direct accountability for delivery outcomes.A technical background: prior hands-on experience as a software or platform engineer, or demonstrably equivalent technical depth.Demonstrable ability to evaluate engineering estimates, work decomposition, and technical risk independently, and to challenge them constructively with evidence.Proven track record running Scrum or Kanban for teams of experienced engineers, owning the full set of ceremonies and the health of the backlog.Experience delivering complex, multi-team technical programs with hard cross-team dependencies and phased delivery gates.Working fluency with modern cloud-native engineering: Kubernetes and containers, CI/CD, infrastructure-as-code, distributed systems, and API design.Hands-on experience with engineering delivery tooling (Jira or equivalent) and Git-based workflows, including the delivery metrics they produce.Evidence of holding delivery teams to timelines and quality standards while retaining their trust and engagement.Ability to communicate delivery status, risk, and trade-offs to senior stakeholders with clarity and candour." That's qualifications/requirements. Could be split into Requirements and Qualifications? The instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = preferred? But we can combine. However we need to avoid thin sections. We have a lot of qualification content; we could put all under Requirements (or Qualifications). But we also have Skills And Attributes For Success which is clearly Skills. So we will have: - About the role (intro + opportunity description) - Responsibilities (list) - Requirements (mandatory qualifications) - Qualifications (maybe preferred/experience items? Could be the "Ideally, you’ll also have" list) - Skills (Skills And Attributes For Success) - Benefits (What We Offer You) - Pay (salary ranges) - Schedule? Not mentioned; no schedule info. So we should NOT include Schedule section because no real specific content. Similarly Benefits we have content. We must not include sections with filler like "commensurate with experience". We have actual salary ranges, so Pay section is valid. We need to preserve all substantive info. So we need to include the salary ranges exactly as given. We need to include benefits: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options, flexible vacation policy, designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, other leaves. We also have "Learn more at ey.com/us/careers." That's maybe boilerplate? It's a link; could be considered part of Benefits? It's more like a call to action. Might be considered application instruction? It's not exactly instruction to apply; it's just a link. Might be okay to keep as part of Benefits? But it's not a benefit. Could be considered generic info; maybe we drop it as it's not substantive benefit. The instruction: remove application instructions. This is not exactly an instruction but a link to learn more. Might be considered boilerplate. Safer to drop. Also "Under our flexible vacation policy, you’ll decide how much vacation time you need based on your own personal circumstances. You’ll also be granted time off for designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, and other leaves of absence when needed to support your physical, financial, and emotional well-being." That's benefits. Now we need to format. We'll produce:

Location: Anywhere in Country

About the role

At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. The opportunity We are seeking a seasoned Technical Delivery Manager to drive the day-to-day execution of the engineering teams building EY’s Agentic AI platform. This role owns delivery cadence across multiple development programs: running the Scrum process and its ceremonies, keeping work flowing, and holding engineers accountable for what they committed to and when. You will be the person who knows, at any moment, what is genuinely in flight, what is genuinely blocked, and what is quietly slipping. This is deliberately not a facilitation-only role; you must understand what is actually being built (Kubernetes and GPU infrastructure, CI/CD/CV pipelines, model serving and routing, agent orchestration, data and state layers) well enough to interrogate an estimate, tell a real dependency from a convenient one, and challenge scope and sizing with evidence. The role is ideal for an engineer-turned-delivery-lead who is credible with senior engineers because they have done the work themselves, who is comfortable being the person who asks the uncomfortable question in stand-up, and who measures success in working capability shipped against committed dates rather than in ceremonies run or boards kept tidy.

Responsibilities

• Own the delivery cadence: run daily stand-ups, sprint planning, backlog refinement, sprint reviews, and retrospectives across the engineering teams, keeping every ceremony short, decision-focused, and genuinely useful to the engineers in the room.
• Drive progress against commitments: track every in-flight item through to completion, surface slippage on the day it happens rather than at sprint end, and ensure blocked work is actually unblocked rather than quietly rescheduled.
• Hold engineers accountable to deliverables and timelines: agree explicit definitions of done and dated commitments, follow them up personally, and escalate early and credibly when delivery is at risk.
• Interrogate estimates and challenge padding: apply your own technical judgement to test sizing, decomposition, and complexity claims, separate genuine engineering risk from conservative buffering, and hold estimates to what the work actually requires.
• Break down ambiguous work: translate architecture intent, phase gates, and platform capability requirements into properly sized, independently deliverable stories with unambiguous acceptance criteria.
• Own sprint and release planning across the phased platform build: sequence work so each phase puts usable capability into engineering teams’ hands, and defend entry and exit gates rather than letting them soften under schedule pressure.
• Manage cross-discipline dependencies: coordinate hand-offs between platform and infrastructure, runtime and observability, data and state, trust infrastructure, security, and the AFE delivery cells.
• Own delivery risk and issue management: maintain a live view of risks, dependencies, and the critical path, drive mitigation to closure, and make trade-offs explicit to leadership while there is still time to act on them.
• Report delivery status with evidence: velocity, throughput, cycle time, flow efficiency, escaped defects, and burn against phase gates, reported honestly and without softening, including when the news is bad.
• Protect the team’s focus: absorb interruptions, scope injection, and competing stakeholder demands so engineers get uninterrupted delivery time.
• Partner with engineering leads and architects: on sequencing, staffing, and technical direction, with a clear boundary that they own the technical decision and you own whether the work lands on time and to standard.

Requirements

• Bachelor’s or Master’s degree in Computer Science, Engineering, or a related technical field, or demonstrably equivalent depth.
• 7+ years in technical delivery, engineering project or program management, or Scrum Master roles supporting software engineering teams, with direct accountability for delivery outcomes.
• A technical background: prior hands-on experience as a software or platform engineer, or demonstrably equivalent technical depth.
• Demonstrable ability to evaluate engineering estimates, work decomposition, and technical risk independently, and to challenge them constructively with evidence.
• Proven track record running Scrum or Kanban for teams of experienced engineers, owning the full set of ceremonies and the health of the backlog.
• Experience delivering complex, multi-team technical programs with hard cross-team dependencies and phased delivery gates.
• Working fluency with modern cloud-native engineering: Kubernetes and containers, CI/CD, infrastructure-as-code, distributed systems, and API design.
• Hands-on experience with engineering delivery tooling (Jira or equivalent) and Git-based workflows, including the delivery metrics they produce.
• Evidence of holding delivery teams to timelines and quality standards while retaining their trust and engagement.
• Ability to communicate delivery status, risk, and trade-offs to senior stakeholders with clarity and candour.

Qualifications

• Ideally, you’ll also have experience delivering AI or agentic AI systems, such as LLM-backed services, orchestration frameworks, agent tooling, or retrieval and knowledge pipelines.
• Experience running delivery for platform or infrastructure teams, where the product is the substrate other engineering teams build on.
• Experience with cost-aware delivery, quota and capacity planning, or FinOps practices.
• Scrum or Agile certification (CSM, PSM, SAFe, or equivalent), treated as useful supporting evidence rather than as