Quality Engineer

We need to output HTML fragment with sections for headings present: About the role? Actually the posting includes "About Heaviside Industries" (company description) then "What You Will Do" (responsibilities), "What We Are Looking For" (requirements/qualifications/skills), "Additional Information" (compensation, benefits, ITAR, EEO). We need to follow rules: 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. We need to decide which sections to include. The posting includes: - About Heaviside Industries (company description). Could be "About the role"? Actually "About the role" is typical but we have company description. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt: we can use "About the role" for description of role? However we have "What You Will Do" which is responsibilities. "What We Are Looking For" is requirements/qualifications/skills. "Additional Information" includes compensation bands, benefits, ITAR requirement, EEO statement (which we should remove as boilerplate). Also mention "U.S. Person as defined by ITAR" is a requirement (citizenship). Also mention "Compensation bands are determined..." and "In addition to base salary, for full-time hires, you may also be eligible for long-term incentives, in the form of stock options, and access to medical, vision & dental coverage as well as access to a 401(k) retirement plan." That's benefits and compensation info. So we can have sections: Responsibilities (What You Will Do), Requirements (What We Are Looking For), Benefits (compensation and benefits). Possibly also "About the company" but not required; we could include as a brief paragraph under a heading like "About Heaviside Industries" but the instruction says use those specific headings; but we could still use

  for any section heading we want? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. Likely we should stick to those headings where applicable. So we can have:

  Responsibilities

  with list from "What You Will Do".

  Requirements

  with list from "What We Are Looking For" plus maybe the ITAR requirement.

  Benefits

  with compensation and benefits info. We could also have

  About the role

  with company description? But "About the role" is more about the role itself, not company. However we have no explicit "About the role" section. The company description could be considered "About Heaviside Industries". Not in the list but we could still include as a

  without heading? The instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding a heading not in the list, but the examples are given. Safer to stick to the given headings. So we will not add a heading for company description; we can incorporate that description into a

  before the first heading? The instruction says "Output ONLY the HTML fragment". It didn't say we cannot have introductory paragraph without heading. Probably okay. But we need to preserve all substantive information. The company description is substantive. We could put it in a

  before any heading. Now we need to format lists: Use

  • for any list of duties/requirements/benefits. We need to extract bullet points from the responsibilities section: "What You Will Do Nonconformance & Corrective Action Manage the NC(Non-Conformity)-Process (Root Cause – Corrective Action) Drive root cause analysis and corrective/preventive actions Track and report on nonconformance trends Audit & Compliance Plan and conduct primarily internal audits. External will probably be applicable in the future. Ensure compliance with ISO 9001 standard. Support certification and surveillance audits First Article Inspection (FAI) Plan and execute First Article Inspections Review and approve FAI documentation and reports Risk Management Identify, assess, and mitigate quality-related risks Maintain risk registers and support risk review processes Documentation & QMS Develop, maintain, and control QMS documents Manage document control processes (versioning, approvals, distribution) Ensure the Quality Management System is kept current and audit-ready Reporting Produce quality reporting for management and stakeholders Manage RMA (Return Merchandise Authorization) reporting and analysis Track quality metrics and KPIs Chemical Management Oversee chemical management processes and compliance requirements" We need to break into list items. Each bold heading seems like a category. We can make each category as a list item with sub-details maybe as part of same li. Could also split further but okay. Similarly requirements: "What We Are Looking For Strong understanding of nonconformance and corrective action (RC-CA) processes Working knowledge of ISO 9001 Experience conducting or supporting internal/external audits Experience with First Article Inspection (FAI) procedures Risk assessment and risk management skills Document management / QMS administration experience Analytical skills for quality and RMA reporting Familiarity with chemical management requirements and regulations Strong attention to detail and process discipline Good written and verbal communication skills for reporting and documentation U.S. Person as defined by ITAR (22 CFR120.62) NICE TO HAVE Experience in a manufacturing or defense industry environment Familiarity with ERP/MES systems Experience working across multi-site quality operations Knowledge about AS9100 and AQAP 2110 standards" We need to separate required vs nice-to-have? Could keep all in one list but maybe separate sections? The instruction says prefer few substantive sections over many thin ones. Could have Requirements section containing both required and nice-to-have as list items, maybe mark nice-to-have with parentheses. But we should preserve all info. We'll just list them as items. Benefits section: "Additional Information Compensation bands are determined by role, level, location, and alignment with market data. Individual level and base pay is determined on a case-by-case basis and may vary based on job-related skills, education, experience, technical capabilities and internal equity. In addition to base salary, for full-time hires, you may also be eligible for long-term incentives, in the form of stock options, and access to medical, vision & dental coverage as well as access to a 401(k) retirement plan. To conform to U.S. Government space technology export regulations, including the International Traffic in Arms Regulations (ITAR) you must be a U.S. citizen, lawful permanent resident of the U.S., protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to obtain the required authorizations from the U.S. Department of State. Learn more about the ITAR here. (https://www.pmddtc.state.gov/?id=ddtc_kb_article_page&sys_id=24d528fddbfc930044f9ff621f961987) Heaviside is an Equal Opportunity Employer; employment with Heaviside is governed on the basis of merit, competence and qualifications and will not be influenced in any manner by race, color, religion, gender, national origin/ethnicity, veteran status, disability status, age, sexual orientation, gender identity, marital status, physical disability or any other legally protected status." We need to remove EEO boilerplate (the last sentence). Also remove the link? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to ITAR is maybe part of legal? It's a reference; but it's not boilerplate; it's a link to learn more about ITAR. Might be considered legal? It's a reference; but we could keep the sentence about ITAR requirement but drop the link? The instruction says remove boilerplate; the link is not boilerplate but it's a URL. Might be okay to keep but it's a link; we could keep as plain text without markup. However we should not include the link as it's not essential? The requirement is to be a US person; the link is extra. We could keep the sentence without the URL. The instruction says preserve ALL substantive information; the URL is not substantive? It's a reference; maybe not needed. Safer to drop the URL and the "Learn more about the ITAR here." phrase, as it's supplemental. Keep the requirement sentence. Thus Benefits section will have paragraphs about compensation, benefits, ITAR requirement. We need to use

    for prose,

    • for lists. Thus final HTML:

      Heaviside Industries builds multi-domain autonomous precision munitions for U.S. and allied special operations and conventional forces. While modern warfare has rapidly evolved with the proliferation of unmanned systems, hyper-precise munitions in contested environments are the future of the battlefield. Economical precision strike capabilities are critical to U.S. and allied war efforts, enabling successful defeat of enemy military assets and infrastructure. Heaviside builds precision munitions designed to operate in GPS-denied and spectrum-jammed battlefields—where traditional systems degrade or fail—without inflated prices or sacrifice to performance. All engineering and manufacturing is conducted in-house in Heaviside's Los Angeles, CA headquarters and Oslo, Norway office. Heaviside is backed by Interlagos, Menlo Ventures, Flume Ventures, Cantos, Anorak Ventures, and Ravelin Ventures.

      Responsibilities

      • Nonconformance & Corrective Action: Manage the NC (Non-Conformity) Process (Root Cause – Corrective Action); drive root cause analysis and corrective/preventive actions; track and report on nonconformance trends.
      • Audit & Compliance: Plan and conduct primarily internal audits (external audits likely in the future); ensure compliance with ISO 9001 standard; support certification and surveillance audits.
      • First Article Inspection (FAI): Plan and execute First Article Inspections; review and approve FAI documentation and reports.
      • Risk Management: Identify, assess, and mitigate quality-related risks; maintain risk registers and support risk review processes.
      • Documentation & QMS: Develop, maintain, and control QMS documents; manage document control processes (versioning, approvals, distribution); ensure the Quality Management System is kept current and audit-ready.
      • Reporting: Produce quality reporting for management and stakeholders; manage RMA (Return Merchandise Authorization) reporting and analysis; track quality metrics and KPIs.
      • Chemical Management: Oversee chemical management processes and compliance requirements.

      Requirements

      • Strong understanding of nonconformance and corrective action (RC-CA) processes.
      • Working knowledge of