Engineering Delivery Manager II
Deloitte · Morristown, NJ · 1 mo ago
Hybrid$108k–$221k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to preserve all substantive info, remove boilerplate, duplicate lines, application instructions, etc. No job title heading. No Job ID. No cookie/legal etc.
We need to parse the posting.
Key content:
- Intro 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 (actually sentences). Let's extract:
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.
- Then "A successful candidate would possess these skills:" list of skills.
- Then "The Team US Deloitte Technology Product Engineering ..." paragraph.
- Then "Qualifications Required:" list.
- Then "Preferred:" list.
- Then "The wage range for this role ..." paragraph with $107,700 to $221,200 and discretionary annual incentive.
We need to decide sections: About the role (intro), Responsibilities (core responsibilities + work you'll do?), Requirements (Qualifications Required), Skills (skills list + preferred?), Benefits (maybe mention discretionary annual incentive?), Pay (wage range), Schedule (maybe mention travel 10%, limited immigration sponsorship, commutable distance, 3 days per week office). Those are schedule/location details.
We must not create sections with filler like "commensurate with experience". So we include only if real content.
Let's extract each.
**About the role**: The introductory paragraph up to recruiting end date. Could be considered About the role.
**Responsibilities**: Combine "Work you'll do" and the Core Responsibilities subpoints. Could be a single Responsibilities section with ul li.
**Requirements**: Qualifications Required list.
**Skills**: The list "A successful candidate would possess these skills:" plus Preferred list maybe combined as Skills.
**Benefits**: Discretionary annual incentive program mention. Also maybe mention limited immigration sponsorship? That's more like eligibility. Benefits could include discretionary annual incentive. Also maybe mention travel? That's not benefit. We'll include Benefits if we have something: "You may also be eligible to participate in a discretionary annual incentive program". That's a benefit.
**Pay**: Wage range $107,700 to $221,200.
**Schedule**: Travel 10%, limited immigration sponsorship may be available, candidates must be located within commutable distance to select locations, ability to work in local office at minimum 3 days per week. That's schedule/location.
We need to ensure we don't repeat info.
Now produce HTML:
. Let's gather all distinct responsibility statements.
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 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.
From Core Responsibilities (each heading with description). We'll extract each sentence as a bullet.
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."
We could split into two bullets: deliver outcomes; scope dashes.
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."
We need to ensure we don't duplicate similar statements (e.g., evidence-gated discipline appears multiple times). But we can keep them as they are distinct contexts; but to avoid redundancy maybe we can combine? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep each bullet as is, even if similar. However we might have duplicates like "proof signals read, harm watches honored" appears in Work you'll do and Discovery & Delivery Proficiency. That's duplicate content; we should not repeat duplicated lines. The instruction: remove duplicated lines. So we need to deduplicate identical sentences.
Let's list all responsibility statements and see duplicates.
List them:
1. Program-level coordination for one significant initiative or a set of related programs.
2. Ensure dashes start when slices are ready and end when deployed evidence confirms the intended behavior shifted.
3. 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.
4. Drive cost-efficient adoption of LLM, agentic AI, and cloud platforms through effective governance, FinOps practices, and consumption optimization.
5. Operational integrity of the evidence-gated cycle in your scope: proof signals being read, harm watches honored and exit gates respected before slices expand.
6. Deliver the right customer and business outcomes by engaging product teams on structure, skills, leverage models, and measurement.
7. Scope dashes against ready slices and observable evidence, so work advances when deployed evidence confirms the behavior shifted - not at a sprint boundary.
8. Champion fit-for-context delivery methodologies and work with Product Managers to drive priorities and execution.
9. Form skilled teams, remove roadblocks, and set cadence to the rhythm the program needs.
10. Surface coordination friction before it becomes a blocker, escalating to the Delivery Leader when it exceeds your authority.
11. Foster delivery excellence through quality processes, program value delivery, and team growth - coaching junior professionals via pairing, observation, and feedback.
12. 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.
13. Spread knowledge through community sessions.
14. Inspire and influence stakeholders, serving as the contact for value achievement across product engineering teams.
15. Communicate status accurately on the cadence the program needs.
16. Hold the room when stakeholders disagree: surface trade-offs, recommend a path, drive to decision.
17. Facilitate co-creation workshops.
18. Work as a connected member of the program alongside the triad ensemble (Product, Engineering and Experience) and cross functional groups.
19. Maintain a live picture of dependencies across the product teams and platform services you touch.
20. Manage conflict, foster collaboration, and enable cross-skilling.
21. Apply deep SDLC expertise with continuous planning and refinement.
22. Watch for drift between intent and execution and raise it early.
23. Hold evidence-gate discipline - proof signals read, harm watches honored, exits and expansions respected.
24. Identify risks, adapt scope, and embed continuous improvement.
25. Drive lean solutions through rapid experimentation, engaging customers before, during, and after delivery to land the right solution effectively.
26. Build inclusive, engaged teams; remove obstacles and coach
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to preserve all substantive info, remove boilerplate, duplicate lines, application instructions, etc. No job title heading. No Job ID. No cookie/legal etc.
We need to parse the posting.
Key content:
- Intro 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 (actually sentences). Let's extract:
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.
- Then "A successful candidate would possess these skills:" list of skills.
- Then "The Team US Deloitte Technology Product Engineering ..." paragraph.
- Then "Qualifications Required:" list.
- Then "Preferred:" list.
- Then "The wage range for this role ..." paragraph with $107,700 to $221,200 and discretionary annual incentive.
We need to decide sections: About the role (intro), Responsibilities (core responsibilities + work you'll do?), Requirements (Qualifications Required), Skills (skills list + preferred?), Benefits (maybe mention discretionary annual incentive?), Pay (wage range), Schedule (maybe mention travel 10%, limited immigration sponsorship, commutable distance, 3 days per week office). Those are schedule/location details.
We must not create sections with filler like "commensurate with experience". So we include only if real content.
Let's extract each.
**About the role**: The introductory paragraph up to recruiting end date. Could be considered About the role.
**Responsibilities**: Combine "Work you'll do" and the Core Responsibilities subpoints. Could be a single Responsibilities section with ul li.
**Requirements**: Qualifications Required list.
**Skills**: The list "A successful candidate would possess these skills:" plus Preferred list maybe combined as Skills.
**Benefits**: Discretionary annual incentive program mention. Also maybe mention limited immigration sponsorship? That's more like eligibility. Benefits could include discretionary annual incentive. Also maybe mention travel? That's not benefit. We'll include Benefits if we have something: "You may also be eligible to participate in a discretionary annual incentive program". That's a benefit.
**Pay**: Wage range $107,700 to $221,200.
**Schedule**: Travel 10%, limited immigration sponsorship may be available, candidates must be located within commutable distance to select locations, ability to work in local office at minimum 3 days per week. That's schedule/location.
We need to ensure we don't repeat info.
Now produce HTML: About the role
...
etc. We must not include markdown fences. Let's craft. First, About the role paragraph: combine the intro up to recruiting end date. Text: "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." Now Responsibilities: combine Work you'll do and Core Responsibilities bullet points. We need to list each as