Supply Chain and Procurement Manager
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove application instructions. The posting includes sections: Who We Are, The role, The day-to-day (list of duties), You should apply if you (requirements), Nice to Have, Join Helsing and work with world-leading experts..., What We Offer (benefits). Also there is mention of base salary determination but not specific numbers, so we should not create Pay section unless actual salary stated. There's no explicit salary figure, so we omit Pay. Schedule? Not mentioned. Benefits: "What We Offer" includes compensation and benefits package, insurance coverage, flexible PTO, paid holidays, remote/hybrid work. So we can create Benefits section with that content.
We need sections: About the role? Could be "About the role" maybe from "The role" paragraph. Could also have "Who We Are" as a section? Not in list but we could treat as "About the company"? 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 suggests using those. Probably we should map content to those headings.
We have:
- About the role: description of role (first paragraph after "The role").
- Responsibilities: day-to-day duties list.
- Requirements: "You should apply if you ..." bullet list.
- Qualifications: maybe "Nice to Have" could be Qualifications? Or we could treat "Nice to Have" as Skills? Actually Skills could be technical skills. But we have "Nice to Have" list. Could be "Qualifications" for required, and "Skills" for nice-to-have? Or we could combine.
Better: Use "Requirements" for mandatory qualifications. Use "Skills" for nice-to-have. Use "Qualifications" maybe for education/clearance? But we have education and clearance in requirements. Could put those in Requirements.
We'll create sections:
About the role
with paragraph(s) describing role.
Responsibilities
with - each duty from day-to-day.
Requirements
with - each bullet from "You should apply if you".
Skills
with - each bullet from "Nice to Have".
Benefits
with - from "What We Offer": insurance coverage (medical and travel), flexible paid time off, paid holidays, remote and/or hybrid work available depending on position. Also "focus on outcomes, not time-tracking" maybe a benefit? It's more culture. Could include as bullet.
We must not include boilerplate like EEO, legal, privacy, etc. Also remove "Join Helsing and work with world-leading experts..." paragraphs (that's more about culture). Could be omitted as not fitting sections? Might be considered part of About the role? But it's more about company culture. Could be omitted as not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info. Where to place? Could be part of "About the role" or maybe a separate section like "About Helsing". But headings list didn't include that. However we could still include a heading like "About Helsing" but instruction says use headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; but we could also add other headings if needed? Safer to stick to those headings and fit content accordingly.
We could incorporate the "Join Helsing..." paragraphs into About the role or Benefits? Probably About the role includes description of role and company mission. The "Who We Are" paragraph at start: "Helsing develops artificial intelligence-enabled capabilities to protect and defend democracies..." That's about company. Could be part of About the role.
Thus About the role section can contain multiple paragraphs: Who we are, The role description, Join Helsing... etc.
We must not include legal/EEO etc.
Now craft HTML.
We need to ensure no markdown fences, just raw HTML.
Let's draft:
About the role
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.
This is Helsing's first supply chain hire in the United States. You will set up how we buy — and then do the buying yourself. Expect to spend your first year as a player-coach: designing the supplier strategy, the sourcing playbook and the compliance posture in the morning, and placing purchase orders, chasing commit dates and clearing the shortage list in the afternoon. We are deliberately not hiring a pure strategist or a pure buyer. The person who succeeds here can hold both altitudes: they know what "right" looks like for a defense supply chain — NDAA, ITAR/EAR, DFARS flow-downs, counterfeit-part avoidance — and they are equally comfortable on the phone with a distributor at 7pm to pull a lead time in by three weeks. You will work daily with Production, Systems Engineering and our Head of Logistics, and you will be the single point of accountability for whether material is where it needs to be. There is no team reporting to you on day one. There is a clear path to building one.
You will work daily with Production, Systems Engineering and our Head of Logistics, and you will be the single point of accountability for whether material is where it needs to be. There is no team reporting to you on day one. There is a clear path to building one.
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 and novel capabilities. This means we take bets, aim high, and focus on big opportunities. Despite being a relatively young company, Helsing has already been selected for multiple significant government contracts. We actively encourage healthy, proactive, and diverse debate internally about what we do and how we choose to do it. Teams and individual engineers are trusted (and encouraged) to practice responsible autonomy and critical thinking, and to focus on outcomes, not conformity. At Helsing you will have a say in how we (and you!) work, the opportunity to engage on what does and doesn’t work, and to take ownership of aspects of our culture that you care deeply about.
But we have duplicated some sentences; we need to preserve all substantive info but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication if it's in source. However we should try to not repeat same sentences unnecessarily but it's okay if they appear in source. The source had some repetition: "You will work daily with Production, Systems Engineering and our Head of Logistics, and you will be the single point of accountability for whether material is where it needs to be. There is no team reporting to you on day one. There is a clear path to building one." appears twice. We could keep both but it's redundant. Might be okay but better to keep once. However we risk losing some info if we remove duplicate? The duplicate is same info, so removing one doesn't lose info. We'll keep one.
Now Responsibilities: list from day-to-day:
- Own the Buy, End to End. Place, expedite and close purchase orders across all production and prototype commodities.
- Run the shortage list daily, hold suppliers to their commit dates, and know when to trigger the next order before MRP tells you.
- Build the Supplier Base. Identify, qualify and negotiate with suppliers across electronics, semiconductors, machined parts and contract manufacturing. Establish terms, pricing agreements and second sources for every single-point-of-failure part.
- Set the Compliance Posture. Know what good looks like and build it in from the start — NDAA Section 889/5949 screening, FAR/DFARS flow-downs, ITAR/EAR export controls, counterfeit-part avoidance (AS5553) and supplier documentation that will survive an audit.
- Purchasing Process & Data Ownership. Define the purchasing process, approval thresholds and supplier documentation standards. Own procurement data quality — part, cost, lead-time and sourcing records — inside the MRP/ERP our Head of Production is standing up, and represent supply chain requirements in that rollout.
- Synchronize with Production and Logistics. Convert the build schedule into a buy plan. Work hand-in-glove with the Head of Logistics on inbound freight, receiving and inventory, and with Production on kitting readiness and line-side availability.
- Support NPI. Partner with Systems Engineering on BOMs, ECOs, alternates and end-of-life parts. Quote new designs early, source prototype material fast, and drive designs toward parts we can actually get at volume.
- Manage Risk. Map geopolitical, allocation and lead-time exposure across the BOM. Maintain buffer and last-time-buy strategies for long-lead and sole-source items so a single shortage never stops a build.
- Grow the Function. Document what you build, then hire and mentor the buyers and planners who come after you as U.S. volume scales.
We'll put each as - .
Now Requirements: from "You should apply if you":
- 7–12 years in supply chain, procurement, strategic sourcing or planning within a hardware manufacturing environment (semiconductor, high-tech, advanced manufacturing, robotics, or aerospace/defense).
- Have personally owned POs, supplier commit dates and shortage resolution within the last few years — and you are eager to do it again without a team beneath you.
- Demonstrated ownership of supplier selection, qualification and commercial negotiation, not just execution against someone else's sourcing decisions.
- Working knowledge of — or the demonstrated ability to rapidly master — NDAA compliance, FAR/DFARS flow-downs, ITAR/EAR and counterfeit-part avoidance, and the judgement to know which rules bind in which situation.
- Hands-on daily user of an MRP/ERP (NetSuite, SAP, Odoo, Arena, Duro or similar) — able to run demand, planning and purchasing from the system and keep its data trustworthy.
- Comfortable with multi-level BOMs, drawings and ECO workflows, and credible in a technical conversation with engineers about alternates and part selection.
- Proven effectiveness where the process does not exist yet — fixing today's problem and building tomorrow's system at the same time.
- Ability to obtain and maintain a U.S. Security Clearance (Secret or Top Secret). U.S. Citizenship is required.
Note: Also 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." That's a note, we could include as a paragraph after list.
Now Skills (Nice to
Requirements
with- each bullet from "You should apply if you".
Skills
with- each bullet from "Nice to Have".
Benefits
with- from "What We Offer": insurance coverage (medical and travel), flexible paid time off, paid holidays, remote and/or hybrid work available depending on position. Also "focus on outcomes, not time-tracking" maybe a benefit? It's more culture. Could include as bullet.
We must not include boilerplate like EEO, legal, privacy, etc. Also remove "Join Helsing and work with world-leading experts..." paragraphs (that's more about culture). Could be omitted as not fitting sections? Might be considered part of About the role? But it's more about company culture. Could be omitted as not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info. Where to place? Could be part of "About the role" or maybe a separate section like "About Helsing". But headings list didn't include that. However we could still include a heading like "About Helsing" but instruction says use headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; but we could also add other headings if needed? Safer to stick to those headings and fit content accordingly. We could incorporate the "Join Helsing..." paragraphs into About the role or Benefits? Probably About the role includes description of role and company mission. The "Who We Are" paragraph at start: "Helsing develops artificial intelligence-enabled capabilities to protect and defend democracies..." That's about company. Could be part of About the role. Thus About the role section can contain multiple paragraphs: Who we are, The role description, Join Helsing... etc. We must not include legal/EEO etc. Now craft HTML. We need to ensure no markdown fences, just raw HTML. Let's draft:
About the role
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.
This is Helsing's first supply chain hire in the United States. You will set up how we buy — and then do the buying yourself. Expect to spend your first year as a player-coach: designing the supplier strategy, the sourcing playbook and the compliance posture in the morning, and placing purchase orders, chasing commit dates and clearing the shortage list in the afternoon. We are deliberately not hiring a pure strategist or a pure buyer. The person who succeeds here can hold both altitudes: they know what "right" looks like for a defense supply chain — NDAA, ITAR/EAR, DFARS flow-downs, counterfeit-part avoidance — and they are equally comfortable on the phone with a distributor at 7pm to pull a lead time in by three weeks. You will work daily with Production, Systems Engineering and our Head of Logistics, and you will be the single point of accountability for whether material is where it needs to be. There is no team reporting to you on day one. There is a clear path to building one.
You will work daily with Production, Systems Engineering and our Head of Logistics, and you will be the single point of accountability for whether material is where it needs to be. There is no team reporting to you on day one. There is a clear path to building one.
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 and novel capabilities. This means we take bets, aim high, and focus on big opportunities. Despite being a relatively young company, Helsing has already been selected for multiple significant government contracts. We actively encourage healthy, proactive, and diverse debate internally about what we do and how we choose to do it. Teams and individual engineers are trusted (and encouraged) to practice responsible autonomy and critical thinking, and to focus on outcomes, not conformity. At Helsing you will have a say in how we (and you!) work, the opportunity to engage on what does and doesn’t work, and to take ownership of aspects of our culture that you care deeply about.
But we have duplicated some sentences; we need to preserve all substantive info but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication if it's in source. However we should try to not repeat same sentences unnecessarily but it's okay if they appear in source. The source had some repetition: "You will work daily with Production, Systems Engineering and our Head of Logistics, and you will be the single point of accountability for whether material is where it needs to be. There is no team reporting to you on day one. There is a clear path to building one." appears twice. We could keep both but it's redundant. Might be okay but better to keep once. However we risk losing some info if we remove duplicate? The duplicate is same info, so removing one doesn't lose info. We'll keep one. Now Responsibilities: list from day-to-day: - Own the Buy, End to End. Place, expedite and close purchase orders across all production and prototype commodities. - Run the shortage list daily, hold suppliers to their commit dates, and know when to trigger the next order before MRP tells you. - Build the Supplier Base. Identify, qualify and negotiate with suppliers across electronics, semiconductors, machined parts and contract manufacturing. Establish terms, pricing agreements and second sources for every single-point-of-failure part. - Set the Compliance Posture. Know what good looks like and build it in from the start — NDAA Section 889/5949 screening, FAR/DFARS flow-downs, ITAR/EAR export controls, counterfeit-part avoidance (AS5553) and supplier documentation that will survive an audit. - Purchasing Process & Data Ownership. Define the purchasing process, approval thresholds and supplier documentation standards. Own procurement data quality — part, cost, lead-time and sourcing records — inside the MRP/ERP our Head of Production is standing up, and represent supply chain requirements in that rollout. - Synchronize with Production and Logistics. Convert the build schedule into a buy plan. Work hand-in-glove with the Head of Logistics on inbound freight, receiving and inventory, and with Production on kitting readiness and line-side availability. - Support NPI. Partner with Systems Engineering on BOMs, ECOs, alternates and end-of-life parts. Quote new designs early, source prototype material fast, and drive designs toward parts we can actually get at volume. - Manage Risk. Map geopolitical, allocation and lead-time exposure across the BOM. Maintain buffer and last-time-buy strategies for long-lead and sole-source items so a single shortage never stops a build. - Grow the Function. Document what you build, then hire and mentor the buyers and planners who come after you as U.S. volume scales. We'll put each as - . Now Requirements: from "You should apply if you": - 7–12 years in supply chain, procurement, strategic sourcing or planning within a hardware manufacturing environment (semiconductor, high-tech, advanced manufacturing, robotics, or aerospace/defense). - Have personally owned POs, supplier commit dates and shortage resolution within the last few years — and you are eager to do it again without a team beneath you. - Demonstrated ownership of supplier selection, qualification and commercial negotiation, not just execution against someone else's sourcing decisions. - Working knowledge of — or the demonstrated ability to rapidly master — NDAA compliance, FAR/DFARS flow-downs, ITAR/EAR and counterfeit-part avoidance, and the judgement to know which rules bind in which situation. - Hands-on daily user of an MRP/ERP (NetSuite, SAP, Odoo, Arena, Duro or similar) — able to run demand, planning and purchasing from the system and keep its data trustworthy. - Comfortable with multi-level BOMs, drawings and ECO workflows, and credible in a technical conversation with engineers about alternates and part selection. - Proven effectiveness where the process does not exist yet — fixing today's problem and building tomorrow's system at the same time. - Ability to obtain and maintain a U.S. Security Clearance (Secret or Top Secret). U.S. Citizenship is required. Note: Also 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." That's a note, we could include as a paragraph after list. Now Skills (Nice to
- from "What We Offer": insurance coverage (medical and travel), flexible paid time off, paid holidays, remote and/or hybrid work available depending on position. Also "focus on outcomes, not time-tracking" maybe a benefit? It's more culture. Could include as bullet.
We must not include boilerplate like EEO, legal, privacy, etc. Also remove "Join Helsing and work with world-leading experts..." paragraphs (that's more about culture). Could be omitted as not fitting sections? Might be considered part of About the role? But it's more about company culture. Could be omitted as not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info. Where to place? Could be part of "About the role" or maybe a separate section like "About Helsing". But headings list didn't include that. However we could still include a heading like "About Helsing" but instruction says use headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "Use
- each bullet from "Nice to Have".