IT Manufacturing Service Delivery Manager

We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about Capgemini Engineering. Then "Job Description:" then "Your Role:" with subsections. Then "Your Skills and Experience:" then compensation and benefits. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not include Job ID etc. We must include sections only when posting has real specific content. So we need to decide which sections to include: About the role (intro), Responsibilities (the detailed duties), Requirements (skills/experience), Benefits (benefits described), Pay (compensation range). Possibly Schedule? Not present. So we omit Schedule. We need to preserve all substantive info, not invent. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must remove boilerplate: cookie/navigation/legal/EEO etc. Remove disclaimer about compensation, equal opportunity, etc. Also remove "Important Notice", "Disclaimers", "Click the following link", etc. Also remove "Capgemini is a global business..." at end (boilerplate). Also remove "Location: Cincinnati OH / Hybrid / Remote" maybe we can include as a short

  maybe? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So location is minor metadata; we can include in a short

  . Probably include a

  with location and work mode. We need to preserve all substantive info: responsibilities list, skills/experience, benefits, pay range. We must not include filler like "commensurate with experience". Not present. We need to ensure we don't create sections with no content. Thus sections: - About the role (intro paragraph) - Responsibilities (list of duties) - Requirements (skills and experience) - Benefits (benefits description) - Pay (compensation range) We could also have a short

  for location. We must not repeat job title as heading. Let's extract content. Intro: "At Capgemini Engineering, the world leader in engineering services, we bring together a global team of engineers, scientists, and architects to help the world’s most innovative companies unleash their potential. From autonomous cars to life-saving robots, our digital and software technology experts think outside the box as they provide unique R&D and engineering services across all industries. Join us for a career full of opportunities. Where you can make a difference. Where no two days are the same." We can put that in

  . Location: "Location: Cincinnati OH / Hybrid / Remote". We'll put in a

  . Then responsibilities: Under "Your Role:" there are many bullet-like paragraphs. We need to turn them into

  • . The content includes many sentences; we can break each bullet as separate
  • . The headings inside like "Service Delivery Management", "Application Support & Operations", etc. Could treat each as a heading? But we only allowed

    for section headings; we could keep them as inside

    or just keep as prose. Probably better to keep as

    with the heading bold. We need to preserve all substantive info; we can keep the headings as part of the

    text. Thus create

    with each major duty as
    • . Let's list them: - Service Delivery Management: Own end-to-end service delivery for Manufacturing IT applications, including MES, LIMS, Veeva, and integration platforms; Ensure stable application operations across multiple plants, labs, and business units globally; Govern service performance against SLAs, OLAs, KPIs, and contractual commitments; Drive high-quality support for incidents, service requests, problem management, and minor enhancements - Application Support & Operations: Oversee L2/L3 application support for manufacturing and quality systems; Ensure timely triage, prioritization, escalation, and resolution of critical incidents; Establish structured processes for incident, problem, change, and knowledge management; Lead root cause analysis (RCA) reviews and track corrective and preventive actions (CAPA); Ensure production support readiness during plant operating windows, releases, and critical business cycles - Platform Oversight: Manage service delivery across platforms such as MES, LIMS, Integrations - Business Relationship & Stakeholder Management: Serve as the primary IT service delivery contact for plant operations, quality, laboratories, manufacturing, and business stakeholders; Partner with global and site teams to prioritize support needs, enhancement demand, and operational risks; Communicate service performance, service risks, outages, and improvement plans to leadership; Coordinate across cross-functional teams including infrastructure, cybersecurity, vendor teams, product owners, and site IT - Vendor & Partner Management: Manage third-party support vendors, system integrators, and strategic application partners; Ensure vendor accountability for SLA adherence, issue resolution, service quality, and documentation; Review contract deliverables, support coverage, and service performance metrics; Drive governance cadence with offshore, nearshore, and on-site support teams - Change, Release & Transition Management: Oversee application changes, release planning, deployment coordination, and production readiness; Ensure proper impact assessment, testing, validation, rollback planning, and business communication; Support onboarding of new plants, acquisitions, and service transitions into steady-state operations; Lead transition-to-support for new implementations, upgrades, and enhancement releases - Compliance, Quality & Risk Management: Ensure application services operate in compliance with internal quality standards and regulated environment requirements; Support audit readiness, validation support, documentation quality, and change control requirements; Work closely with Quality, Compliance, and CSV/validation teams where applicable; Monitor operational, security, and compliance risks and develop mitigation plans - Continuous Improvement & Service Excellence: Drive standardization, automation, and optimization of support processes across sites and platforms; Identify recurring issues, technical debt, and process inefficiencies, and lead improvement initiatives; Promote knowledge management through SOPs, KB articles, runbooks, and support documentation; Build a metrics-driven service culture focused on service reliability, user experience, and business value - Leadership & Team Management: Lead global support teams, application analysts, and technical specialists across multiple time zones; Define team objectives, priorities, operating model, and performance expectations; Coach team members and build functional capabilities across manufacturing and quality IT domains; Foster a collaborative, accountable, and customer-focused support culture We could split each bullet into separate
    • for each sentence, but the instruction: "Use
      • for any list of duties/requirements/benefits". It doesn't require each sentence separate; we can keep each major heading as a list item with sub-detail separated by semicolons. That's fine. Now Requirements: "Your Skills and Experience:" list: - Bachelor’s degree in Information Technology, Computer Science, Engineering, Life Sciences, or related discipline - 10+ years of experience in IT application support, service delivery, or operations management - 5+ years of experience supporting manufacturing, laboratory, or quality applications in global environments - Proven experience managing support for platforms such as MES, LIMS, Veeva, or similar regulated enterprise applications - Experience working in multi-site / multi-region manufacturing operations - Strong understanding of Manufacturing IT application landscapes, including MES platforms, LIMS applications, Veeva or similar platforms - Working knowledge of: - ERP integration (e.g., SAP) - API/interface support - Data flows between manufacturing, quality, and enterprise systems We can put each as
      • . For the sub-bullets under Working knowledge, we could nest
        inside
        • or just list as separate items. Simpler: treat each as separate
        • and include the sub-items as separate
        • with indentation? Probably fine to list them as separate
        • with dash. We'll produce:
          • Bachelor’s degree in Information Technology, Computer Science, Engineering, Life Sciences, or related discipline
          • 10+ years of experience in IT application support, service delivery, or operations management
          • 5+ years of experience supporting manufacturing, laboratory, or quality applications in global environments
          • Proven experience managing support for platforms such as MES, LIMS, Veeva, or similar regulated enterprise applications
          • Experience working in multi-site / multi-region manufacturing operations
          • Strong understanding of Manufacturing IT application landscapes, including MES platforms, LIMS applications, Veeva or similar platforms
          • Working knowledge of ERP integration (e.g., SAP)
          • Working knowledge of API/interface support
          • Working knowledge of Data flows between manufacturing, quality, and enterprise systems
          Now Benefits: The paragraph about benefits: "Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include: Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave Medical, dental, and vision coverage (or provincial healthcare coordination in Canada) Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada) Life and disability insurance Employee assistance programs Other benefits as provided by local policy and eligibility" We can turn each benefit into
        • . Also first sentence as

          maybe. We'll produce a

          for the intro sentence, then

          • for each benefit. Benefits list: - Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade - Company paid holidays - Personal Days - Sick Leave - Medical, dental, and vision coverage (or provincial healthcare coordination in Canada) - Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada) - Life and disability insurance - Employee assistance programs - Other benefits as provided by local policy and eligibility Now Pay: The compensation range paragraph: "The base compensation range for this role in the posted location is $73,000 - $174,000/year. Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws. The base compensation range listed for this position reflects the minimum and maximum target compensation Capgemini, in good faith, believes it may pay for the role at the time of this posting. This range may be subject to change as permitted by law. The actual compensation offered to any candidate may fall outside of the posted range and will be determined based on multiple factors legally permitted in the applicable jurisdiction. These may include, but are not limited to: Geographic location, Education and qualifications, Certifications and licenses, Relevant experience and skills, Seniority and performance, Market and business consideration, Internal pay equity. It is not typical for candidates to be hired at or near the top of the posted compensation range. In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws." We need to include Pay section only if posting has real specific content. It does have a range. We should include the range and maybe mention that additional compensation possible. However we must not include boilerplate like "Capgemini provides compensation range information..." etc? That is still substantive? It's more explanation but could be considered boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is not exactly legal but it's about compensation disclosure. Might be considered boilerplate but it's part of the posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the range and maybe the note about additional compensation. The rest is explanatory but still part of the posting. However it's somewhat generic; but we can keep it as it's part of the compensation description. To be safe, we can include