IDO Delivery Manager
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse posting.
We need to include sections only when posting has real specific content.
Let's extract:
- About the role: The first paragraph describing Deloitte's Sourcing and Procurement practice, etc. That's about the role? Could be "About the role". We'll include.
- Responsibilities: The "Work you'll do" paragraph describing duties: lead core delivery execution, coordinate teams, translate technical work, design oversight of data integration layer, etc. That's responsibilities.
- Requirements: Might be qualifications? There's "Qualifications" section later. We'll treat "Qualifications" as separate heading.
- Skills: The list of abilities after "A successful candidate would possess these skills:" includes bullet list.
- Benefits: Not mentioned explicitly. There's mention of discretionary annual incentive program, but not benefits like health etc. Probably not enough to create Benefits section.
- Pay: There's wage range $155,600 to $306,800. That's pay info. So include Pay section.
- Schedule: Travel 50% mentioned. That's schedule? Could be schedule (travel). Might include Schedule section.
- Also there is "The team" paragraph describing team. Could be part of About the role or separate? Not a standard heading; we could incorporate into About the role.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: accommodation link, EEO, etc. Remove the accommodation link line.
We must preserve all substantive information.
Let's craft sections:
About the role
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. The team is composed of strategic advisors, architects, and implementers who drive business transformations. Our diverse talent energizes clients' business functions and technology to maximize value in Supply Chain enhancing their ability to fulfill their growth and efficiency ambitions.
That captures about role and team.Responsibilities
In this role, you will lead core delivery execution for industrial data and analytics engagements, coordinating onshore and offshore teams while managing clear, client-facing delivery communications. You will help translate technical work into practical delivery plans, keep execution moving across teams, and support alignment between client stakeholders, delivery teams, and platform partners. You will 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.
Qualifications
Required 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. Technical leadership background; this role is intended for someone who moved into delivery leadership from data architecture or engineering, rather than a project manager without deep data platform experience. 8+ years of total experience in consulting and/or industry. Bachelor's degree. Experience coordinating/leading work across onshore and offshore delivery teams. 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.
But travel 50% maybe schedule; we could move to Schedule section. However qualifications includes travel; but we can keep it there or separate. The instruction: prefer few substantive sections over many thin ones. Travel could be part of Qualifications or Schedule. Since we already have Schedule maybe separate. Let's keep travel in Schedule. Thus Qualifications without travel.Skills
- 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
Pay
The wage range for this role is $155,600 to $306,800. You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance.
Schedule
Ability to travel 50%, on average, based on the work you do and the clients and industries/sectors you serve.
Check for any other content: Preferred qualifications list includes many items like comfort coordinating with platform solution architects, strong client communication skills, data integration patterns, experience designing lakehouse schemas, etc. Those are essentially skills/qualifications. We could incorporate them into Qualifications or Skills. Since we already have Skills list, we could add those as additional bullet points under Skills. But we must not invent content; we need to preserve all substantive information. The preferred qualifications include: - 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. These are substantive; we should include them. They could go under Skills or Qualifications. Since they are more like preferred qualifications, we could add them to Qualifications section as a list. But we already have Qualifications as a paragraph; we could convert to list for clarity. However we must not change meaning drastically; but we can use- for list of duties/requirements/benefits. The instruction: Use
- for any list of duties/requirements/benefits. So we should list requirements/qualifications as list. Similarly skills as list.
Thus better to restructure Qualifications as list.
Let's extract all qualifications (required and preferred) into a list under Qualifications.
Required:
- 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.
- Technical leadership background; this role is intended for someone who moved into delivery leadership from data architecture or engineering, rather than a project manager without deep data platform experience.
- 8+ years of total experience in consulting and/or industry.
- Bachelor's degree.
- Experience coordinating/leading work across onshore and offshore delivery teams.
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future.
Preferred (we can include as part of Qualifications list, maybe note "Preferred:" but we can just list them; they are still qualifications.
- 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.
We could also include travel 50% as Schedule.
Now Skills list we already have.
Now Responsibilities list maybe as list? The responsibilities are described in paragraph; we could keep as paragraph or list. The instruction: Use
- for any list of duties/requirements/benefits. Responsibilities are duties, so we should list them.
Let's extract responsibilities as bullet points:
- 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.
- 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.
- Review offshore data engineering output to identify architectural risks and guide corrections (requires hands-on data platform depth).
- Early in engagements, coordinate with Databricks and AWS alliance solution architects for platform-specific design input.
We'll put those as
- .
Now About the role: we can keep as paragraph.
Now Pay: we have paragraph.
Now Schedule: travel 50% as paragraph.
Now ensure we don't include boilerplate: accommodation link, etc.
Now produce HTML fragment.
Let's craft:
About the role
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. The team is composed of strategic advisors, architects, and implementers who drive business transformations. Our diverse talent energizes clients' business functions and technology to maximize value in Supply Chain enhancing their ability to fulfill their growth and efficiency ambitions.
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.
- 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.
- Review offshore data engineering output to identify architectural risks and guide corrections, requiring hands‑on data platform depth.
- Early in engagements, coordinate with Databricks and AWS alliance solution architects for platform‑specific design input.
Qualifications
- .
Now About the role: we can keep as paragraph.
Now Pay: we have paragraph.
Now Schedule: travel 50% as paragraph.
Now ensure we don't include boilerplate: accommodation link, etc.
Now produce HTML fragment.
Let's craft:
- for any list of duties/requirements/benefits. Responsibilities are duties, so we should list them.
Let's extract responsibilities as bullet points:
- 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.
- 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.
- Review offshore data engineering output to identify architectural risks and guide corrections (requires hands-on data platform depth).
- Early in engagements, coordinate with Databricks and AWS alliance solution architects for platform-specific design input.
We'll put those as
- for any list of duties/requirements/benefits. So we should list requirements/qualifications as list. Similarly skills as list.
Thus better to restructure Qualifications as list.
Let's extract all qualifications (required and preferred) into a list under Qualifications.
Required:
- 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.
- Technical leadership background; this role is intended for someone who moved into delivery leadership from data architecture or engineering, rather than a project manager without deep data platform experience.
- 8+ years of total experience in consulting and/or industry.
- Bachelor's degree.
- Experience coordinating/leading work across onshore and offshore delivery teams.
- Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future.
Preferred (we can include as part of Qualifications list, maybe note "Preferred:" but we can just list them; they are still qualifications.
- 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.
We could also include travel 50% as Schedule.
Now Skills list we already have.
Now Responsibilities list maybe as list? The responsibilities are described in paragraph; we could keep as paragraph or list. The instruction: Use