IDO Delivery Manager
Deloitte · New York, NY · 1 mo ago
HybridManufacturing$156k–$307k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The first paragraph: "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."
That's about the practice, not exactly role but could be "About the role". We'll include.
- Responsibilities: The paragraph starting "Work you'll do In this role, you will lead core delivery execution..." includes responsibilities. Also later bullet points? Actually there is a list of skills after "A successful candidate would possess these skills:" which is more skills. Responsibilities: leading delivery execution, coordinating teams, translating technical work, keeping execution moving, supporting alignment, owning design oversight of data integration layer, reviewing offshore data engineering output, identifying architectural risks, guiding corrections, early coordination with Databricks and AWS alliance solution architects.
We'll put those in
- .
- Requirements: The qualifications section includes required experience etc. Could be "Qualifications". But we have separate headings: Requirements and Qualifications. The posting has "Qualifications Required" and then list. Also "Preferred:" after that. So we can treat "Qualifications" as required qualifications, and maybe "Skills" as the list of skills. However we also have a "Skills" section: "A successful candidate would possess these skills:" list.
Thus:
- Skills: list of abilities (Ability to work independently..., etc.)
- Qualifications: Required Experience as a data platform architect..., etc. plus Preferred items.
- Pay: The wage range: "$155,600 to $306,800" plus mention of discretionary annual incentive program.
- Schedule: Travel 50% average.
- Benefits: Not explicitly mentioned besides maybe discretionary annual incentive program? That's compensation, not benefits. No explicit benefits like health, retirement. So we should not create Benefits section unless posting actually states them. It does not. So omit Benefits.
- Schedule: Travel 50% average.
- About the role: we have.
- Responsibilities: we have.
- Requirements: maybe we can combine with Qualifications? But we need to decide. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content exists. The posting has "Qualifications Required" and then list. That could be Qualifications. Requirements maybe not explicitly separate; but we could treat the required experience etc as Requirements. However the posting lumps them under Qualifications Required. To avoid duplication, we could put Requirements as the same as Qualifications? But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. If we don't have distinct Requirements separate from Qualifications, we could omit Requirements and just have Qualifications. However the heading list is just examples; we are not required to include all. So we can omit Requirements if no distinct content.
Thus sections: About the role, Responsibilities, Skills, Qualifications, Pay, Schedule.
Check if any other: maybe "Team" description: "The team We are a team of strategic advisors..." That could be part of About the role or maybe a separate section like "Team". Not in allowed headings, so we could incorporate into About the role.
Now we need to preserve all substantive information. Let's extract details.
About the role paragraph: we have that.
Responsibilities: list items:
- 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.
- Review offshore data engineering output, identify architectural risks, and guide corrections.
- Early in engagements, coordinate with Databricks and AWS alliance solution architects for platform-specific design input.
Also maybe "manage execution across multiple workstreams while maintaining focus on architecture quality and delivery outcomes" is more qualification.
Skills list:
- 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
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.
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.
Pay:
- Wage range: $155,600 to $306,800.
- May also be eligible to participate in a discretionary annual incentive program, subject to rules.
Schedule:
- Ability to travel 50%, on average.
We already have travel in qualifications; but schedule section can mention travel expectation.
We must not repeat content unnecessarily but preserve all. It's okay if some overlap but we should try to avoid duplication. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all info, even if repeated across sections? Ideally we should not duplicate but we can include each piece once. Travel appears both in qualifications and schedule; we can put travel in Schedule section and maybe not repeat in Qualifications. But Qualifications includes "Ability to travel 50%, on average, based on the work you do and the clients and industries/sectors you serve." That's substantive; we need to preserve it. If we put it only in Schedule, we still preserve it. So we can omit from Qualifications to avoid duplication. But we need to check if any other qualification details are unique.
Let's list qualifications without travel:
- 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 items as above.
Now Skills list as above.
Now Responsibilities list as above.
Now About the role paragraph.
Now Pay: wage range and discretionary annual incentive program.
Now Schedule: travel 50% average.
Now we need to output HTML fragment with appropriate headings
and content. Structure:
About the role
... paragraph ...
Responsibilities
- ... ...
Skills
- ... ...
Qualifications
- ... ...
Preferred?Preferred qualifications: then
- . That's okay.
Pay
... wage range ...
... discretionary annual incentive program ...
Schedule
Ability to travel 50%, on average, based on the work you do and the clients and industries/sectors you serve.
Make sure not to include any boilerplate like EEO, accommodation link, etc. We removed that. Check for any leftover boilerplate: The accommodation link at end should be removed. Also the sentence about "Information for applicants with a need for accommodation - https://..." remove. Also remove any mention of "The wage range for this role takes into account..." we can keep the substantive range and incentive program but maybe we can condense. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the explanation about wage range? That is substantive but maybe considered boilerplate? It's describing how range determined. Might be considered boilerplate but it's part of the posting. However it's not a specific detail like range; it's explanatory. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence? It's not a specific detail like range; it's explanatory. Might be considered boilerplate but it's part of the compensation description. The instruction also says: "Prefer a few substantive sections over many thin ones." It didn't say to strip explanatory sentences. I'd keep the range and incentive program; the explanatory sentence about factors can be omitted? It's not a specific detail like range; it's generic. Might be considered boilerplate. Safer to keep only the range and incentive program. However the instruction says preserve ALL substantive information; the explanatory sentence is substantive? It's about how range determined; could be considered boilerplate but still info. I'd keep it to be safe. Thus Pay section:The wage range for this role takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which the position may be filled. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and