Jobs · Management · South Carolina

Integration & Process Improvement Engineer

Vertiv · Anderson, SC · 3 wk ago
ManagementFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes Position Summary, Responsibilities, Qualifications, maybe About Us, Work Authorization, Equal Opportunity Employer (but we must remove EEO boilerplate). Also maybe "Physical & Environmental Demands", "Travel Required". Those are specific content, so we can include sections like "Physical & Environmental Demands" and "Travel Required". However we must not include sections with filler like "commensurate with experience". Not present. We must not repeat job title as heading. The page already shows it, so we omit. We must not put Job ID/requisition numbers as headings. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we drop "Work Authorization", "Equal Opportunity Employer", maybe "About Us" is okay? It's substantive about company. Keep "About Us". Also "About Vertiv" maybe part of About Us. We'll keep a section "About the Company" maybe but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect only those headings. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only use those headings if content matches. The posting has sections like "Position Summary" (maybe About the role), "Responsibilities", "Qualifications". There's also "About Us" which is not in the list but could be considered "About the role"? Not exactly. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are examples. Probably we should stick to those headings where applicable. For "About Us" we could treat as "About the role"? Not ideal. Maybe we can omit About Us because it's not required? But we must preserve ALL substantive information; we cannot drop About Us if it's substantive. However we could incorporate About Us content into a

without a heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but suggests using those for sections. Safer to create headings matching content: we could use "About the role" for Position Summary, "Responsibilities" for Responsibilities, "Qualifications" for Qualifications, "Skills" maybe for preferred skills? Could combine. "Benefits", "Pay", "Schedule" we don't have specifics (Travel Required is schedule-ish but not pay/benefits). Travel Required could go under Schedule? Not exactly. But we could create a "Schedule" section for travel required? Might be okay. However instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Travel Required is not schedule but maybe we could put under "Schedule"? Not sure. Better to avoid creating Schedule if not explicit schedule like work hours. Travel Required is not schedule. Could put under a generic heading like "Additional Information". But not in list. Might be okay to add a heading like "Travel Required". The instruction didn't forbid other headings, just gave examples. So we can add headings for Travel Required, Physical & Environmental Demands, About Us. Thus produce HTML with sections:

About the role

(position summary),

Responsibilities

,

Qualifications

,

Skills

(maybe preferred),

Physical & Environmental Demands

,

Travel Required

,

About the Company

(or About Us). Ensure we preserve all substantive info. We need to use
  • for any list of duties/requirements/benefits. So within Responsibilities we have many bullet-like sentences; we should convert each responsibility into
  • . Similarly Qualifications: required and preferred lists. We must not invent or summarize away detail. Keep all details. Let's extract content. Position Summary paragraph: "We are seeking an Integration and Process Improvement Engineer to join our Engineering organization in Anderson, SC. This role serves as the primary liaison between Engineering, IT, Operations, Manufacturing, and Quality to support Oracle ERP/PLM integration initiatives while driving continuous improvement across the Engineering Line of Business. The Integration and Process Improvement Engineer will lead and support the migration and optimization of engineering processes within Oracle and related business systems, ensuring alignment between engineering workflows, BOM management, engineering change processes, and manufacturing execution. This position is responsible for establishing standardized engineering processes, governing engineering change management activities, improving data integrity, and identifying opportunities for workflow automation and operational excellence. The ideal candidate possesses a strong combination of engineering operations experience, ERP/PLM system knowledge, process improvement expertise, and change management capabilities. This role is ideal for a self-driven professional who enjoys solving complex business challenges through process optimization, digital transformation, and cross-functional collaboration." We'll put that as

    under About the role. Responsibilities: There are subheadings: Oracle Integration & Digital Transformation, Engineering Process Governance & Optimization, Engineering Change Management, Cross-Functional Collaboration & Knowledge Management. Each has bullet-like sentences. We'll create a single

      with
    • for each sentence (or maybe keep subheadings as

      ? Not allowed? Could use

      but instruction only mentions h3 for section headings. Could still use

      inside? Might be okay but safer to just list items. We need to preserve all detail; we can keep subheadings as maybe. But not required. We'll produce list items. Qualifications: Required and Preferred. We'll create two lists maybe under Qualifications heading, with subheadings

      Required and Preferred. Or we can just list all items with indication. Physical & Environmental Demands: "None." That's specific content; we should include it. Not filler. So we can have a

      None.

      under that heading. Travel Required: "Up to 25% travel may be required, including occasional domestic and international travel to support Oracle deployment, training, and continuous improvement initiatives." We'll put as

      . About Us: The paragraph about Vertiv's Core Principles & Behaviors, Strategic Priorities, etc. Also About Vertiv paragraph. We'll combine. We must remove EEO boilerplate, Work Authorization, etc. Let's craft. HTML fragment:

      About the role

      We are seeking an Integration and Process Improvement Engineer to join our Engineering organization in Anderson, SC. This role serves as the primary liaison between Engineering, IT, Operations, Manufacturing, and Quality to support Oracle ERP/PLM integration initiatives while driving continuous improvement across the Engineering Line of Business. The Integration and Process Improvement Engineer will lead and support the migration and optimization of engineering processes within Oracle and related business systems, ensuring alignment between engineering workflows, BOM management, engineering change processes, and manufacturing execution. This position is responsible for establishing standardized engineering processes, governing engineering change management activities, improving data integrity, and identifying opportunities for workflow automation and operational excellence. The ideal candidate possesses a strong combination of engineering operations experience, ERP/PLM system knowledge, process improvement expertise, and change management capabilities. This role is ideal for a self-driven professional who enjoys solving complex business challenges through process optimization, digital transformation, and cross-functional collaboration.

      Responsibilities

      • Oracle Integration & Digital Transformation: Lead and support Engineering participation in Oracle ERP and Oracle PLM deployment, migration, and optimization initiatives.
      • Collaborate with IT, Engineering, Operations, Manufacturing, Supply Chain, and Quality teams to integrate Oracle with engineering tools, CAD/PDM systems, manufacturing systems, and other business applications.
      • Develop and maintain data mapping, workflows, process configurations, and system integrations to support business requirements.
      • Ensure accurate migration and synchronization of BOMs, part master data, engineering specifications, and revision-controlled documentation.
      • Troubleshoot and resolve issues between Oracle and engineering, manufacturing, and reporting systems.
      • Support the development of dashboards, reports, and business intelligence tools that provide visibility into engineering performance and data quality.
      • Monitor system performance and identify opportunities to improve usability, efficiency, automation, and data integrity.
      • Develop user documentation, work instructions, and training materials for Oracle-related engineering processes.
      • Partner with global Oracle deployment teams to align local engineering requirements with enterprise standards.
      • Engineering Process Governance & Optimization: Own, develop, and maintain engineering process documentation, including SOPs, work instructions, process maps, governance standards, and RACI matrices.
      • Design and optimize engineering workflows from project intake through design release and production handoff.
      • Establish and manage engineering service level agreements (SLAs) and process performance metrics.
      • Conduct process audits to identify bottlenecks, waste, inefficiencies, and compliance gaps.
      • Analyze engineering and manufacturing data to identify root causes of rework, delays, and process variation.
      • Develop KPI dashboards and regularly communicate performance metrics to Engineering leadership.
      • Lead continuous improvement initiatives utilizing Lean Manufacturing, Six Sigma, Value Stream Mapping, and other structured problem-solving methodologies.
      • Drive workflow automation opportunities through digital tools, Oracle capabilities, and process standardization.
      • Benchmark engineering processes against industry best practices and recommend improvements that improve quality, cost, delivery, and productivity.
      • Engineering Change Management Governance: Govern the Engineering Change Request (ECR), Engineering Change Order (ECO), and Engineering Change Notice (ECN) lifecycle.
      • Ensure engineering changes are accurately implemented and fully traceable across Oracle ERP, Oracle PLM, CAD, and related business systems.
      • Conduct engineering impact assessments evaluating effects on BOMs, drawings, models, certifications, tooling, inventory, and production processes.
      • Monitor engineering change metrics including backlog, cycle time, implementation effectiveness, and closure performance.
      • Maintain revision control standards, audit trails, and engineering documentation compliance.
      • Develop and enforce change management procedures, templates, and governance standards.
      • Train engineering personnel on change management processes and documentation requirements.
      • Cross-Functional Collaboration & Knowledge Management: Drive alignment between Engineering, Project Management, Manufacturing, Purchasing, Operations, Quality, and IT teams.
      • Facilitate adoption of standardized engineering processes, systems, and best practices.
      • Support onboarding and training of engineering personnel through development of documented procedures and training resources.
      • Collaborate with continuous improvement teams, offshore engineering resources, and digital transformation initiatives.
      • Assist leadership in identifying strategic opportunities to improve engineering scalability, efficiency, and data quality.
      • Promote a culture of continuous improvement, accountability, and operational excellence throughout the Engineering organization.

      Qualifications

      Required

      • Bachelor’s degree in engineering, Industrial Engineering, Manufacturing Engineering, Mechanical Engineering, Information Systems, or a related technical field.
      • 3+ years of experience in engineering operations, process engineering, manufacturing engineering, systems integration, or related disciplines.
      • Experience with Oracle ERP and/or Oracle PLM systems.
      • Experience supporting ERP, PLM, CAD, or business system integrations.
      • Knowledge of BOM management, revision control, and engineering change management processes.
      • Experience developing process documentation, SOPs, workflows, and governance standards.
      • Strong

Similar jobs