ERP Technical Lead

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where there is real specific content. No placeholder like "commensurate with experience". The posting includes responsibilities, required qualifications, benefits, maybe skills (explicit list). Also maybe "About the role" can be derived from first paragraph. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions (like "To view all of our open positions go to: ..." and social media links). Also remove AI & Hiring Disclosure? That's likely boilerplate; we should remove it. Also remove "Additional Info" about company purpose maybe not boilerplate? It's about company culture; might be considered substantive? It's not required but could be considered "About the role"? Probably not needed. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine some. We need sections: About the role (maybe from first paragraph). Responsibilities (list). Requirements (maybe combine qualifications). Skills (maybe list of specific technologies). Benefits (list). Pay and Schedule not present, so omit. We must not repeat job title as heading. So no heading for ERP Technical Lead. We need to use

for each section heading. Use

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

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, etc. But we can combine similar items? Must not lose detail. So we need to include each bullet point as

• . Ensure we don't omit any. Let's extract responsibilities sections: From text: "Key Responsibilities Lead ERP technical activities for acquisition and enterprise integration/onboarding (due diligence through post Day One stabilization)." "Develop and execute ERP integration strategies aligned with business goals, integration timelines, and synergy objectives." "Assess acquired company systems, technical architecture, master data, interfaces, custom developments, and reporting capabilities." "Partner with Integration Program Management, Enterprise Architecture, Infrastructure, Cybersecurity, Data Management, and Business Process teams to ensure a coordinated integration approach." "Identify integration risks, dependencies, and technical constraints. Develop counter measures and mitigation plans." "ERP Technical Delivery Lead technical design, development, testing, and deployment activities related to ERP integration." "System migration, carve-ins, harmonization efforts, and legacy system retirements" "Ensure successful integration of acquired entities into Oracle ERP platforms, with particular emphasis on Oracle E-Business Suite and Oracle Cloud ERP environments." "Lead ERP migration activities involving SAP-to-Oracle conversions, including application rationalization, data migration, process harmonization, interface redesign, and legacy system decommissioning." "Establish and enforce technical standards, governance, and best practices within the scope of the integration program." "Coordinate ERP environment strategy, transport management, release planning, and cutover activities." "Data Migration & Integration Lead the assessment, design, and execution of SAP-to-Oracle data migration strategies, including data mapping, transformation, reconciliation, and validation across finance, supply chain, procurement, manufacturing, and customer domains." "Ensure successful integration of ERP with surrounding business applications, third-party systems, and enterprise platforms." "Lead data conversion and migration efforts, including master data, transactional data, and historical data requirements." "Oversee data cleansing, mapping, validation, reconciliation, and conversion activities." "Ensure successful integration of ERP with surrounding business applications, third-party systems, and enterprise platforms." (duplicate) "Oversee EDI integration architecture and implementation, including onboarding trading partners, mapping standards, transaction monitoring, exception management, and integration with ERP and middleware platforms." "Direct interface development, middleware integration, API strategies, and technical testing." "Technical Architecture & Solution Design Evaluate current-state and future-state architectures for acquired entities." "Define scalable integration solutions that minimize business disruption and technical risk." "Collaborate with enterprise architects to align solutions with corporate technology standards and roadmaps." "Drive decisions regarding system consolidation, harmonization, and technical debt reduction." "Project & Team Leadership Lead internal and external technical resources, including consultants, developers, integration specialists, and offshore teams." "Manage technical work plans, project milestones, resource allocation, and deliverables." "Provide regular status updates to program leadership, executive stakeholders, and steering committees." "Mentor technical team members and foster a culture of accountability, collaboration, and continuous improvement." "Quality, Compliance & Risk Management Ensure compliance with corporate governance, security requirements, and regulatory standards." "Lead system validation, testing, audit readiness, and controls compliance activities." "Establish technical risk management processes and proactively resolve critical issues." "Support business continuity planning, cutover readiness, and hyper-care activities." That's a lot. We need to preserve all. We'll put them as
• under Responsibilities. Now Required Qualifications: "Bachelor's degree in Computer Science, Information Systems, Engineering, or related field." "8+ years of ERP implementation, support, or integration experience." "5+ years of experience leading complex ERP technical teams and large-scale enterprise programs." "Demonstrated experience supporting mergers, acquisitions, divestitures, or enterprise integration initiatives." "Deep hands-on expertise in Oracle ERP platforms, including Oracle E-Business Suite and/or Oracle Cloud ERP, with demonstrated leadership of enterprise-scale implementations, integrations, and transformation programs." "Proven experience leading ERP migration initiatives from SAP ECC and/or SAP S/4HANA to Oracle ERP platforms, including application integration, data conversion, process harmonization, and organizational change management activities." "In-depth experience with: Data migration, conversion, and SAP-to-Oracle transformation programs System integration and middleware technologies EDI architecture, mapping, transaction processing, and trading partner integration APIs and interface development ERP security and controls Technical architecture and solution design Release and deployment management" "Proven ability to manage multiple priorities in a fast-paced global environment." "Strong expertise with EDI platforms and standards such as ANSI X12, EDIFACT, AS2, SPS Commerce, OpenText, IBM Sterling, MuleSoft, Boomi, or equivalent integration technologies." We can treat these as list items under Requirements (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills. We have both Required Qualifications and also maybe Skills (the list of expertise). We could combine Required Qualifications and Skills into one section "Requirements" or separate. But we need to avoid thin sections. Perhaps we make one section "Requirements" containing both qualifications and skills as list items. However we need to preserve all detail; we can still list them. But we also have "Success Measures" which could be considered maybe not needed; but it's substantive. Could be a section "Success Measures". However instruction says prefer few substantive sections over many thin ones. We could incorporate success measures into Responsibilities or a separate section? Might be thin but still substantive. Could be its own section but maybe we can include under Responsibilities? It's about outcomes. Might be better as its own section "Success Measures". But we need to decide. Also "Additional Info" about company purpose etc. Might be considered boilerplate? It's not standard legal boilerplate but it's company culture. Might be considered not essential to role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This "Additional Info" is not those; it's company description. Could be kept maybe under "About the role" or separate "About the company". But we have no heading for About the company; we could include under About the role? The role description already includes first paragraph. The additional info about purpose could be considered extra but not required. Might be okay to omit as it's not directly about role. However we must preserve ALL substantive information; does that include company description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. But we need to decide where to place it. Could be a section "About the company" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we could fold it into About the role (makes sense). So About the role section can include the initial description plus the company purpose paragraph. Now Benefits: list items. We need to output only HTML fragment, no /, no markdown. Let's craft:

  About the role

  The ERP Technical Lead will provide technical leadership for a large-scale acquisition integration program, to ensure the successful integration of the acquired business (Eaton Mobility Operations) into the enterprise ERP landscape per established Program Milestones. This role is responsible for leading ERP technical workstreams, overseeing system integration activities, managing technical resources, and partnering with business, functional, and IT stakeholders to deliver seamless integration of processes, data, applications, and infrastructure.

  At FastTek Global, Our Purpose is Our People and Our Planet . We come to work each day and are reminded we are helping people find their success stories . Also, Doing the right thing is our mantra . We act responsibly, give back to the communities we serve and have a little fun along the way. We have been doing this with pride, dedication and plain, old-fashioned hard work for 24 years ! FastTek Global is financially strong, privately held company that is 100% consultant and client focused . We've differentiated ourselves by being fast, flexible, creative and honest . Throw out everything you've heard, seen, or felt about every other IT Consulting company. We do unique things and we do them for Fortune 10, Fortune 500, and technology start-up companies.

  Then Responsibilities:

  Responsibilities

  • Lead ERP technical activities for acquisition and enterprise integration/onboarding (due diligence through post Day One stabilization).
  • Develop and execute ERP integration strategies aligned with business goals, integration timelines, and synergy objectives.
  • Assess acquired company systems, technical architecture, master data, interfaces, custom developments, and reporting capabilities.
  • Partner with Integration Program Management, Enterprise Architecture, Infrastructure, Cybersecurity, Data Management, and Business Process teams to ensure a coordinated integration approach.
  • Identify integration risks, dependencies, and technical constraints. Develop counter measures and mitigation plans.
  • Lead technical design, development, testing, and deployment activities related to ERP integration.
  • System migration, carve-ins, harmonization efforts, and legacy system retirements.
  • Ensure successful integration of acquired entities into Oracle ERP platforms, with particular emphasis on Oracle E-Business Suite and Oracle Cloud ERP environments.
  • Lead ERP migration activities involving SAP-to-Oracle conversions, including application rationalization, data migration, process harmonization, interface redesign, and legacy system decommissioning.
  • Establish and enforce technical standards, governance, and best practices within the scope of the integration program.
  • Coordinate ERP environment strategy, transport management, release planning, and cutover activities.
  • Lead the assessment, design, and execution of SAP-to-Oracle data migration strategies, including data mapping, transformation, reconciliation, and validation across finance, supply chain, procurement, manufacturing, and customer domains.
  • Ensure successful integration of ERP with surrounding business applications, third-party systems, and enterprise platforms.
  • Lead data conversion and migration efforts, including master data, transactional data, and historical data requirements.
  • Oversee data cleansing, mapping, validation, reconciliation, and conversion activities.
  • Oversee EDI integration architecture and implementation, including onboarding trading partners, mapping standards, transaction monitoring, exception management, and integration with ERP and middleware platforms.
  • Direct interface development, middleware integration, API strategies, and technical testing.
  • Evaluate current-state and future-state architectures for acquired entities.
  • Define scalable integration solutions that minimize business disruption and technical risk.