Senior Manufacturing Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: - Who We Are (maybe not needed as heading? Could be About the role? Actually "Who We Are" is about company, not role. Could be omitted? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings if present. We have: - About the role: The role description: "We are seeking an experienced Senior Manufacturing Engineer to help stand up our brand-new manufacturing facility in Martinsburg, West Virginia, and to help write the next chapter of our company's growth story. This is more than a job; it's a rare opportunity to build a factory from the ground up. As a founding member of our manufacturing engineering team, you'll own the design and implementation of process flows, tooling, and equipment that will bring our production line to life — working hands-on from concept through startup and steady-state production." - Responsibilities: The day-to-day sections: Process & Production Line Development, Factory Standup & Production Support, Cross-Functional Collaboration. Those are responsibilities. - Requirements/Qualifications/Skills: The "You should apply if you" list includes BS degree, 5-10 years experience, etc. Also "Nice to Have" list. - Benefits: "What We Offer" includes focus on outcomes, generous compensation and benefits package (insurance coverage, flexible PTO, paid holidays, remote/hybrid work). Also mention base salary determined by factors. So we have some benefits info. - Pay: Not specific numbers, just "base salary offered ... determined by a variety of factors". That's vague; we should not create Pay section unless posting actually states them. It says base salary will be determined by factors, not a specific range. That's not specific content; we should avoid Pay section. - Schedule: Not mentioned. Thus we include sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits. Possibly combine Requirements and Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have qualifications: BS degree, 5-10 years experience, etc. Also skills: designing custom tooling, fixtures, test stands, building process flows, procuring equipment, MES setup, project management, cross-functional collaboration, problem solving, communication, organizational skills, US citizenship required. We could have a "Requirements" section for mandatory qualifications, and a "Skills" section for desired skills/nice-to-have. Or combine. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, privacy, etc. We must preserve all substantive information. Let's extract content. About the role paragraph: as above. Responsibilities: bullet list? The text has headings: Process & Production Line Development, Factory Standup & Production Support, Cross-Functional Collaboration. Under each there are sentences. We can format as

• each responsibility item. Could break each sentence into li. Let's list: Process & Production Line Development: - Design, build, and continuously improve manufacturing process flows for new and existing product lines. - Develop and implement standard work stations, work instructions, and standardized processes to ensure repeatable, high-quality production. - Concept, plan, and design custom tooling, jigs, and fixtures to support efficient and ergonomic manufacturing operations. - Design and build custom test stands and fixtures to support product validation and end-of-line testing. - Lead the procurement of capital equipment, tooling, and fixtures, from specification and vendor selection through installation and qualification. Factory Standup & Production Support: - Manage the timeline and budget for manufacturing engineering workstreams as part of the broader factory standup effort. - Support the startup, ramp, and stabilization of production lines, including troubleshooting equipment, tooling, and process issues in real time. - Set up and configure MES (Manufacturing Execution System) processes and work instructions to support production tracking, traceability, and quality control. - Partner with Supply Chain to ensure tooling, equipment, and materials are procured and delivered on schedule to support production timelines. - Collaborate with Quality to build in process controls, inspection points, and validation steps that meet product and regulatory requirements. - Work closely with Production to ensure process designs translate into safe, efficient, and scalable operations on the floor. Cross-Functional Collaboration: - Serve as a key technical point of contact between Manufacturing Engineering, Supply Chain, Quality, and Production teams throughout the factory standup. - Support continuous improvement initiatives (Lean, Six Sigma, or similar methodologies) as the factory matures from startup to full-rate production. - Document processes, tooling designs, and lessons learned to build institutional knowledge as the site scales. Requirements (mandatory): - BS degree in Mechanical Engineering, Industrial Engineering, Manufacturing Engineering, or a related field - 5–10 years of experience in manufacturing engineering, ideally within aircraft or automotive production environments - Demonstrated experience designing custom tooling, fixtures, and test stands - Experience building manufacturing process flows and standard work stations from the ground up - Hands-on experience procuring manufacturing equipment and managing vendor relationships - Experience setting up MES systems from a process and work instruction perspective - Strong project management skills, with experience managing timelines and budgets in a fast-paced environment - Comfortable working cross-functionally with Supply Chain, Quality, and Production teams - Excellent problem-solving, communication, and organizational skills - U.S. citizenship required Skills/Nice to Have: - Prior experience in drone, UAS, or aerospace/defense manufacturing - Experience standing up a greenfield manufacturing facility - Lean Manufacturing, Six Sigma, or continuous improvement certifications - CAD proficiency (SolidWorks, CATIA, or similar) for tooling and fixture design - Familiarity with AS9100 or IATF 16949 quality systems Benefits: - A focus on outcomes, not time-tracking - A generous compensation and benefits package (in addition to base salary) that includes, but may not be limited to, insurance coverage (medical and travel), flexible paid time off, paid holidays, and remote and/or hybrid work available depending on position. - All compensation and benefits are subject to the terms and conditions of the underlying plans or programs, as applicable and as may be amended, terminated or superseded from time to time. - The base salary offered to the successful candidate will be determined by a variety of factors including relevant experience, qualifications, education, skill level, interview performance, and the level and scope of the position. We should not include Pay section because no specific numbers. Benefits section includes compensation info but it's okay. We must not include boilerplate like EEO, privacy, etc. Now produce HTML fragment: use

  for each section heading, then

  for prose,

  • for lists. We need to decide where to use

    vs

    . For About the role: a paragraph. For Responsibilities: we could have a

    intro then

    . But we can just do
    directly. The instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. So responsibilities are a list of duties -> use

      . Similarly requirements and skills are lists ->
      . Benefits also list ->
      . About the role is prose ->

      . We should not repeat the job title as heading. No extra. Let's craft. We'll have:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Skills

      • ...
      ...

      Benefits

      • ...
      ...
      Check that we didn't include Pay or Schedule. Make sure to preserve all substantive information: include US citizenship required, note about encouraging to apply even if not meet all qualifications? That's a note: "Note: We encourage you to apply even if you don’t meet all the listed qualifications; ability and impact cannot be summarized in a few bullet points." This is substantive? It's a note encouraging applicants. Should we preserve? It's not a requirement but it's part of posting. It's not boilerplate. Should we include? Probably yes, as it's substantive. Where to put? Could be under Requirements as a note, maybe as a

      after list. Or we could add a

      under Requirements. Since it's not a list, we can put a

      . Similarly "Nice to Have" we already captured as Skills. Also the sections "Who We Are" and the paragraphs about Helsing's work, mission, etc. Are those substantive? They describe company mission and work. Could be considered "About the company" but not requested headings. We could include as a

      under About the role? But About the role is specifically about the role. The "Who We Are" is about company. Could we add a section "About Helsing"? Not in allowed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings but better to stick to those. However we need to preserve all substantive information. The "Who We Are" and the later paragraphs about mission, work uniqueness, etc. Are substantive. Where to place? Could be included in About the role as a preamble? But About the role currently only has role description. We could expand About the role to include company mission? Might be okay. Alternatively we could add a

      before the headings with company description. Since no heading restriction, we can just put a

      with that content. 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 we should follow the pattern. Safer to include company description as a

      before the first heading. Thus output:

      Helsing develops artificial intelligence-enabled capabilities to protect and defend democracies. We are growing our US operations, cultivating an ambitious and committed team of mission-driven professionals to apply their skills to solve challenging problems.

      Then About the role heading. Then responsibilities etc. Also include the note about encouraging to apply even if you don't meet all qualifications as a

      under Requirements or after Requirements. Also include the paragraphs about Helsing's work being important, unique, etc. Could be added as a

      after Benefits maybe? Or as a separate section "About Helsing" but not in allowed headings. Could incorporate into Benefits? Not appropriate. Better to add a

      after Benefits with that content. Let's extract those paragraphs: "Join Helsing and work with world-leading experts in their fields Helsing’s work is important. You’ll be directly contributing to the protection of democratic countries while balancing both ethical and geopolitical concerns The work is unique. We operate in a domain that has highly unusual technical requirements and constraints, and where robustness, safety, and ethical considerations are vital. You will face unique Engineering and AI challenges that make a meaningful impact in the world Our work frequently takes us right up to the state of the art in technical innovation, be it reinforcement learning, distributed systems, generative AI, or deployment infrastructure. The defense industry is entering the most exciting phase of the technological development curve. Advances in our field of world are not incremental: Helsing is part of, and often leading, historic leaps forward In our domain, success is a matter of order-of-magnitude improvements