Technical Delivery Manager - Agentic AI Engineering (Manager)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have content for responsibilities (Your Key Responsibilities). Skills and Attributes For Success (skills). Qualifications (To qualify you must have...). Benefits (What We Offer You). Pay (base salary range). Schedule? Not mentioned. So we should not include Schedule section. Also maybe About the role: we have introductory paragraphs describing role. Could treat as About the role. The "The opportunity" paragraph maybe part of About the role. We'll include About the role section with that content.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Remove lines about equal opportunity, accommodation, etc. Also remove application instructions like "Apply today", "limit yourself to two applications", etc. Also remove "For those living in California..." etc. Also remove "EY | Building a better working world" etc. Also remove "EY provides equal employment opportunities..." etc. Also remove "EY is committed to providing reasonable accommodation..." etc.
We need to preserve all substantive information: location, description, responsibilities, skills, qualifications, benefits, pay.
We need to use - for any list of duties/requirements/benefits. The responsibilities are a list of bullet-like sentences each starting with a verb. We'll put them in
- . Similarly skills list maybe bullet? It's a paragraph with bullet-like sentences separated by periods. We'll convert to list. Qualifications also list. Benefits list.
We need to use
for prose.
We must not repeat job title as heading. No Job ID.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is present, Benefits present. Schedule not present.
We must not emit heading followed by filler/placeholder text. Ensure each section has substantive content.
Let's extract content.
Location: "Anywhere in Country". Could be included in About the role paragraph.
About the role: combine first paragraphs: "Location: Anywhere in Country 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."
We'll put that in
.
Responsibilities: list each bullet from "Your Key Responsibilities". Let's extract each sentence that starts with a capital verb.
- 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.
We'll put each as
- .
Skills And Attributes For Success: list each bullet.
- Genuine technical depth: able to read code, follow an architecture or design review, and form an independent view of how hard a piece of work actually is.
- Constructive scepticism: willing to challenge an estimate, a blocker, or a “nearly done”, and to press for specifics, without putting the team on the defensive.
- Credibility with senior engineers: respect earned through technical understanding and sound judgement rather than through process authority.
- Strong command of Agile practice across Scrum and Kanban, with the judgement to adapt the process to the work instead of running the ceremony for its own sake.
- Comfortable holding people to commitments: direct, early, and specific in difficult conversations, with escalation as a considered step rather than a first move.
- Evidence-driven: reports what the delivery data shows, not what leadership would prefer to hear.
- Strong communicator, able to move between a technical design discussion, a sprint-level trade-off, and an executive delivery update without losing precision.
- Calm and steady under pressure, keeping a team delivering when dates are tight, scope is contested, and priorities are shifting.
We'll put as
- .
Qualifications: "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."
We can split into list items.
Ideal qualifications (Ideal, you’ll also have) maybe separate but could be included as additional qualifications but not required. We'll include as part of Qualifications maybe as additional bullet list under "Preferred qualifications". But we only have sections: Qualifications. Could include both required and preferred. We'll just list all.
Ideal items:
- 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 a substitute for technical depth.
- Experience in regulated delivery environments (financial services, tax, audit, healthcare, risk) with audit-grade evidence requirements.
- A track record of introducing flow metrics such as cycle time, throughput, and flow efficiency, and improving them measurably.
- Exposure to multi-environment delivery across cloud, on-prem, edge, client-managed, and air-gapped targets.
We'll include these as list items under Qualifications.
Benefits: "What We Offer You At EY, we harness our collective strength to empower you to shape your future with confidence through professional growth, personal fulfillment and an inclusive culture. Learn more at ey.com/us/careers. We offer a comprehensive compensation and benefits package where you’ll be rewarded based on your performance and recognized for the value you bring to the business. The base salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $172,800 to $359,000Bay Area California offices – $180,000 to $374,000All other offices locations in the US, including Sacramento – $144,000 to $329,100Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography. In addition, our Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options.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."
We need Benefits section (maybe includes description). Pay section separate for salary range. Benefits section could include medical, dental, pension, 401k, paid time off, flexible vacation, holidays, etc.
We'll separate Pay and Benefits.
Pay: include the salary ranges.
We need to avoid filler like "Individual salaries within these ranges are determined through a wide variety of factors..." That's substantive, we can keep as prose.
We'll put Pay section with
Pay
and then containing the salary ranges and note about determination.
Benefits:
Benefits
with describing medical, dental, pension, 401k, paid time off, flexible vacation, holidays, etc. Could also include list.
We'll use
- for benefits list.
Now we need to strip out boilerplate: lines about "Learn more at ey.com/us/careers." maybe keep? It's part of benefits description but could be considered navigation? It's a link; maybe we keep as it's part of offering. But it's not essential; we could keep but it's okay. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "
- . Similarly skills list maybe bullet? It's a paragraph with bullet-like sentences separated by periods. We'll convert to list. Qualifications also list. Benefits list.
We need to use
for prose. We must not repeat job title as heading. No Job ID. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is present, Benefits present. Schedule not present. We must not emit heading followed by filler/placeholder text. Ensure each section has substantive content. Let's extract content. Location: "Anywhere in Country". Could be included in About the role paragraph. About the role: combine first paragraphs: "Location: Anywhere in Country 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." We'll put that in
. Responsibilities: list each bullet from "Your Key Responsibilities". Let's extract each sentence that starts with a capital verb. - 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. We'll put each as
- . Skills And Attributes For Success: list each bullet. - Genuine technical depth: able to read code, follow an architecture or design review, and form an independent view of how hard a piece of work actually is. - Constructive scepticism: willing to challenge an estimate, a blocker, or a “nearly done”, and to press for specifics, without putting the team on the defensive. - Credibility with senior engineers: respect earned through technical understanding and sound judgement rather than through process authority. - Strong command of Agile practice across Scrum and Kanban, with the judgement to adapt the process to the work instead of running the ceremony for its own sake. - Comfortable holding people to commitments: direct, early, and specific in difficult conversations, with escalation as a considered step rather than a first move. - Evidence-driven: reports what the delivery data shows, not what leadership would prefer to hear. - Strong communicator, able to move between a technical design discussion, a sprint-level trade-off, and an executive delivery update without losing precision. - Calm and steady under pressure, keeping a team delivering when dates are tight, scope is contested, and priorities are shifting. We'll put as
- .
Qualifications: "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."
We can split into list items.
Ideal qualifications (Ideal, you’ll also have) maybe separate but could be included as additional qualifications but not required. We'll include as part of Qualifications maybe as additional bullet list under "Preferred qualifications". But we only have sections: Qualifications. Could include both required and preferred. We'll just list all.
Ideal items:
- 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 a substitute for technical depth.
- Experience in regulated delivery environments (financial services, tax, audit, healthcare, risk) with audit-grade evidence requirements.
- A track record of introducing flow metrics such as cycle time, throughput, and flow efficiency, and improving them measurably.
- Exposure to multi-environment delivery across cloud, on-prem, edge, client-managed, and air-gapped targets.
We'll include these as list items under Qualifications.
Benefits: "What We Offer You At EY, we harness our collective strength to empower you to shape your future with confidence through professional growth, personal fulfillment and an inclusive culture. Learn more at ey.com/us/careers. We offer a comprehensive compensation and benefits package where you’ll be rewarded based on your performance and recognized for the value you bring to the business. The base salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $172,800 to $359,000Bay Area California offices – $180,000 to $374,000All other offices locations in the US, including Sacramento – $144,000 to $329,100Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography. In addition, our Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options.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."
We need Benefits section (maybe includes description). Pay section separate for salary range. Benefits section could include medical, dental, pension, 401k, paid time off, flexible vacation, holidays, etc.
We'll separate Pay and Benefits.
Pay: include the salary ranges.
We need to avoid filler like "Individual salaries within these ranges are determined through a wide variety of factors..." That's substantive, we can keep as prose.
We'll put Pay section with
Pay
and thencontaining the salary ranges and note about determination. Benefits:
Benefits
withdescribing medical, dental, pension, 401k, paid time off, flexible vacation, holidays, etc. Could also include list. We'll use
- for benefits list. Now we need to strip out boilerplate: lines about "Learn more at ey.com/us/careers." maybe keep? It's part of benefits description but could be considered navigation? It's a link; maybe we keep as it's part of offering. But it's not essential; we could keep but it's okay. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "