Engineering Delivery Manager II
or drop it." So we can include recruiting end date in a paragraph. We need sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe qualifications?). Qualifications (maybe required qualifications). Skills (maybe preferred?). Benefits (maybe mention discretionary annual incentive program). Pay (wage range). Schedule (maybe travel 10%, office 3 days per week). Also maybe mention location/commutable distance. We must not create sections with filler like "commensurate with experience". We have actual pay range, so Pay section is valid. Schedule: we have travel 10% and office 3 days per week. That's schedule info. Benefits: discretionary annual incentive program. Also maybe mention limited immigration sponsorship? That's a benefit? Could be included but it's not exactly benefit; but we can include in Benefits or maybe in About. We'll include Benefits section with discretionary annual incentive program and limited immigration sponsorship. We must not include boilerplate like EEO etc. Not present. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract content:
About the role: first paragraph: "As a Delivery Manager, you hold program-level execution accountable on a day-to-day basis within Deloitte's Product Engineering organization, one or more product teams operating against a shared set of intents. Delivery in this organization operates inside an intent-driven development model with three concurrent layers - governance, execution, and learning - that run simultaneously. Execution advances in evidence-gated dashes, not sprints. The activities that used to define this role - status compilation, schedule maintenance, risk-log upkeep, and ceremony documentation - are increasingly AI-assisted. What remains, and grows, is the judgment work: cross-team coordination on initiatives larger than a single product team can self-coordinate, stakeholder alignment, dependency management, and the operational discipline that keeps evidence-gated delivery. Recruiting for this role ends on September 22nd 2026."
Then "Work you'll do:" bullet list (but it's prose with line breaks). We'll treat as responsibilities.
List of work you'll do:
- Program-level coordination for one significant initiative or a set of related programs.
- Ensure dashes start when slices are ready and end when deployed evidence confirms the intended behavior shifted.
- Day-to-day stakeholder orchestration with internal Deloitte stakeholders at the program level, including reconciliation of AI-drafted artifacts when stakeholders arrive with their own briefs.
- Drive cost-efficient adoption of LLM, agentic AI, and cloud platforms through effective governance, FinOps practices, and consumption optimization.
- Operational integrity of the evidence-gated cycle in your scope: proof signals being read, harm watches honored and exit gates respected before slices expand.
Then "Core Responsibilities" with subheadings: Outcome-Driven Leadership, Delivery Leadership and Advocacy, Craft Mastery, Communication, Cross-Functional Collaboration, Discovery & Delivery Proficiency, Customer-Centric Delivery, Operational Excellence, Engagement and Collaborative Co-Creation, Domain Expertise.
Each has bullet-like sentences. We'll need to capture them as list items under Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits. So we can combine all responsibilities into a single list, or multiple lists per subsection. Probably easiest: one
with all responsibility items.
We need to preserve all substantive info; we can break into subheadings inside the list? Not allowed; only headings are . Could have subheadings as ? Not allowed per instruction (only for section headings). So we should not add extra headings. We can keep the responsibility text as paragraphs? But they said use - for any list of duties/requirements/benefits. So we should put duties in a list. We can keep the descriptive sentences as list items.
Thus Responsibilities section:
Responsibilities
- ...
...
.
We need to include all responsibility sentences.
Let's extract each bullet from the "Core Responsibilities" sections:
Outcome-Driven Leadership:
- Deliver the right customer and business outcomes by engaging product teams on structure, skills, leverage models, and measurement.
- Scope dashes against ready slices and observable evidence, so work advances when deployed evidence confirms the behavior shifted - not at a sprint boundary.
Delivery Leadership and Advocacy:
- Champion fit-for-context delivery methodologies and work with Product Managers to drive priorities and execution.
- Form skilled teams, remove roadblocks, and set cadence to the rhythm the program needs.
- Surface coordination friction before it becomes a blocker, escalating to the Delivery Leader when it exceeds your authority.
Craft Mastery:
- Foster delivery excellence through quality processes, program value delivery, and team growth - coaching junior professionals via pairing, observation, and feedback.
- Experiment with new tools like GenAI and support the AI Workflow Orchestrator on your program, knowing which workflows are AI-driven and how exceptions route.
- Spread knowledge through community sessions.
Communication:
- Inspire and influence stakeholders, serving as the contact for value achievement across product engineering teams.
- Communicate status accurately on the cadence the program needs.
- Hold the room when stakeholders disagree: surface trade-offs, recommend a path, drive to decision.
- Facilitate co-creation workshops.
Cross-Functional Collaboration:
- Work as a connected member of the program alongside the triad ensemble (Product, Engineering and Experience) and cross functional groups.
- Maintain a live picture of dependencies across the product teams and platform services you touch.
- Manage conflict, foster collaboration, and enable cross-skilling.
Discovery & Delivery Proficiency:
- Apply deep SDLC expertise with continuous planning and refinement.
- Watch for drift between intent and execution and raise it early.
- Hold evidence-gate discipline - proof signals read, harm watches honored, exits and expansions respected.
- Identify risks, adapt scope, and embed continuous improvement.
Customer-Centric Delivery:
- Drive lean solutions through rapid experimentation, engaging customers before, during, and after delivery to land the right solution effectively.
Operational Excellence:
- Build inclusive, engaged teams; remove obstacles and coach; improve satisfaction and reduce attrition.
- Govern the intake of AI-drafted artifacts so they become productive inputs, not noise.
- Report on financials, innovation, and engagement, and drive efficiency and productivity.
Engagement and Collaborative Co-Creation:
- Engage stakeholders at all levels and foster a culture of co-creation.
- Hold the relationship with program sponsors and affected stakeholders, informing them in proportion to their stake, and reconcile conflicting AI-generated artifacts on the same initiative.
- Align diverse perspectives to deliver quality solutions.
Domain Expertise:
- Rapidly acquire domain-specific knowledge and navigate enterprise functions to drive product value and organizational alignment.
Also earlier "Work you'll do" items we should include as responsibilities as well. So add those.
Now Requirements section: maybe we separate Required qualifications vs Preferred? The instruction: Use sections Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have "Qualifications Required:" list (10+ years..., etc). Also "Preferred:" list.
We also have "A successful candidate would possess these skills:" list (soft skills). That could go under Skills.
We have "The Team ..." description maybe About the role? Could be part of About.
We have wage range and discretionary annual incentive program -> Pay and Benefits.
We have travel 10%, office 3 days per week -> Schedule.
We have location/commutable distance -> maybe About or Schedule? Could be in About.
We must not create sections with filler. So we will include:
- About the role: intro paragraph + The Team description + location note + recruiting end date.
- Responsibilities: as described.
- Requirements: maybe the "Qualifications Required:" list (hard requirements). Could also include "Preferred:" as part of Requirements? But we have separate Qualifications section maybe for preferred? Let's map:
Qualifications Required: could go under Requirements.
Preferred: could go under Qualifications (or Skills). But we also have Skills section for soft skills list.
Thus:
Requirements (Requirements
) list the required qualifications.
Qualifications (Qualifications
) list the preferred qualifications.
Skills (Skills
) list the "A successful candidate would possess these skills:" list.
Benefits (Benefits
) list discretionary annual incentive program and limited immigration sponsorship.
Pay (Pay
) wage range.
Schedule (Schedule
) travel 10%, office 3 days per week.
We must ensure we don't create sections with placeholder text. All have real content.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
We'll need to escape any special characters? Not needed.
We'll produce:
About the role
As a Delivery Manager, you hold program-level execution accountable on a day-to-day basis within Deloitte's Product Engineering organization, one or more product teams operating against a shared set of intents. Delivery in this organization operates inside an intent-driven development model with three concurrent layers - governance, execution, and learning - that run simultaneously. Execution advances in evidence-gated dashes, not sprints. The activities that used to define this role - status compilation, schedule maintenance, risk-log upkeep, and ceremony documentation - are increasingly AI-assisted. What remains, and grows, is the judgment work: cross-team coordination on initiatives larger than a single product team can self-coordinate, stakeholder alignment, dependency management, and the operational discipline that keeps evidence-gated delivery. Recruiting for this role ends on September 22nd 2026. The US Deloitte Technology Product Engineering team has modernized software and product delivery, creating a scalable, cost-effective model that focuses on value and outcomes. It leverages a progressive and responsive talent structure across a four-capability matrix: Product, Experience, Engineering, and Delivery. As Deloitte's primary product development team, Product Engineering delivers innovative digital solutions to businesses, service lines, and internal operations with proven bottom-line results. We develop and deploy cutting-edge go-to-market solutions that help Deloitte operate effectively and lead in the market. Candidates must be located within a commutable distance to one of the select locations available for this role and are expected to work in the local office at a minimum of 3 days per week.
But note we moved office 3 days per week to About; but we also have Schedule section for travel and office days. Might duplicate. Better keep schedule separate: About includes location note and recruiting end date; Schedule includes travel 10% and office 3 days per week. So we should not include office days in About. Let's adjust.
About: include intro, The Team description, location note, recruiting end date.
Schedule: travel 10%, office 3 days per week.
Thus About paragraph: include location note and recruiting end date.
Now Responsibilities: combine "Work you'll do" items and Core Responsibility items.
Let's list all responsibility items:
From Work you'll do:
- Program-level coordination for one significant initiative or a set of related programs.
- Ensure dashes start when slices are ready and end when deployed evidence confirms the intended behavior shifted.
- Day-to-day stakeholder orchestration
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting. Let's extract content: About the role: first paragraph: "As a Delivery Manager, you hold program-level execution accountable on a day-to-day basis within Deloitte's Product Engineering organization, one or more product teams operating against a shared set of intents. Delivery in this organization operates inside an intent-driven development model with three concurrent layers - governance, execution, and learning - that run simultaneously. Execution advances in evidence-gated dashes, not sprints. The activities that used to define this role - status compilation, schedule maintenance, risk-log upkeep, and ceremony documentation - are increasingly AI-assisted. What remains, and grows, is the judgment work: cross-team coordination on initiatives larger than a single product team can self-coordinate, stakeholder alignment, dependency management, and the operational discipline that keeps evidence-gated delivery. Recruiting for this role ends on September 22nd 2026." Then "Work you'll do:" bullet list (but it's prose with line breaks). We'll treat as responsibilities. List of work you'll do: - Program-level coordination for one significant initiative or a set of related programs. - Ensure dashes start when slices are ready and end when deployed evidence confirms the intended behavior shifted. - Day-to-day stakeholder orchestration with internal Deloitte stakeholders at the program level, including reconciliation of AI-drafted artifacts when stakeholders arrive with their own briefs. - Drive cost-efficient adoption of LLM, agentic AI, and cloud platforms through effective governance, FinOps practices, and consumption optimization. - Operational integrity of the evidence-gated cycle in your scope: proof signals being read, harm watches honored and exit gates respected before slices expand. Then "Core Responsibilities" with subheadings: Outcome-Driven Leadership, Delivery Leadership and Advocacy, Craft Mastery, Communication, Cross-Functional Collaboration, Discovery & Delivery Proficiency, Customer-Centric Delivery, Operational Excellence, Engagement and Collaborative Co-Creation, Domain Expertise. Each has bullet-like sentences. We'll need to capture them as list items under Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits. So we can combine all responsibilities into a single list, or multiple lists per subsection. Probably easiest: one
- with all responsibility items.
We need to preserve all substantive info; we can break into subheadings inside the list? Not allowed; only headings are
- for any list of duties/requirements/benefits. So we should put duties in a list. We can keep the descriptive sentences as list items.
Thus Responsibilities section:
Responsibilities
- ... ...
Requirements
) list the required qualifications. Qualifications (Qualifications
) list the preferred qualifications. Skills (Skills
) list the "A successful candidate would possess these skills:" list. Benefits (Benefits
) list discretionary annual incentive program and limited immigration sponsorship. Pay (Pay
) wage range. Schedule (Schedule
) travel 10%, office 3 days per week. We must ensure we don't create sections with placeholder text. All have real content. Now we need to output only HTML fragment, no /, no markdown. Let's craft. We'll need to escape any special characters? Not needed. We'll produce:About the role
As a Delivery Manager, you hold program-level execution accountable on a day-to-day basis within Deloitte's Product Engineering organization, one or more product teams operating against a shared set of intents. Delivery in this organization operates inside an intent-driven development model with three concurrent layers - governance, execution, and learning - that run simultaneously. Execution advances in evidence-gated dashes, not sprints. The activities that used to define this role - status compilation, schedule maintenance, risk-log upkeep, and ceremony documentation - are increasingly AI-assisted. What remains, and grows, is the judgment work: cross-team coordination on initiatives larger than a single product team can self-coordinate, stakeholder alignment, dependency management, and the operational discipline that keeps evidence-gated delivery. Recruiting for this role ends on September 22nd 2026. The US Deloitte Technology Product Engineering team has modernized software and product delivery, creating a scalable, cost-effective model that focuses on value and outcomes. It leverages a progressive and responsive talent structure across a four-capability matrix: Product, Experience, Engineering, and Delivery. As Deloitte's primary product development team, Product Engineering delivers innovative digital solutions to businesses, service lines, and internal operations with proven bottom-line results. We develop and deploy cutting-edge go-to-market solutions that help Deloitte operate effectively and lead in the market. Candidates must be located within a commutable distance to one of the select locations available for this role and are expected to work in the local office at a minimum of 3 days per week.
But note we moved office 3 days per week to About; but we also have Schedule section for travel and office days. Might duplicate. Better keep schedule separate: About includes location note and recruiting end date; Schedule includes travel 10% and office 3 days per week. So we should not include office days in About. Let's adjust. About: include intro, The Team description, location note, recruiting end date. Schedule: travel 10%, office 3 days per week. Thus About paragraph: include location note and recruiting end date. Now Responsibilities: combine "Work you'll do" items and Core Responsibility items. Let's list all responsibility items: From Work you'll do: - Program-level coordination for one significant initiative or a set of related programs. - Ensure dashes start when slices are ready and end when deployed evidence confirms the intended behavior shifted. - Day-to-day stakeholder orchestration
. Could have subheadings as
? Not allowed per instruction (only
for section headings). So we should not add extra headings. We can keep the responsibility text as paragraphs? But they said use
- for any list of duties/requirements/benefits. So we should put duties in a list. We can keep the descriptive sentences as list items.
Thus Responsibilities section: