Manager, Quality
U.S. Fusion Energy · Energy, IL · 3 wk ago
On-siteQuality Assurance$182k–$214k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each section heading. Only include sections where posting has real specific content. We have:
- Overview/About Helion (company description) maybe "About the role"? Actually "About Helion" is company description, not role. The posting includes "OverviewApplication About Helion ..." The "About Helion" is company description. Could be considered "About the role"? Not exactly. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We have:
- "What You Will Be Doing" -> Responsibilities.
- "You Will Build and lead Helion’s quality organization ..." also responsibilities (maybe bullet list). So we can combine.
- "Required Skills" -> Requirements/Qualifications/Skills. Could be Requirements.
- "Benefits" -> Benefits.
- "Compensation Range: $182K - $214K" -> Pay.
- No schedule info (full time, on-site). Could include Schedule? The posting mentions "Employment Type Full time Location Type On-site". That's schedule info (full-time, on-site). So we can include Schedule section with that.
- Also location: Everett, WA. Could be part of Schedule or maybe not needed. But we can include location in Schedule or maybe not needed. The instruction: include a section ONLY when posting has real specific content. So we can include Schedule with "Full-time, on-site in Everett, WA".
- Pay: include compensation range.
- Benefits: list benefits.
- Responsibilities: list duties.
- Requirements: list required skills/qualifications.
- Possibly Qualifications separate? Could combine Requirements and Qualifications. But we can have Requirements (education, experience) and Skills (specific skills). The posting includes "Required Skills" bullet list with education, years experience, etc. Could treat as Requirements. Skills maybe not separate. But we can still include Skills if we have specific skills list: knowledge of quality engineering principles and tools etc. That is also in Required Skills. Might split: Requirements: education, years experience, team leadership. Skills: quality engineering principles, tools, etc. But we can keep one section.
Better to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those that have content.
We have:
- About the role: maybe a brief summary of role? The posting includes "What You Will Be Doing" and "You Will Build...". That's responsibilities. About the role could be a brief overview: "Build and lead Helion's quality function from the ground up..." Might be considered About the role. But we can just use Responsibilities for that.
We need to avoid repeating job title as heading. Not needed.
We must not include boilerplate like EEO, etc.
We must preserve all substantive information.
Let's extract substantive content:
Company description: "We are a fusion power company based in Everett, WA, with the mission to build the world's first fusion power plant, enabling a future with unlimited clean electricity. Our vision is a world with clean, reliable, and affordable energy for everyone. Since Helion's founding in 2013, we have raised $1.5 billion from long-time investors such as Sam Altman, Mithril, and Capricorn Investment Group as well as new investors including Thrive Capital, LightSpeed Venture Capital, SoftBank, and others to propel us forward. Our current prototype, Polaris, has reached record-breaking plasma temperatures of 150 million degrees Celsius (13 keV). Helion is continuing to iterate and on the path to the world's first fusion power plant, Orion. This is a pivotal time to join Helion. You will tackle real-world challenges with a team that prizes urgency, rigor, ownership, and a commitment to delivering hard truths – values essential to achieving what no one has before. Together, we will change the future of energy, because the world can't wait."
That's about the company, could be placed under "About the role"? Actually "About the role" is about the role, not company. But we could put under "About the role" a short description of the role and maybe include company mission? Might be okay.
But we have a separate "About Helion" which is company overview. Could be placed under "About the role" as context. The instruction didn't forbid including company description. It said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with company overview and role summary.
Responsibilities: bullet list from "What You Will Be Doing" and "You Will Build and lead Helion’s quality organization...".
Let's extract responsibilities:
- Build and lead Helion's quality function from the ground up, creating the people, systems, standards, and operating rhythms needed to deliver first-of-a-kind fusion hardware with repeatable, measurable, and scalable quality.
- Establish the quality strategy, processes, and culture that enable Helion to move quickly while ensuring quality is built into every stage of the hardware lifecycle.
- Partner closely with Engineering, Manufacturing, Supply Chain, Operations, and Test to prevent defects before they occur, identify and mitigate risk, solve complex problems at their root cause, and continuously improve execution as we scale toward commercial fusion power.
- Build and lead Helion’s quality organization across Quality Engineering, Supplier Quality, Inspection, and Quality Systems
- Hire, develop, and mentor a high-performing technical team that promotes ownership, continuous learning, and operational excellence
- Design and scale practical quality systems, processes, standards, inspection strategies, traceability, and metrics that support speed and rigor
- Own quality execution across the hardware lifecycle, including nonconformance management, MRB, CAPA, supplier quality, root cause analysis, and continuous improvement
- Partner with Engineering, Manufacturing, Supply Chain, Operations, and Test to build quality in early, improve process capability, reduce defects, and increase first-pass yield
- Foster a culture where quality is everyone’s responsibility, using structured problem-solving and data-driven decisions to identify risk and support Helion’s growth from prototype to commercial-scale production
That's a lot; we can keep as bullet list.
Requirements: education and experience:
- Bachelor's degree in Engineering, Manufacturing, Quality, or a related technical field
- 7+ years of experience in quality, manufacturing, supplier quality, hardware engineering, production engineering, or a related discipline, including experience in complex hardware environments
- 3+ years of experience building and leading high-performing technical teams and developing quality capabilities at scale
- Demonstrated success designing, implementing, or transforming quality systems that improve consistency, accountability, and execution without creating unnecessary bureaucracy
Skills: knowledge of quality engineering principles and tools including supplier quality, nonconformance management, MRB, CAPA, FMEA, root cause analysis, inspection planning, and statistical problem-solving with the ability to influence cross-functional teams and drive durable results
We could put that under Skills.
Benefits: list:
- Medical, Dental, and Vision plans for employees and their families
- 31 Days of PTO (21 vacation days and 10 sick days)
- 10 Paid holidays, plus company-wide winter break
- Up to 5% employer 401(k) match
- Short term disability, long term disability, and life insurance
- Paid parental leave and support (up to 16 weeks)
- Annual wellness stipend
Pay: Compensation Range: $182K - $214K
Schedule: Employment Type Full time, Location Type On-site, based in Everett, WA.
We could phrase: Full-time, on-site position in Everett, WA.
Now produce HTML:
for each section heading. Only include sections where posting has real specific content. We have:
- Overview/About Helion (company description) maybe "About the role"? Actually "About Helion" is company description, not role. The posting includes "OverviewApplication About Helion ..." The "About Helion" is company description. Could be considered "About the role"? Not exactly. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content accordingly.
We have:
- "What You Will Be Doing" -> Responsibilities.
- "You Will Build and lead Helion’s quality organization ..." also responsibilities (maybe bullet list). So we can combine.
- "Required Skills" -> Requirements/Qualifications/Skills. Could be Requirements.
- "Benefits" -> Benefits.
- "Compensation Range: $182K - $214K" -> Pay.
- No schedule info (full time, on-site). Could include Schedule? The posting mentions "Employment Type Full time Location Type On-site". That's schedule info (full-time, on-site). So we can include Schedule section with that.
- Also location: Everett, WA. Could be part of Schedule or maybe not needed. But we can include location in Schedule or maybe not needed. The instruction: include a section ONLY when posting has real specific content. So we can include Schedule with "Full-time, on-site in Everett, WA".
- Pay: include compensation range.
- Benefits: list benefits.
- Responsibilities: list duties.
- Requirements: list required skills/qualifications.
- Possibly Qualifications separate? Could combine Requirements and Qualifications. But we can have Requirements (education, experience) and Skills (specific skills). The posting includes "Required Skills" bullet list with education, years experience, etc. Could treat as Requirements. Skills maybe not separate. But we can still include Skills if we have specific skills list: knowledge of quality engineering principles and tools etc. That is also in Required Skills. Might split: Requirements: education, years experience, team leadership. Skills: quality engineering principles, tools, etc. But we can keep one section.
Better to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those that have content.
We have:
- About the role: maybe a brief summary of role? The posting includes "What You Will Be Doing" and "You Will Build...". That's responsibilities. About the role could be a brief overview: "Build and lead Helion's quality function from the ground up..." Might be considered About the role. But we can just use Responsibilities for that.
We need to avoid repeating job title as heading. Not needed.
We must not include boilerplate like EEO, etc.
We must preserve all substantive information.
Let's extract substantive content:
Company description: "We are a fusion power company based in Everett, WA, with the mission to build the world's first fusion power plant, enabling a future with unlimited clean electricity. Our vision is a world with clean, reliable, and affordable energy for everyone. Since Helion's founding in 2013, we have raised $1.5 billion from long-time investors such as Sam Altman, Mithril, and Capricorn Investment Group as well as new investors including Thrive Capital, LightSpeed Venture Capital, SoftBank, and others to propel us forward. Our current prototype, Polaris, has reached record-breaking plasma temperatures of 150 million degrees Celsius (13 keV). Helion is continuing to iterate and on the path to the world's first fusion power plant, Orion. This is a pivotal time to join Helion. You will tackle real-world challenges with a team that prizes urgency, rigor, ownership, and a commitment to delivering hard truths – values essential to achieving what no one has before. Together, we will change the future of energy, because the world can't wait."
That's about the company, could be placed under "About the role"? Actually "About the role" is about the role, not company. But we could put under "About the role" a short description of the role and maybe include company mission? Might be okay.
But we have a separate "About Helion" which is company overview. Could be placed under "About the role" as context. The instruction didn't forbid including company description. It said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with company overview and role summary.
Responsibilities: bullet list from "What You Will Be Doing" and "You Will Build and lead Helion’s quality organization...".
Let's extract responsibilities:
- Build and lead Helion's quality function from the ground up, creating the people, systems, standards, and operating rhythms needed to deliver first-of-a-kind fusion hardware with repeatable, measurable, and scalable quality.
- Establish the quality strategy, processes, and culture that enable Helion to move quickly while ensuring quality is built into every stage of the hardware lifecycle.
- Partner closely with Engineering, Manufacturing, Supply Chain, Operations, and Test to prevent defects before they occur, identify and mitigate risk, solve complex problems at their root cause, and continuously improve execution as we scale toward commercial fusion power.
- Build and lead Helion’s quality organization across Quality Engineering, Supplier Quality, Inspection, and Quality Systems
- Hire, develop, and mentor a high-performing technical team that promotes ownership, continuous learning, and operational excellence
- Design and scale practical quality systems, processes, standards, inspection strategies, traceability, and metrics that support speed and rigor
- Own quality execution across the hardware lifecycle, including nonconformance management, MRB, CAPA, supplier quality, root cause analysis, and continuous improvement
- Partner with Engineering, Manufacturing, Supply Chain, Operations, and Test to build quality in early, improve process capability, reduce defects, and increase first-pass yield
- Foster a culture where quality is everyone’s responsibility, using structured problem-solving and data-driven decisions to identify risk and support Helion’s growth from prototype to commercial-scale production
That's a lot; we can keep as bullet list.
Requirements: education and experience:
- Bachelor's degree in Engineering, Manufacturing, Quality, or a related technical field
- 7+ years of experience in quality, manufacturing, supplier quality, hardware engineering, production engineering, or a related discipline, including experience in complex hardware environments
- 3+ years of experience building and leading high-performing technical teams and developing quality capabilities at scale
- Demonstrated success designing, implementing, or transforming quality systems that improve consistency, accountability, and execution without creating unnecessary bureaucracy
Skills: knowledge of quality engineering principles and tools including supplier quality, nonconformance management, MRB, CAPA, FMEA, root cause analysis, inspection planning, and statistical problem-solving with the ability to influence cross-functional teams and drive durable results
We could put that under Skills.
Benefits: list:
- Medical, Dental, and Vision plans for employees and their families
- 31 Days of PTO (21 vacation days and 10 sick days)
- 10 Paid holidays, plus company-wide winter break
- Up to 5% employer 401(k) match
- Short term disability, long term disability, and life insurance
- Paid parental leave and support (up to 16 weeks)
- Annual wellness stipend
Pay: Compensation Range: $182K - $214K
Schedule: Employment Type Full time, Location Type On-site, based in Everett, WA.
We could phrase: Full-time, on-site position in Everett, WA.
Now produce HTML:
About the role
... company description and role summary ...
But we need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't duplicate content. Let's craft About the role paragraph summarizing company mission and role purpose. We can combine company description and brief role purpose: "Helion is a fusion power company ... This is a pivotal time to join Helion. You will tackle real-world challenges..." That's from the posting. Let's write:Helion is a fusion power company based in Everett, WA, with the mission to build the world's first fusion power plant, enabling a future with unlimited clean electricity. Since its founding in 2013, Helion has raised $1.5 billion from investors including Sam Altman, Mithril, Capricorn Investment Group, Thrive Capital, LightSpeed Venture Capital, SoftBank, and others. Its prototype Polaris has achieved plasma temperatures of 150 million °C (13 keV) and the company is advancing toward the Orion fusion power plant. In this role you will build and lead Helion's quality function from the ground up, creating the people, systems, standards, and operating rhythms needed to deliver first‑of‑a‑kind fusion hardware with repeatable, measurable, and scalable quality.
That seems good. Now Responsibilities:Responsibilities
- ... each bullet
Requirements
- ...
Skills
- ...
Benefits
- ...