Buyer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: Who We Are, Export Control Compliance, Equal Opportunity Statement, etc. Also remove navigation, legal, EEO, scam-warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Content: - Who We Are (mission) - maybe not needed? It's not a required heading; we can include as maybe "About the company"? But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if content exists. "About the role" likely corresponds to the "About The Role" paragraph. So we will put that content under

About the role

with

. Responsibilities: from "What You’ll Do" bullet list. We'll put under

Responsibilities

with

• . Requirements: maybe "Required Qualifications". That's a list of qualifications. Could be under Requirements or Qualifications. The instruction includes both Requirements and Qualifications headings. We need to decide where to put content. Likely "Required Qualifications" goes under Requirements (or Qualifications). Since both headings allowed, we can split: maybe Requirements for mandatory items, Qualifications for preferred? But we have both Required and Preferred Qualifications. Could put Required under Requirements, Preferred under Qualifications. Skills maybe separate? Could include skills under Skills heading (like proficiency with Microsoft Office, analytical skills). But we can also incorporate them in Requirements/Qualifications. To follow instruction, better to separate: Requirements = mandatory qualifications (Required Qualifications). Qualifications = preferred qualifications. Skills maybe could be extracted from both (like analytical, organizational, communication skills, proficiency with MS Office). But we could also put skills under Skills heading. However we must not create thin sections. Let's see content: Required Qualifications list includes many items: Bachelor's degree, 3 years experience, ERP systems, PLM systems, NPI experience, hands-on experience sourcing for prototype/production, understanding manufacturing processes and engineering BOMs, demonstrated success in supplier negotiations, cost reduction, supplier performance management, familiarity with FAR, DFARS, ITAR, US Gov acquisition regs, excellent analytical, organizational, communication skills, ability to understand new concepts quickly, apply them, organize work assignments, proficiency with Microsoft Office Suite, US Citizenship required due to ITAR & ability to obtain DoD security clearance. Preferred Qualifications list includes: 4+ years experience in aerospace/defense, startups, interfacing with DCAA/DCMA, materials management desirable, exposure to additive manufacturing, automation, advanced hardware, understanding supply chain risk management, supplier contingency planning, knowledge of forecasting tools, procurement analytics, market benchmarking, experience supporting R&D procurement and prototype builds. Work Environment: Based at HQ San Diego, daily on-site presence, must lift up to 25 lbs, wear PPE, occasional travel up to 10%. Compensation: US Salary Range: $78,000 - $105,000 USD. Benefits & Perks: list of benefits. Schedule? Not explicitly given besides occasional travel up to 10% and daily on-site presence. Could be considered schedule? Not explicit. Might not create Schedule section unless posting states schedule (like full-time, shift). It doesn't. So we omit Schedule. Pay: we have compensation range, so include Pay section. Benefits: we have Benefits & Perks, include Benefits section. Now we need to ensure we don't include boilerplate like "Who We Are", "Export Control Compliance", "Equal Opportunity Statement". Also remove duplicated lines. We need to preserve all substantive information. So we need to include the mission? Not under allowed headings; maybe we could incorporate into About the role? But About the role already has its own paragraph. The "Who We Are" is separate; but we could maybe include a brief intro under About the role? However instruction: "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." It doesn't forbid adding other headings not listed, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; but we could also have other headings? Probably better to stick to those. So we can omit "Who We Are" entirely? But that is substantive info about company mission. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit it, we lose substantive info. But maybe we can incorporate it into About the role section as a paragraph before the role description? The About the role heading could contain both the role description and maybe a brief about company? However the "About The Role" section in the posting is separate from "Who We Are". We could combine them under About the role heading: first paragraph about company mission, then paragraph about role. That would preserve info. Thus under

  About the role

  we can have two

  elements: one for Who We Are (mission) and one for About The Role description. Now Responsibilities: from "What You’ll Do" bullet list. We'll capture each bullet as

• . Need to ensure we keep all bullet points exactly. Let's extract bullet points from "What You’ll Do": - Procurement Operations - Execute full-cycle procurement: issue RFQs, evaluate suppliers, negotiate terms, place POs, manage delivery schedules, and resolve past-due items - Place purchase orders and work with receiving, quality, and finance to resolve downstream issues - Conduct price and cost analysis to inform acquisition strategies and contract negotiations - Implement cost-saving initiatives and track procurement expenditures - Compliance & Risk Management - Source, negotiate, and procure goods and services in compliance with FAR, DFARS, ITAR, and internal policies - Support the development and maintenance of a DCAA/DCMA-compliant procurement system - Ensure adherence to supply chain risk management frameworks (e.g., NIST 800-171) - Support internal and external audits, including DCAA/DCMA reviews - Maintain accurate and audit-ready procurement documentation and records - Supplier & Sourcing Strategy - Support engineering and operations in identifying and qualifying the best suppliers - Vet and onboard suppliers to meet DoD, cybersecurity, and regulatory requirements - Analyze supplier data to identify opportunities to expand or consolidate the Approved Supplier List - Manage supplier performance for quality, cost, and delivery; escalate and mitigate risks as needed - Conduct market research and benchmarking to ensure a best-in-class supply base - Cross-Functional Collaboration - Work on cross-functional projects to achieve cost, quality, and delivery targets - Collaborate with engineering on BOM creation, revisions, and sourcing impact for change management - Coordinate with inventory management and warehouse teams to maintain appropriate stock levels - Coordinate with the operations, finance and warehouse teams, to resolve invoicing and reconciliation issues - Help negotiate commercial terms and supplier agreements - Contribute to procurement process improvements and implement procedural enhancements - Communicate effectively with internal stakeholders and external suppliers across programs and departments We need to preserve all. We'll output as a flat list? Could keep subheadings? But we only allowed
  • . Could we include headings inside list? Not allowed. Better to just list all items as
  • preserving the text. Might lose grouping but still preserve content. That's acceptable. Now Requirements: from Required Qualifications list. We'll extract each line as
  • . Need to keep the exact phrasing. Let's list Required Qualifications lines: - Bachelor’s degree in supply chain, business, engineering or a related field - Minimum 3 years of supply chain or sourcing experience, in a manufacturing or technology environment, including technical procurement - Experience with ERP systems (e.g., Deltek Costpoint, SAP, etc.) & and PLM systems (e.g., Arena) - Demonstrated experience with New Product Introduction and Product Lifecycle Change Management processes - Hands-on experience sourcing and procuring for prototype and production builds - Strong understanding of manufacturing processes and engineering BOMs - Demonstrated success in supplier negotiations, cost reduction, and supplier performance management - Familiarity with FAR, DFARS, ITAR, and U.S. Government acquisition regulations - Excellent analytical, organizational, and communication skills - Must possess the ability to understand new concepts quickly, apply them accurately throughout an evolving environment, and organize work assignments to meet established timetables - Proficiency with Microsoft Office Suite (Excel, Word, Outlook, PowerPoint) - U.S. Citizenship required due to ITAR regulations & the ability to obtain and maintain a Department of Defense (DoD) security clearance Note there is a typo "& and". We'll keep as is. Now Qualifications (Preferred): list each. - 4+ years of procurement or supply chain experience in an aerospace or defense industries - Experience in startups or fast-growing environments - Demonstrated experience interfacing with DCAA, DCMA, or other U.S. Government oversight agencies - Materials management experience is desirable (i.e., warehousing, transportation, logistics) - Exposure to additive manufacturing, automation, or advanced hardware environments - Understanding of supply chain risk management and supplier contingency planning - Knowledge of forecasting tools, procurement analytics, and market benchmarking - Experience supporting R&D procurement and prototype builds Now Benefits: from Benefits & Perks paragraph. Need to capture all benefits listed. Paragraph: "Our culture fosters collaboration, respect, and trust, empowering passionate people to do their best work. We offer a competitive salary, comprehensive benefits, and opportunities for career growth. In addition to an opportunity to take part in an innovative, collaborative and fast-growing business with a highly motivated and skilled team, we also take pride in taking care of our employees. Here are just a few ways that we show our appreciation: We offer comprehensive medical, dental, and visions plans401(k) Retirement Savings Plan to invest in your long-term retirement goalsUnlimited PTOExtremely generous company holiday calendar, including a holiday hiatus in November, & December.Generous Parental Leave FSA DCFSAHSAHospital Indemnity insurance Critical Illness insurance Accident insurance Basic Life/AD&D, short-term and long-term disability insurance, 100% covered by Firestorm. Plus, the option to purchase additional life insurance for you and your family.Mental Health Resources: We provide free mental health resources 24/7 including therapy and more. Additional work-life services, such as free legal and financial support, are available to you as well." There's some missing spaces and concatenation. We need to preserve as is? Probably we should keep the text but maybe fix obvious missing spaces? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. We should not alter text except maybe to correct obvious formatting errors? It's ambiguous. Safer to keep as given, but we could add spaces for readability? Might be considered altering. I'd keep the exact text but maybe we can insert spaces where missing to make readable but not change meaning. However "visions plans401(k)" is obviously missing a space. If we keep as is, it's still substantive but weird. I'd add a space to make it readable but not change meaning. Similarly "Unlimited PTOExtremely" missing space. "November, & December." maybe okay. "FSA DCFSAHSA" missing spaces. Might be intended as "FSA, DCFSA, HSA". Hard