Senior Systems Engineer, Build Configuration

We need to output HTML fragment with sections: About Us? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and produce sections: maybe "About Us", "Role Overview", "Key Responsibilities", "Compensation & Benefits", "About You: Basic Qualifications", "Preferred Qualifications", "Typical Education And Experience", "Relocation". However headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can use other headings if appropriate? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings where applicable. But we can also use other headings like "About Us" maybe not in list but still okay? The instruction says use

  for section headings (e.g. ...). It doesn't forbid other headings, but to be safe we should map content to those headings. We have sections: About Us (company description) could be "About the role"? Actually "About the role" is more about role overview. "About Us" could be considered "About the role"? Not exactly. But we could treat "About Us" as "About the role"? Might be okay. However they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can have headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to include sections only when posting has real specific content. Let's map: - About the role: Could include "Role Overview" and maybe "About Us"? The role overview includes description of role, reporting to Chief Engineer, etc. Also "About Us" is company description, not role. But we could put company description under "About the role"? Might be odd. However we could create a separate heading like "About Us" but not in list; maybe they'd accept. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, just gives examples. I'd lean to using those examples where appropriate, but we can also add others if needed. However to be safe, we could map: - About the role: combine "About Us" and "Role Overview"? Might be too much. Better: Use headings: "About the role" for role overview; "Responsibilities" for key responsibilities; "Requirements" for basic qualifications; "Qualifications" for preferred qualifications; "Skills" maybe not needed; "Benefits" for compensation & benefits; "Pay" for base salary; "Schedule" maybe not present (they mention full-time, 100% in-office, occasional travel). That could be schedule info. So we can include Schedule. We must not create sections with filler like "not specified". We have actual content for each. Thus produce:

  About the role

  ... role overview text ...

  Responsibilities

  • ... each responsibility ...

  Requirements

  • ... basic qualifications ...

  Qualifications

  • ... preferred qualifications ...

  Benefits

  • ... benefits list ...

  Pay

  Base salary: $111,000 - $135,000 plus equity

  Schedule

  This is a full-time, 100% in-office role based in St. Louis, MO. You'll work within a team of 3–10 engineers and engage in occasional domestic travel for integration, demonstrations, and customer interactions.

  We also need to include relocation info? Could be part of Benefits or maybe a separate paragraph under About the role? The instruction says include a section ONLY when posting has real, specific content. Relocation is mentioned: "This position offers a competitive relocation package for qualified candidates." That's specific. Could be included under Benefits or maybe a separate section like "Relocation". But not in list. Could fold into Benefits as a bullet. We'll add a bullet under Benefits: "Competitive relocation package". Also need to include "About Us" company description. Where to put? Could be under About the role as introductory paragraph before responsibilities. Or we could create a heading "About the company" but not in list. Might be okay to include as a paragraph under About the role. The instruction says "About the role" heading examples; we can put company description there as part of role overview. Let's include it in About the role paragraph. Thus About the role paragraph: combine company description and role overview. Now ensure we preserve all substantive information: need to include details like "Based in St. Louis, MO", "self-propelled battery-electric railcars", etc. Also mention "In 2027 this role is a full-time seat managing our customer vehicle builds. It also offers the opportunity to lead a small team doing this work in 2028 and beyond." That's part of role overview. Also mention "You'll work within a team of 3–10 engineers and engage in occasional domestic travel for integration, demonstrations, and customer interactions." Already in schedule. Also mention "Build Configuration Ownership: Define and run the process..." etc. Also mention "Module BOM Matching: ..." etc. Also mention "Order-to-Procurement Handoff: ..." etc. Also mention "Build Change Control: ..." etc. Also mention "Build Scheduling: ..." etc. Also mention "Process & Tooling Definition: ..." etc. Also mention "Technical Leadership: ..." etc. Also mention "Compensation & Benefits Base salary: $111,000 - $135,000 plus equity Intramotev offers a comprehensive benefits package for all team members, including: Medical coverage: We cover 100% of employee medical premiums, plus low-cost dental and vision options.Vacation: Full-time employees enjoy unlimited paid time off.Equity: Full-time employees receive equity in the company.Parental leave: New parents receive paid time off to spend quality time with their family." Also mention "About You: Basic Qualifications (Required Skills/Experience) At least a Bachelor's Degree in Engineering (any discipline).5 or more years of engineering experience. Not all of it needs to be in configuration or order engineering.Hands-on experience working with multi-level BOMs and engineering release and change processes for physical products.Experience working across engineering, sales, and procurement/supply chain to take a product from order to build, and comfort defining a repeatable process where none exists yet.Willingness to expand into technical areas beyond your area of expertise; ability to develop innovative and novel approaches.Open-minded and comfortable working in a teaming environment as a technical leader.Fluent in both written and verbal English.U.S. Person (immigration or work visa sponsorship will not be provided)." Also mention "Preferred Qualifications (Desired Skills/Experience) Candidate should have a working knowledge of one or (ideally) multiple areas listed below: Experience in custom engineering builds, job-shop, configure-to-order, or engineer-to-order manufacturing.Experience with modular product architecture, variant or option BOMs, or product configurators.Exposure to ERP and PLM/PDM systems as a user or process owner (e.g., Odoo, Autodesk Vault, SAP, Epicor, Windchill, Teamcenter, or similar). No specific tool is required.Experience with master or build scheduling across multiple concurrent customer builds.Experience in directly applicable industry or projects, such as Rail, heavy or specialty vehicles, Electric Vehicles, Heavy Machinery, or Aerospace/Defense.Experience leading or mentoring a small team." Also mention "Typical Education And Experience Education/experience typically acquired through advanced technical education (e.g. Bachelor and/or Master) and typically 5 or more years' related work experience, or an equivalent combination of technical education and experience." Also mention "Relocation This position offers a competitive relocation package for qualified candidates." Also mention "Equal Opportunity Employer ..." which is boilerplate to remove. Also mention "Closing If you're passionate about systems engineering and eager to lead the charge in autonomous rail technology, we'd love to hear from you!" That's application instruction/boilerplate to remove. Thus we need to exclude EEO, closing, etc. Now produce HTML. We need to ensure we use
  • for any list of duties/requirements/benefits. For responsibilities we have many items; we can make each bullet. For requirements (basic qualifications) we can list each bullet. For qualifications (preferred) we can list each bullet. For benefits we list each bullet. Now ensure we don't repeat job title as heading; we aren't. Now produce final HTML fragment. Let's craft paragraphs. About the role paragraph: "At Intramotev, we are dedicated to revolutionizing the freight industry by liberating tons of freight from congested highways, reducing carbon emissions, and enhancing transportation efficiency. We are deploying self-propelled battery-electric railcars and vehicles to transform freight logistics and bring innovation to our rail network. Based in St. Louis, MO, we are committed to promoting industrial revitalization, saving lives, and minimizing the environmental impact of trucking/transportation. We actively foster a work environment for every teammate that's welcoming, respectful and inclusive, with great opportunities for professional growth. We are seeking a Senior Systems Engineer, Build Configuration to join our systems engineering team, reporting to the Chief Engineer. We build self-propelled battery-electric railcars and vehicles for multiple customers, and every customer order becomes its own vehicle build. This role owns how each build gets finalized, configured, and matched to our library of module BOMs. It is the engineering link between a sales order and buying the parts to build that vehicle. If you have worked in configure-to-order (CTO), engineer-to-order (ETO), or order engineering, you will recognize the work. Here you will define the process, not inherit one. That includes shaping the tooling it runs on. In 2027 this role is a full-time seat managing our customer vehicle builds. It also offers the opportunity to lead a small team doing this work in 2028 and beyond." That's good. Now Responsibilities list: - Build Configuration Ownership: Define and run the