Supply Chain Integration Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description of role, responsibilities, what you'll do, what you bring (required, preferred). No explicit Benefits, Pay, Schedule. So we should not include those sections. We'll include About the role (maybe a brief intro), Responsibilities (What You'll Do), Requirements (Required), Qualifications (maybe Preferred?), Skills (maybe combine required/preferred skills). The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have: - Intro paragraph: "Supply Chain ERP/MES Integration Engineer Build the Digital Backbone Behind the Future of On-Demand Manufacturing ..." That's about the role. - "What You'll Do" list of responsibilities. - "What You Bring" includes Required and Preferred. We can map: About the role: intro paragraph(s) before responsibilities. Responsibilities: the bullet list under "What You'll Do". Requirements: the Required bullet list. Qualifications: maybe the Preferred bullet list (or we could treat Preferred as Qualifications). Skills: maybe combine both required and preferred skills? But we already have Requirements and Qualifications; Skills could be a summary of technical skills. However we must not create thin sections. If we include Skills, we need substantive content. We could put a combined list of skills from both required and preferred. But that might be redundant. Better to include only sections with distinct content: About the role, Responsibilities, Requirements, Qualifications (Preferred). That's four sections. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points exactly as given (or close). We must not add extra info not present. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus:

  About the role

  Supply Chain ERP/MES Integration Engineer Build the Digital Backbone Behind the Future of On-Demand Manufacturing What if a customer could upload a design, receive an automated quote, approve the order—and the entire manufacturing process could begin without a single person re-entering data? That's the system you're being hired to build. This position will create a highly automated, on-demand manufacturing platform designed to compress the traditional order-to-production cycle from weeks to days. We're looking for a Supply Chain ERP/MES Integration Engineer who can architect and own the digital thread connecting customer orders, quoting, inventory, suppliers, ERP, MES, and the factory floor. This isn't a role where you'll simply maintain integrations. You'll engineer the infrastructure that makes lights-out, data-driven manufacturing possible. As the Supply Chain ERP/MES Integration Engineer, you'll own the bidirectional, real-time flow of information between the systems that run the business and the systems that run the factory. When a customer approves an order, your architecture should make it possible for that decision to automatically trigger the next steps—from material availability and procurement through production scheduling, operator instructions, testing, and shipment documentation. You'll have the opportunity to influence both the technology architecture and the way manufacturing operates, working at the intersection of software engineering, supply chain, automation, and advanced manufacturing.

  But note we should not repeat the job title as heading; but we can include it in prose? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It's okay to have it in prose. However the intro includes the job title at start; we could keep it as part of prose. It's fine. Now Responsibilities: we need to capture the bullet points under "What You'll Do". There are several paragraphs each with multiple sentences. We should turn each bullet into
• . The original text: "Connect ERP, MES & Manufacturing Systems Design and implement bidirectional, real-time ERP/MES integrations. Create automated workflows where order entry triggers material reservation, production-queue creation, and downstream manufacturing activity. Build reliable APIs, middleware, data pipelines, and system interfaces that eliminate manual data entry. Establish robust data synchronization, validation, error handling, monitoring, and recovery processes. Automate Quoting & Supply Chain Decisions Integrate AI-powered quoting workflows with live ERP, supplier, and distributor databases. Enable automated BOM costing, material availability checks, pricing, and lead-time validation. Connect customer order information directly to manufacturing and supply-chain systems. Help create a scalable architecture that can support rapidly increasing transaction volumes. Build the Manufacturing Execution Architecture Design MES order-queue architecture and sequencing logic. Develop rules that prioritize work based on capacity, complexity, material availability, and production readiness. Connect production orders to equipment, operators, work instructions, and quality processes. Help establish the digital infrastructure required for highly automated manufacturing. Enable the Factory Floor Create digital workflows that automatically deliver the right work instructions and production information to operators. Enable material-allocation workflows that pull the correct components to production at the right time. Support barcode/RFID-based inventory and line-side replenishment. Integrate MES with manufacturing equipment and other shop-floor technologies where appropriate. Automate Procurement & Documentation Integrate supplier and distributor APIs to support automated purchase-order generation. Align procurement activity with demand forecasts, production requirements, and inventory levels. Develop automated replenishment triggers using barcode/RFID technologies. Automate generation of production and shipment documentation, including certifications and test reports." We can treat each bold heading as a subsection? But we only need
  • for list. We could make each line a list item. Or we could group under headings but we cannot add extra headings besides the specified ones. However we could still include

    ?? Not allowed; only specified headings. So we should just make a flat list of all responsibilities. That may lose some grouping but still preserve all info. That's acceptable. Thus

    with each sentence as
    • . Ensure we keep the exact wording. Now Requirements: Required bullet list: "Required Bachelor's degree in Computer Science, Information Systems, Industrial Engineering, Software Engineering, or a related field—or equivalent experience. 3+ years of experience integrating ERP and/or MES platforms. Experience working with APIs, EDI, SCADA, WMS, middleware, data pipelines, or similar integration technologies. Strong understanding of manufacturing data structures and workflows, including: Bills of Material (BOMs) Work orders Inventory Procurement Production scheduling Material allocation Manufacturing execution Strong software development and systems-integration capabilities. Ability to evaluate build-vs-buy decisions and select practical solutions that can scale." We need to turn each bullet into
    • . The sub-bullets under Strong understanding... we can treat each as separate
    • as well. Now Qualifications: Preferred bullet list: "Preferred Experience with Arcadia or eCAD environments. Experience integrating MES platforms with manufacturing equipment. Experience working with RFID, barcode, or automated inventory systems. Experience in a high-growth manufacturing, technology, or startup environment. Familiarity with digital work instructions and connected-factory concepts. Experience designing systems where multiple platforms must exchange data in real time." We'll put those as
    • . Now Skills: maybe we could combine required and preferred skills? But we already have Requirements and Qualifications; Skills could be redundant. Better to omit Skills section if no distinct content beyond those. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills. We also must not include Benefits, Pay, Schedule as they are not present. Thus final HTML fragment:

      About the role

      ... (the intro paragraph(s) )

      Responsibilities

      • Design and implement bidirectional, real-time ERP/MES integrations.
      • Create automated workflows where order entry triggers material reservation, production-queue creation, and downstream manufacturing activity.
      • Build reliable APIs, middleware, data pipelines, and system interfaces that eliminate manual data entry.
      • Establish robust data synchronization, validation, error handling, monitoring, and recovery processes.
      • Integrate AI-powered quoting workflows with live ERP, supplier, and distributor databases.
      • Enable automated BOM costing, material availability checks, pricing, and lead-time validation.
      • Connect customer order information directly to manufacturing and supply-chain systems.
      • Help create a scalable architecture that can support rapidly increasing transaction volumes.
      • Design MES order-queue architecture and sequencing logic.
      • Develop rules that prioritize work based on capacity, complexity, material availability, and production readiness.
      • Connect production orders to equipment, operators, work instructions, and quality processes.
      • Help establish the digital infrastructure required for highly automated manufacturing.
      • Create digital workflows that automatically deliver the right work instructions and production information to operators.
      • Enable material-allocation workflows that pull the correct components to production at the right time.
      • Support barcode/RFID-based inventory and line-side replenishment.
      • Integrate MES with manufacturing equipment and other shop-floor technologies where appropriate.
      • Integrate supplier and distributor APIs to support automated purchase-order generation.
      • Align procurement activity with demand forecasts, production requirements, and inventory levels.
      • Develop automated replenishment triggers using barcode/RFID technologies.
      • Automate generation of production and shipment documentation, including certifications and test reports.

      Requirements

      • Bachelor's degree in Computer Science, Information Systems, Industrial Engineering, Software Engineering, or a related field—or equivalent experience.
      • 3+ years of experience integrating ERP and/or MES platforms.
      • Experience working with APIs, EDI, SCADA, WMS, middleware, data pipelines, or similar integration technologies.
      • Strong understanding of manufacturing data structures and workflows, including:
      • Bills of Material (BOMs)
      • Work orders
      • Inventory
      • Procurement
      • Production scheduling
      • Material allocation
      • Manufacturing execution
      • Strong software development and systems-integration capabilities.
      • Ability to evaluate build-vs-buy decisions and select practical solutions that can scale.

      Qualifications

      • Experience with Arcadia or eCAD environments.
      • Experience integrating MES platforms with manufacturing equipment.
      • Experience working with RFID, barcode, or automated inventory systems.
      • Experience in a high-growth manufacturing, technology, or startup environment.
      • Familiarity with digital work instructions and connected-factory concepts.
      • Experience designing systems where multiple platforms must exchange data in real time.
      We need to ensure we didn't miss any substantive info: The intro also had "Supply Chain ERP/MES Integration Engineer Build the Digital Backbone Behind the Future of On-Demand Manufacturing What if a customer could upload a design, receive an automated quote, approve the order—and the entire manufacturing process could begin without a single person re-entering data? That's the system you're being hired to build. This position will create a highly automated, on-demand manufacturing platform designed to compress the traditional order-to-production cycle from weeks to days. We're looking for a Supply Chain ERP/MES Integration Engineer who can architect and own the digital thread connecting customer orders, quoting, inventory, suppliers, ERP, MES, and the factory floor. This isn't a role where you'll simply maintain integrations. You'll engineer the infrastructure that makes lights-out, data-driven manufacturing possible. As the Supply Chain ERP/MES Integration Engineer, you'll own the bidirectional, real-time flow of information between the systems that run the