Engineering Delivery Manager II

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections based on content. We have job description: includes description of role, responsibilities, qualifications, skills, pay range, maybe benefits (discretionary annual incentive program). Also schedule: maybe mention travel 10%, ability to work in local office min 3 days per week. That's schedule? Could be schedule: hybrid (3 days office). Also maybe location? Not schedule. We must not include boilerplate like recruiting end date? That's metadata; we can fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Recruiting end date is metadata; we can include in a short p maybe under About the role? Or just drop? Probably include as a short p. We must preserve all substantive information; do not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". Pay section: we have wage range $107,700 to $221,200 and discretionary annual incentive program. That's substantive, so include Pay section. Benefits: mention discretionary annual incentive program (maybe also other benefits not listed). Could treat that as Benefits? But they said Benefits section only if posting actually states them. The posting mentions "You may also be eligible to participate in a discretionary annual incentive program". That's a benefit. So we can include Benefits section with that. Schedule: mention travel 10%, ability to work in local office at minimum 3 days per week. That's schedule info. So include Schedule section. Qualifications: we have Required qualifications list and Preferred qualifications. We'll put under Qualifications (maybe separate Required and Preferred as lists). Skills: they list a bunch of skills under "A successful candidate would possess these skills:" and also under Preferred. Those are skills. Could combine under Skills section. Responsibilities: we have "Work you'll do:" bullet list and then "Core Responsibilities" with many subheadings. We'll combine into Responsibilities section. About the role: initial paragraph describing role. We'll put that. We must not repeat job title as heading. So no

Delivery Manager. We need to output only HTML fragment, no /. Use

for each section heading. Use

• for lists. Use

  for prose. We must ensure we don't include empty sections. 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." Then maybe also mention recruiting end date? We'll include as a short p: "Recruiting for this role ends on September 22nd 2026." Now Responsibilities: we have "Work you'll do:" bullet list (4 items) then "Core Responsibilities" with many subheadings each with description. We'll combine all into a single list? Might be long; but we can keep as list items each representing a responsibility. Could also keep subheadings as inside

• . But instruction: use
  • for any list of duties/requirements/benefits. So we can make a
    with each responsibility as
    • . For subheadings we can bold. Let's list responsibilities from text: 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. Core Responsibilities (with headings): 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. We'll turn each of these into
    • with bold heading. Now Qualifications: Required qualifications list (numbered). We'll make a
      list. Required: - 10+ years of delivery management with direct experience leading a cross-functional program or set of programs with meaningful dependencies and multiple stakeholders. - Experience operating inside an Agile or Lean model and demonstrated readiness to operate inside intent-driven, evidence-gated delivery patterns. - Experience working in a product-staffed model where durable product teams stay with their products across build, deploy, operate, and evolve. - Strong expertise in AI/Cloud FinOps, budget management, financial forecasting, vendor management, cost optimization, and data-driven delivery governance. - Ability to travel 10%, on average, based on the work you do and the clients and industries/sectors you serve. - Limited immigration sponsorship may be available. - Candidates must be located within a commutable distance to one of the select locations available for this role - Ability to work in your local office at a minimum of 3 days per week Preferred: - Coordination at scale: Track record of managing dependencies, surfacing risks, and driving alignment across teams that do not naturally talk to each other. - Engineering fluency: Able to follow technical conversations, ask useful questions, and challenge feasibility claims constructively. More than passive listening. - Evidence orientation: Comfortable measuring delivery by outcome validation rather than velocity proxies. Able to hold the line on evidence gates. - AI-augmented working practice: Fluent with current GenAI assistants and agentic delivery tooling. Able to direct AI output for status, risk, and coordination tasks rather than only consume or produce it manually. - Specification literacy: Able to read and reason about charter, persona, intent, constitution, and blueprint artifacts and understand how a program is governed through them. - Communication: Writes clearly. Presents to senior stakeholders without over formatting. Tells the truth about status, including bad news, without varnish. Now Skills: The list under "A successful candidate would possess these skills:" includes: - Ability to work independently and collaborate as part of a team - Effective written and verbal communication skills - Meticulous attention to detail and quality of work product - Ability to build and sustain professional relationships - Ability to lead projects or workstreams - Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment - Strong interpersonal skills and professional demeanor - Ability to meet deadlines - Ability to mentor and provide clear guidance to others We could combine with Preferred skills but they are separate. We'll make a Skills section with that list. Pay: wage range $107,700 to $221,200. Also mention discretionary annual incentive program. We'll put both in Pay section maybe as

      . Benefits: discretionary annual incentive program (maybe also other benefits not listed). We'll put that as Benefits. Schedule: travel 10%, ability to work in local office min 3 days per week. Also maybe mention location? Not schedule. We'll put schedule. Now ensure we don't duplicate content: travel 10% appears both in Qualifications (Required) and Schedule. We should not duplicate; but we need to preserve all substantive information. If we put travel 10% in Qualifications (as required) and also in Schedule, that's duplication. Better to keep it only once. Where does it belong? It's a requirement (ability to travel 10%). Could be considered schedule? The instruction: schedule section only if posting actually states them. The posting states ability to travel 10%, on average, based on work. That's more of a requirement than schedule. However schedule could include travel expectation and office days. We could keep travel 10% under Qualifications (Required) and schedule includes office days (minimum 3 days per week). That avoids duplication. Thus Schedule: Ability to work in your local office at a minimum of 3 days per week. Now Benefits: discretionary annual incentive program. Now Pay: wage range and maybe mention that it's not typical to be hired at top of range etc. That's substantive; we should include that description as well. The paragraph about wage range includes many sentences. We'll include all that as

      under Pay. Now ensure we don't include boilerplate like EEO etc. Not present. Now produce HTML. Structure:

      About the role

      ...

      Recruiting for this role ends on September 22nd 2026.

      Responsibilities

      • 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