Technical Delivery Manager - Agentic AI Engineering (Manager)
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. No metadata like Job ID. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - Location: Anywhere in Country (maybe not needed? It's metadata; we can drop or put in short p). 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 p. - Intro paragraph: "At EY, we’re all in to shape your future with confidence..." etc. That's about the role? Could be "About the role". We'll treat that as About the role. - The opportunity paragraph: "We are seeking a seasoned Technical Delivery Manager..." That's also about role. - Then "Your Key Responsibilities" list: many bullet points. That's Responsibilities. - Then "Skills And Attributes For Success": list of bullet points. That's Skills. - Then "To qualify you must have...": that's Requirements/Qualifications. Could split into Requirements (education, experience) and Qualifications (maybe same). But we can combine into Requirements. - Then "Ideally, you’ll also have...": that's additional preferred qualifications; could be part of Qualifications or Skills? Probably Qualifications (preferred). We'll include under Qualifications. - Then "What We Offer You": includes benefits description, salary ranges, etc. That's Benefits and Pay. We need separate sections for Benefits and Pay if content exists. The posting includes base salary range details and total rewards package (medical, dental, pension, 401k, PTO, flexible vacation). So we can have Pay section with salary ranges, and Benefits section with medical/dental, pension, 401k, PTO, flexible vacation, holidays, etc. - Schedule: not mentioned. So we should not create Schedule section. - Also there is some fluff about applying etc. Remove application instructions. - Also there is EEO statement etc. Remove. - Also there is "EY | Building a better working world" etc. Remove. Thus sections: About the role, Responsibilities, Skills, Requirements (or Qualifications), Benefits, Pay. We need to use
for each section heading. Use - for lists. Use
for prose.
We must not repeat job title as heading. So no heading for "Technical Delivery Manager". Good.
We need to preserve all substantive information. Let's extract.
About the role: combine intro paragraphs.
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 can make that as About the role.
Responsibilities: list bullet points under "Your Key Responsibilities". Let's capture each bullet:
- 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.
That's responsibilities.
Skills And Attributes For Success: list bullet points:
- 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.
That's skills.
Qualifications/Requirements: "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 requirements.
Ideally, you’ll also have: list:
- 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.
These are preferred qualifications; we can include under Qualifications as "Preferred Qualifications" or just add to Qualifications.
We need to decide sections: maybe Requirements (mandatory) and Qualifications (preferred). But instruction: Prefer a few substantive sections over many thin ones. Could combine into one "Requirements" section covering both mandatory and preferred. But we need to keep headings meaningful. Could have "Requirements" and "Preferred Qualifications". That's two sections. Might be okay.
But we also have Benefits and Pay.
Benefits: from "What We Offer You": "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." Then details: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. Under flexible vacation policy, decide how much vacation time you need based on personal circumstances. Also granted time off for designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, and other leaves of absence when needed to support physical, financial, and emotional well-being.
Thus Benefits section: medical, dental, pension, 401k, paid time off, flexible vacation, holidays, winter/summer breaks, personal/family care, other leaves.
Pay: base salary range details: New York City, Boston, Washington DC Metro Areas, Washington State, Southern California offices – $172,800 to $359,000; Bay Area California offices – $180,000 to $374,000; All other offices locations in the US, including Sacramento – $144,000 to $329,100. Also note individual salaries determined by factors.
Thus Pay section.
Schedule: none.
We also have location: "Location: Anywhere in Country". Could be a short p at top.
We must not include boilerplate like "Learn more at ey.com/us/careers." That's part of What We Offer You? Actually appears after "Learn more at ey.com/us/careers." That's a link; we can drop as it's navigation/link. Also "Apply today." etc. Remove application instructions.
Also remove "Under our flexible vacation policy..." we kept.
Also remove "Are you ready to shape your future with confidence? Apply today." etc.
Also remove "To make the most of your application experience, please limit yourself to two applications within a six-month period." etc.
Also remove "EY accepts applications for this position on an on-going basis." etc.
Also remove "For those living in California, please click here
for prose. We must not repeat job title as heading. So no heading for "Technical Delivery Manager". Good. We need to preserve all substantive information. Let's extract. About the role: combine intro paragraphs. 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 can make that as About the role. Responsibilities: list bullet points under "Your Key Responsibilities". Let's capture each bullet: - 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. That's responsibilities. Skills And Attributes For Success: list bullet points: - 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. That's skills. Qualifications/Requirements: "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 requirements. Ideally, you’ll also have: list: - 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. These are preferred qualifications; we can include under Qualifications as "Preferred Qualifications" or just add to Qualifications. We need to decide sections: maybe Requirements (mandatory) and Qualifications (preferred). But instruction: Prefer a few substantive sections over many thin ones. Could combine into one "Requirements" section covering both mandatory and preferred. But we need to keep headings meaningful. Could have "Requirements" and "Preferred Qualifications". That's two sections. Might be okay. But we also have Benefits and Pay. Benefits: from "What We Offer You": "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." Then details: medical and dental coverage, pension and 401(k) plans, wide range of paid time off options. Under flexible vacation policy, decide how much vacation time you need based on personal circumstances. Also granted time off for designated EY Paid Holidays, Winter/Summer breaks, Personal/Family Care, and other leaves of absence when needed to support physical, financial, and emotional well-being. Thus Benefits section: medical, dental, pension, 401k, paid time off, flexible vacation, holidays, winter/summer breaks, personal/family care, other leaves. Pay: base salary range details: New York City, Boston, Washington DC Metro Areas, Washington State, Southern California offices – $172,800 to $359,000; Bay Area California offices – $180,000 to $374,000; All other offices locations in the US, including Sacramento – $144,000 to $329,100. Also note individual salaries determined by factors. Thus Pay section. Schedule: none. We also have location: "Location: Anywhere in Country". Could be a short p at top. We must not include boilerplate like "Learn more at ey.com/us/careers." That's part of What We Offer You? Actually appears after "Learn more at ey.com/us/careers." That's a link; we can drop as it's navigation/link. Also "Apply today." etc. Remove application instructions. Also remove "Under our flexible vacation policy..." we kept. Also remove "Are you ready to shape your future with confidence? Apply today." etc. Also remove "To make the most of your application experience, please limit yourself to two applications within a six-month period." etc. Also remove "EY accepts applications for this position on an on-going basis." etc. Also remove "For those living in California, please click here