Technical Delivery Manager - Agentic AI Engineering (Manager)
EY · Chattanooga, TN · 1 mo ago
Hybrid$173k–$359k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about EY and opportunity. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must 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. Also maybe "About the role" could be the intro paragraph(s) before responsibilities. The posting includes: "Location: Anywhere in Country At EY, we’re all in to shape your future with confidence.... The opportunity We are seeking a seasoned Technical Delivery Manager..." That could be considered About the role. We'll put that in
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must 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. Also maybe "About the role" could be the intro paragraph(s) before responsibilities. The posting includes: "Location: Anywhere in Country At EY, we’re all in to shape your future with confidence.... The opportunity We are seeking a seasoned Technical Delivery Manager..." That could be considered About the role. We'll put that in About the role
with paragraphs.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, legal, etc. Remove application instructions, cookie/navigation, etc. Also remove duplicated lines. We'll keep substantive info.
We need to use - for any list of duties/requirements/benefits. The responsibilities are a list of bullet-like sentences but they are in paragraph with each duty separated by periods. We could convert each duty into
- . Similarly for skills/attributes, qualifications, benefits.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to capture each bullet.
Let's extract responsibilities list:
- 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 11 items.
Skills and Attributes For Success list:
- 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.
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.
Ideally, you’ll also have (these are "Ideally" but still substantive; we could include under Qualifications or maybe a separate "Preferred Qualifications". But we only have headings: Qualifications, Skills, Benefits, Pay, etc. We could include these under Qualifications as additional bullet points. Or we could create a separate section "Preferred Qualifications" but not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those. So we can incorporate the "Ideally" items under Qualifications as additional bullets.
Benefits (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.
- 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,000; Bay Area California offices – $180,000 to $374,000; All other offices locations in the US, including Sacramento – $144,000 to $329,100. Individual 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.
Pay: we could extract base salary range as separate Pay section. But the Benefits section already includes salary. However instruction: "Prefer a few substantive sections over many thin ones." We could combine Pay into Benefits or have separate Pay. Since they explicitly list Pay as a possible heading, we could create a Pay section with the salary ranges. Benefits section then would include other benefits (medical, dental, pension, 401k, vacation). Let's do that.
Thus sections:
- About the role (intro paragraphs)
- Responsibilities (list)
- Skills (list)
- Qualifications (list)
- Benefits (list of non-salary benefits)
- Pay (list of salary ranges)
We must not include Requirements heading if not present; we have Qualifications.
We must not include Schedule.
Now produce HTML fragment.
We need to wrap each section: About the role
then
... maybe multiple paragraphs. The intro includes location line and some fluff. We'll keep location line? It's "Location: Anywhere in Country". That's minor metadata; we could fold into short
or drop. Probably keep as a short p.
Thus:
About the role
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.
That seems to capture the intro.
Now Responsibilities:
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
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those. So we can incorporate the "Ideally" items under Qualifications as additional bullets.
Benefits (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.
- 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,000; Bay Area California offices – $180,000 to $374,000; All other offices locations in the US, including Sacramento – $144,000 to $329,100. Individual 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.
Pay: we could extract base salary range as separate Pay section. But the Benefits section already includes salary. However instruction: "Prefer a few substantive sections over many thin ones." We could combine Pay into Benefits or have separate Pay. Since they explicitly list Pay as a possible heading, we could create a Pay section with the salary ranges. Benefits section then would include other benefits (medical, dental, pension, 401k, vacation). Let's do that.
Thus sections:
- About the role (intro paragraphs)
- Responsibilities (list)
- Skills (list)
- Qualifications (list)
- Benefits (list of non-salary benefits)
- Pay (list of salary ranges)
We must not include Requirements heading if not present; we have Qualifications.
We must not include Schedule.
Now produce HTML fragment.
We need to wrap each section: About the role
then
... maybe multiple paragraphs. The intro includes location line and some fluff. We'll keep location line? It's "Location: Anywhere in Country". That's minor metadata; we could fold into short
or drop. Probably keep as a short p. Thus:
About the role
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.
That seems to capture the intro. Now Responsibilities: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