Technical Delivery Manager - Agentic AI Engineering (Manager)

We need to output HTML fragment with sections: About the role? The posting includes description: "At EY, we’re all in to shape your future with confidence..." etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Let's extract sections: - Location: "Anywhere in Country" (maybe not needed as heading; we can include in a short paragraph maybe 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 p. - 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." - 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 could be About the role. - Your Key Responsibilities: list of responsibilities (bulleted). We'll put under

Responsibilities

with

• each. - Skills And Attributes For Success: list of skills/attributes. Could be under

  Skills

  (or Skills And Attributes). We'll use Skills. - To qualify you must have ...: qualifications. Could be under

  Qualifications

  (or Requirements). We'll use Qualifications. - Ideally, you’ll also have ...: additional preferred experience. Could be under

  Preferred Qualifications

  but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Requirements" maybe similar to Qualifications. We could put the "To qualify you must have" under Qualifications, and the "Ideally, you’ll also have" under Skills? But Skills already used for skills/attributes. Maybe we can put the "Ideally" under Skills as additional bullet points. Or we could create a separate section "Requirements" for the mandatory qualifications, and "Qualifications" for the preferred? But we need to avoid duplication. Let's think: The posting has: - Skills And Attributes For Success (list) - To qualify you must have (list of mandatory qualifications) - Ideally, you’ll also have (list of preferred qualifications) We could map: - Skills: Skills And Attributes For Success - Qualifications: To qualify you must have (mandatory) - Requirements: Ideally, you’ll also have (preferred) maybe. But the instruction: "Prefer a few substantive sections over many thin ones." Could combine mandatory and preferred into Qualifications? But we need to preserve all info. Could have Qualifications section containing both mandatory and preferred, maybe with subheadings? But we cannot add extra headings beyond allowed? We can still use

  inside. Could just list all qualifications (mandatory and preferred) as a list under Qualifications. That would preserve all info. Then Skills section for skills/attributes. Thus:

  About the role

  with intro paragraphs (maybe combine the initial EY blurb and the opportunity paragraph). Could be two

  elements.

  Responsibilities

  with
  list.

  Skills

  with
  list of skills/attributes.

  Qualifications

  with
  list of mandatory and preferred qualifications (combine). Ensure we don't lose any detail. We also need Benefits, Pay, Schedule sections only if posting states them. The posting includes "What We Offer You" with description of compensation and benefits package, base salary range, total rewards, flexible vacation policy, etc. So we have Benefits and Pay info. Schedule not mentioned. So we should include Benefits and Pay sections. 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. Pay: base salary range for NYC/Boston/DC Metro, Washington State, Southern California: $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. We should include that as Pay section. Schedule: not mentioned, so omit. We also need to include location maybe as a short p under About the role or separate? Could be a short p before sections. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata, we can include a short p. We must remove boilerplate: EEO, legal, scam warning, application instructions, etc. Also remove duplicated lines. Let's craft HTML. We'll start with a p for location:

  Location: Anywhere in Country

  Then About the role: maybe two paragraphs: first the EY intro, second the opportunity description. We need to ensure we don't repeat the job title as heading (the page already shows it). So we don't add a heading for Technical Delivery Manager. Now Responsibilities list: extract each bullet from "Your Key Responsibilities". Let's list them: - 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 list from "Skills And Attributes For Success": - 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 each as
  • . Qualifications: combine mandatory and preferred. Mandatory (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. Preferred (Ideal, 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 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,