IDO Delivery Manager
for each section.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we should exclude the accommodation link and maybe the sentence about "Information for applicants with a need for accommodation". Also exclude any duplicated lines (none seen). Also exclude any generic filler like "commensurate with experience" etc. Not present.
Now craft sections:
1. About the role (or About the practice). Use first paragraph.
2. Responsibilities: from "Work you'll do" paragraph(s). It includes multiple sentences; we can turn into list items.
Let's extract responsibilities:
- Lead core delivery execution for industrial data and analytics engagements, coordinating onshore and offshore teams while managing clear, client-facing delivery communications.
- Help translate technical work into practical delivery plans, keep execution moving across teams, and support alignment between client stakeholders, delivery teams, and platform partners.
- Own the design oversight of the data integration layer between operational technology (OT) sources and cloud analytics platforms, including lakehouse schemas, time-series mapping, cloud landing zone architecture, and pipeline patterns.
- This role requires enough hands-on data platform depth to review offshore data engineering output, identify architectural risks, and guide corrections.
- Early in engagements, you may coordinate with Databricks and AWS alliance solution architects for platform-specific design input.
We could also include "Ideal background is a data platform architect or senior data engineer who has led delivery on industrial data or manufacturing analytics programs and moved into delivery leadership from a technical foundation." That's more of qualification/ideal background; maybe put under Qualifications or Requirements.
But we already have Qualifications section.
We'll keep responsibilities as above.
3. Requirements: maybe combine Qualifications and Skills? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need separate Requirements and Qualifications and Skills.
We need to decide what goes where.
Typically:
- Requirements: mandatory items (experience, education, travel, work authorization).
- Qualifications: maybe preferred qualifications? But they have "Required Experience" and "Preferred:" list.
- Skills: list of abilities (Ability to work independently...).
Thus:
Requirements:
- Bachelor's degree
- 8+ years of total experience in consulting and/or industry
- Experience as a data platform architect, senior data engineer, or similar technical delivery leader
- Background leading delivery on industrial data, manufacturing analytics, operational technology (OT), or related data platform programs
- Ability to manage execution across multiple workstreams while maintaining focus on architecture quality and delivery outcomes
- Experience working with cloud data platforms and hyperscaler ecosystems, with exposure to Databricks and AWS preferred (maybe this is preferred, but we can still include as requirement? It says preferred; but we can put under Qualifications preferred.)
- Ability to travel 50%, on average, based on the work you do and the clients and industries/sectors you serve
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future
Qualifications (maybe preferred):
- Comfortable coordinating with platform solution architects or alliance teams for platform-specific design support
- Strong client communication skills, with the ability to explain technical topics clearly to both technical and business stakeholders
- Data integration patterns between OT source systems and cloud analytics platforms
- Experience designing or overseeing lakehouse schemas, time-series data mapping, cloud landing zone architecture, and data pipeline patterns
- Ability to review data engineering deliverables in enough technical depth to identify architectural issues, integration risks, and design gaps
But note some of these overlap with skills list.
Skills: list of abilities:
- 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 also include some of the preferred qualifications as skills but they are more specific.
We need to avoid duplication. The posting includes both a list of abilities (skills) and also some preferred qualifications that are similar. We'll keep them separate as per headings.
Now Benefits: mention discretionary annual incentive program.
Pay: wage range $155,600 to $306,800.
Schedule: travel 50% (already in Requirements as ability to travel). But we could also put travel under Schedule section. The instruction: include Schedule section only if posting actually states them. It does state travel 50%. So we can put travel under Schedule. However we also have travel as a requirement; we could keep it only under Schedule and not duplicate. But we need to preserve all substantive information; if we only put under Schedule, it's still preserved. So we can remove from Requirements.
Thus Requirements will not include travel.
Now we need to ensure we don't create sections with filler text. All sections have content.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine.
Now craft each content precisely, preserving original wording.
About the role paragraph: Let's copy exactly:
"Delivery Manager Deloitte's Sourcing and Procurement practice helps clients transform their Strategic Sourcing & Procurement functions into strategic partners for their businesses. We are differentiated by our executable mindset, focus, and strategy capabilities. We excel at strategies that are delivered through a combination of strong category experience, Sourcing and Procurement operating model expertise, broad-based knowledge and management skills, and geographical reach around the world. We advise companies on potential areas of savings relating direct Cost of Goods Sold (COGS) and enable digital transformation goals of Strategic Sourcing & Procurement functions through technology (e.g., Coupa, Ariba, etc.) assessments, selection, implementation, and continuous operations."
Note there is a missing space after "Delivery Manager"? It's "Delivery Manager Deloitte's". We'll keep as is.
Now Responsibilities items:
We need to break into list items preserving meaning.
Item1: "Lead core delivery execution for industrial data and analytics engagements, coordinating onshore and offshore teams while managing clear, client-facing delivery communications."
Item2: "Help translate technical work into practical delivery plans, keep execution moving across teams, and support alignment between client stakeholders, delivery teams, and platform partners."
Item3: "Own the design oversight of the data integration layer between operational technology (OT) sources and cloud analytics platforms, including lakehouse schemas, time-series mapping, cloud landing zone architecture, and pipeline patterns."
Item4: "This role requires enough hands-on data platform depth to review offshore data engineering output, identify architectural risks, and guide corrections."
Item5: "Early in engagements, you may coordinate with Databricks and AWS alliance solution architects for platform-specific design input."
We could also include the ideal background sentence? That seems more like qualification. We'll not include.
Now Requirements items:
- Bachelor's degree
- 8+ years of total experience in consulting and/or industry
- Experience as a data platform architect, senior data engineer, or similar technical delivery leader
- Background leading delivery on industrial data, manufacturing analytics, operational technology (OT), or related data platform programs
- Ability to manage execution across multiple workstreams while maintaining focus on architecture quality and delivery outcomes
- Experience working with cloud data platforms and hyperscaler ecosystems (exposure to Databricks and AWS preferred) – but since it's preferred, maybe we put under Qualifications. Let's keep it under Requirements? The posting says "Experience working with cloud data platforms and hyperscaler ecosystems, with exposure to Databricks and AWS preferred." It's a requirement but with preferred exposure. We'll keep as requirement but note preferred.
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future
We'll not include travel.
Now Qualifications (preferred) items:
- Comfortable coordinating with platform solution architects or alliance teams for platform-specific design support
- Strong client communication skills, with the ability to explain technical topics clearly to both technical and
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we should exclude the accommodation link and maybe the sentence about "Information for applicants with a need for accommodation". Also exclude any duplicated lines (none seen). Also exclude any generic filler like "commensurate with experience" etc. Not present. Now craft sections: 1. About the role (or About the practice). Use first paragraph. 2. Responsibilities: from "Work you'll do" paragraph(s). It includes multiple sentences; we can turn into list items. Let's extract responsibilities: - Lead core delivery execution for industrial data and analytics engagements, coordinating onshore and offshore teams while managing clear, client-facing delivery communications. - Help translate technical work into practical delivery plans, keep execution moving across teams, and support alignment between client stakeholders, delivery teams, and platform partners. - Own the design oversight of the data integration layer between operational technology (OT) sources and cloud analytics platforms, including lakehouse schemas, time-series mapping, cloud landing zone architecture, and pipeline patterns. - This role requires enough hands-on data platform depth to review offshore data engineering output, identify architectural risks, and guide corrections. - Early in engagements, you may coordinate with Databricks and AWS alliance solution architects for platform-specific design input. We could also include "Ideal background is a data platform architect or senior data engineer who has led delivery on industrial data or manufacturing analytics programs and moved into delivery leadership from a technical foundation." That's more of qualification/ideal background; maybe put under Qualifications or Requirements. But we already have Qualifications section. We'll keep responsibilities as above. 3. Requirements: maybe combine Qualifications and Skills? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need separate Requirements and Qualifications and Skills. We need to decide what goes where. Typically: - Requirements: mandatory items (experience, education, travel, work authorization). - Qualifications: maybe preferred qualifications? But they have "Required Experience" and "Preferred:" list. - Skills: list of abilities (Ability to work independently...). Thus: Requirements: - Bachelor's degree - 8+ years of total experience in consulting and/or industry - Experience as a data platform architect, senior data engineer, or similar technical delivery leader - Background leading delivery on industrial data, manufacturing analytics, operational technology (OT), or related data platform programs - Ability to manage execution across multiple workstreams while maintaining focus on architecture quality and delivery outcomes - Experience working with cloud data platforms and hyperscaler ecosystems, with exposure to Databricks and AWS preferred (maybe this is preferred, but we can still include as requirement? It says preferred; but we can put under Qualifications preferred.) - Ability to travel 50%, on average, based on the work you do and the clients and industries/sectors you serve - Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future Qualifications (maybe preferred): - Comfortable coordinating with platform solution architects or alliance teams for platform-specific design support - Strong client communication skills, with the ability to explain technical topics clearly to both technical and business stakeholders - Data integration patterns between OT source systems and cloud analytics platforms - Experience designing or overseeing lakehouse schemas, time-series data mapping, cloud landing zone architecture, and data pipeline patterns - Ability to review data engineering deliverables in enough technical depth to identify architectural issues, integration risks, and design gaps But note some of these overlap with skills list. Skills: list of abilities: - 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 also include some of the preferred qualifications as skills but they are more specific. We need to avoid duplication. The posting includes both a list of abilities (skills) and also some preferred qualifications that are similar. We'll keep them separate as per headings. Now Benefits: mention discretionary annual incentive program. Pay: wage range $155,600 to $306,800. Schedule: travel 50% (already in Requirements as ability to travel). But we could also put travel under Schedule section. The instruction: include Schedule section only if posting actually states them. It does state travel 50%. So we can put travel under Schedule. However we also have travel as a requirement; we could keep it only under Schedule and not duplicate. But we need to preserve all substantive information; if we only put under Schedule, it's still preserved. So we can remove from Requirements. Thus Requirements will not include travel. Now we need to ensure we don't create sections with filler text. All sections have content. Now produce HTML. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine. Now craft each content precisely, preserving original wording. About the role paragraph: Let's copy exactly: "Delivery Manager Deloitte's Sourcing and Procurement practice helps clients transform their Strategic Sourcing & Procurement functions into strategic partners for their businesses. We are differentiated by our executable mindset, focus, and strategy capabilities. We excel at strategies that are delivered through a combination of strong category experience, Sourcing and Procurement operating model expertise, broad-based knowledge and management skills, and geographical reach around the world. We advise companies on potential areas of savings relating direct Cost of Goods Sold (COGS) and enable digital transformation goals of Strategic Sourcing & Procurement functions through technology (e.g., Coupa, Ariba, etc.) assessments, selection, implementation, and continuous operations." Note there is a missing space after "Delivery Manager"? It's "Delivery Manager Deloitte's". We'll keep as is. Now Responsibilities items: We need to break into list items preserving meaning. Item1: "Lead core delivery execution for industrial data and analytics engagements, coordinating onshore and offshore teams while managing clear, client-facing delivery communications." Item2: "Help translate technical work into practical delivery plans, keep execution moving across teams, and support alignment between client stakeholders, delivery teams, and platform partners." Item3: "Own the design oversight of the data integration layer between operational technology (OT) sources and cloud analytics platforms, including lakehouse schemas, time-series mapping, cloud landing zone architecture, and pipeline patterns." Item4: "This role requires enough hands-on data platform depth to review offshore data engineering output, identify architectural risks, and guide corrections." Item5: "Early in engagements, you may coordinate with Databricks and AWS alliance solution architects for platform-specific design input." We could also include the ideal background sentence? That seems more like qualification. We'll not include. Now Requirements items: - Bachelor's degree - 8+ years of total experience in consulting and/or industry - Experience as a data platform architect, senior data engineer, or similar technical delivery leader - Background leading delivery on industrial data, manufacturing analytics, operational technology (OT), or related data platform programs - Ability to manage execution across multiple workstreams while maintaining focus on architecture quality and delivery outcomes - Experience working with cloud data platforms and hyperscaler ecosystems (exposure to Databricks and AWS preferred) – but since it's preferred, maybe we put under Qualifications. Let's keep it under Requirements? The posting says "Experience working with cloud data platforms and hyperscaler ecosystems, with exposure to Databricks and AWS preferred." It's a requirement but with preferred exposure. We'll keep as requirement but note preferred. - Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future We'll not include travel. Now Qualifications (preferred) items: - Comfortable coordinating with platform solution architects or alliance teams for platform-specific design support - Strong client communication skills, with the ability to explain technical topics clearly to both technical and