Business Strategy & Operations Lead
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Intro paragraph: "Denver, CO Operations – Business Operations / Full-Time / On-site apply for this job Xcimer Energy leverages decades of research on Inertial Fusion Energy (IFE) combined with groundbreaking new laser architecture. Our mission is to deploy fusion power plants to meet global decarbonization goals as fast as possible. Xcimer has assembled a team of leaders in tough tech, fusion science, and manufacturing with a track record of rapid execution. Supported by leading investors, Xcimer is uniquely positioned to deliver limitless, clean, fusion power to combat climate change. Join us in powering a better world with inertial fusion! This is a full-time role based at our headquarters in Denver, CO, reporting to the Chief Operating Officer."
We can treat that as "About the role" section.
Then "As a Strategy & Operations Lead, you will apply your skills to connecting Xcimer's strategic priorities to day-to-day execution by partnering with Program Management and the Chief of Staff to close the gap between decisions made in leadership reviews and what actually gets built, running the analysis that informs program and resource prioritization, and personally driving the rollout, training, and adoption of new operational processes across the company. You'll often be the connective tissue on initiatives that don't sit cleanly inside any one function, owning ambiguous, cross-functional problems end-to-end, from first framing through implementation, and handing off a clean, sustainable process rather than a one-time fix. We are looking for our operations leaders to apply their technical expertise, problem solving skills, and dedication to quality to positively impact the future of energy!"
That could be part of About the role or Responsibilities. But we have a separate "Responsibilities" heading later.
After that, there is a "Responsibilities" heading (uppercase) with bullet list items.
Then "Qualifications" heading with bullet list.
Then "Desired Experience" heading with bullet list.
Then salary line: "$155,000 - $182,000 a year" plus note about actual base salary determined individually.
Then "Benefits" heading with bullet list.
Then other sections: "Equal Employment Opportunity" (EEO) which is boilerplate; we should remove.
Then "We may use artificial intelligence (AI) tools..." also boilerplate; remove.
Then "apply for this job Xcimer Energy Home Page Jobs powered by" - remove.
Thus we need sections: About the role (intro + maybe some description), Responsibilities, Qualifications, Desired Experience (could be considered Skills?), Benefits, Pay.
We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no explicit Schedule info (full-time on-site mentioned). Could we infer schedule? The posting says "Full-Time / On-site". That's schedule info: full-time, on-site. So we could create a Schedule section with that info. But we need to ensure we only include sections with real specific content. The posting does mention full-time and on-site. So we can include Schedule section with that.
We have Pay: salary range.
We have Benefits: bullet list.
We have Qualifications: bullet list (including education, experience, etc.)
We have Desired Experience: bullet list (could be considered Skills). The instruction says use Skills heading for skills. Could combine Desired Experience under Skills. But we need to avoid thin sections; maybe we merge Desired Experience into Qualifications or Skills. However we have both Qualifications and Desired Experience; we could treat Qualifications as mandatory qualifications, and Desired Experience as Skills (preferred). So we can have Qualifications section (mandatory) and Skills section (desired). That seems appropriate.
Thus sections:
- About the role (intro paragraph + maybe the description of role before Responsibilities)
- Responsibilities (list)
- Qualifications (list)
- Skills (list) (desired experience)
- Benefits (list)
- Pay (maybe just a paragraph with salary range)
- Schedule (full-time, on-site)
We must not repeat job title as heading. Not include Job ID.
We must use
for each section heading.
Inside sections, use
for prose,
- for lists.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (or close). We must not drop any bullet content.
Let's extract bullet points.
Responsibilities (as listed):
- Serve as the implementation arm for newly approved operational processes: write clear, usable process documentation, design and run the training and rollout plan, and own the post-implementation adoption review.
- Own operational projects end-to-end — from problem definition through solutioning and implementation to a clean transition of ownership — coordinating finance, procurement, IT, facilities, and HR to deliver company-wide operational projects that don't sit cleanly inside a single engineering program.
- Own headcount planning and demand/supply forecasting for business-operations functions, building the tooling and processes that support efficient resource allocation as Xcimer scales.
- Define and evolve Xcimer's operational knowledge-management and information architecture (e.g., Confluence or similar), driving adoption and content hygiene across departments.
- Maintain a prioritized backlog of identified-but-unresourced operational process gaps across the company and recommend sequencing and resourcing to close them.
- Partner with other departments to map end-to-end business data workflows (e.g., Teamcenter, Boltline, ERP) and drive resolution of cross-team data and process gaps.
- Work with the Chief of Staff to translate decisions and action items from executive offsites and business reviews into resourced initiatives with clear owners, timelines, and follow-through.
- Identify, evaluate, and help mitigate operational risks and single points of failure across business operations functions.
- Partner with Finance to build and maintain the program-level economic models that connect technical and schedule decisions to long-run plant economics, capital requirements, and investment tradeoffs — feeding the assumptions Finance uses in its capital-markets and fundraising models — to support program prioritization and make/buy decisions.
- Partner with the Head of PMO to represent business-operations capacity and constraints (finance, procurement, IT, facilities, data systems) in program planning, ensuring program schedules are built against realistic support-function resourcing.
- Project-manage across large, cross-functional stakeholder groups: lead working sessions, wrangle multiple threads at once, and report progress up to executive stakeholders without dropping the ball.
- Prepare analysis and materials to support budget reviews, board updates, and investor reporting as requested by the COO.
Qualifications (as listed):
- Bachelor's degree in business, engineering, operations, or a related field; MBA or equivalent experience a plus.
- 5+ years of experience in strategy, business operations, program management, or management consulting, ideally supporting a hardware, deep-tech, or complex engineering organization.
- Demonstrated experience designing and rolling out operational processes end-to-end — including training and post-implementation follow-through — in a fast-growing or resource-constrained organization.
- Demonstrated experience with headcount planning, demand/supply forecasting, or workforce modeling in a scaling organization.
- Experience supporting facilities or space planning, ideally across multiple sites.
- Strong analytical and financial modeling skills, with comfort building quantitative models that connect technical or program decisions to business and economic outcomes.
- High ownership and low ego, with a bias toward proactively stepping into ambiguous, cross-functional problems rather than waiting to be assigned one.
- Excellent written and verbal communication skills, with the ability to work effectively — and lead meetings — across engineering, finance, procurement, IT, and executive stakeholders.
- Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee of granted asylum
Desired Experience (as listed):
- Experience in fusion, aerospace, defense, or other capital-intensive hardware development environments.
- Familiarity with PLM/ERP and business data systems (e.g., Teamcenter, Boltline, or similar) and the challenges of integrating data across them.
- Experience administering or architecting Confluence or a similar knowledge-management platform at scale.
- Experience with BI/analytics platforms such as Looker, Tableau, or similar.
- Experience establishing or scaling a PMO, or working closely alongside one, in a matrixed engineering organization.
- Project Management Professional (PMP) or similar certification.
Benefits (as listed):
- medical, dental, and vision coverage;
- basic and supplemental life insurance;
- short- and long-term disability;
- paid parental leave for employees at the time of birth or adoption;
- and a 401(k) with a company match of up to 6%;
- Eligible employees also receive equity, allowing them to share in the company’s long-term success.
- Xcimer operates under a flexible Paid Time Off (ATO) approach. Rather than a fixed number of vacation days, employees are trusted to take the time they need to rest and recharge while meeting the expectations of their role and team.
- In addition, employees receive paid sick time, 13 company-paid holidays, and an annual paid company shutdown.
- Benefits are available to regular employees, including part-time and fixed-term roles, as well as interns, with eligibility varying by benefit.
We may need to keep the bullet formatting; but we can convert each bullet to
- . Some sentences have semicolons; we can keep as is.
Pay: "$155,000 - $182,000 a year Candidates may be considered for other positions at Xcimer Energy, and our actual base salary will be determined on an individual basis and may vary based on job-related knowledge and skills, education, and experience. The range is published in accordance with Colorado Equal Pay for Equal Work Act and California Equal Pay Act."
We should keep that as prose in Pay section.
Schedule: "This is a full-time role based at our headquarters in Denver, CO, reporting to the Chief Operating Officer." Also earlier: "Denver, CO Operations – Business Operations / Full-Time / On-site". So schedule: Full-time, On-site.
We can put schedule as a paragraph: "Full-time, on-site role based at Xcimer Energy's headquarters in Denver, CO."
Now we need to ensure we don't include any boilerplate like EEO, AI, etc.
Now produce HTML fragment.
We need to use
for each section heading.
We'll order sections logically: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule.
Make sure not to include empty sections.
Now craft HTML.
We'll need to escape any HTML special characters? The content includes ampersands (&) and em dashes (—). We can keep them as is; they are okay in HTML if we use proper encoding? The ampersand should be & but if we keep as & it might be interpreted as start of entity. Safer to encode as &. However the instruction says preserve ALL substantive information; but we can encode entities. Usually they'd accept raw & as it's ambiguous but better to encode. We'll encode & as &. Also em dash — is okay as Unicode; we can keep.
We'll need to ensure any < or > are not present; they aren't.
Now produce.
Let's draft:
About the role
Denver, CO Operations – Business Operations / Full-Time / On-site. Xcimer Energy leverages decades of research on Inertial Fusion Energy (IFE) combined with
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Intro paragraph: "Denver, CO Operations – Business Operations / Full-Time / On-site apply for this job Xcimer Energy leverages decades of research on Inertial Fusion Energy (IFE) combined with groundbreaking new laser architecture. Our mission is to deploy fusion power plants to meet global decarbonization goals as fast as possible. Xcimer has assembled a team of leaders in tough tech, fusion science, and manufacturing with a track record of rapid execution. Supported by leading investors, Xcimer is uniquely positioned to deliver limitless, clean, fusion power to combat climate change. Join us in powering a better world with inertial fusion! This is a full-time role based at our headquarters in Denver, CO, reporting to the Chief Operating Officer." We can treat that as "About the role" section. Then "As a Strategy & Operations Lead, you will apply your skills to connecting Xcimer's strategic priorities to day-to-day execution by partnering with Program Management and the Chief of Staff to close the gap between decisions made in leadership reviews and what actually gets built, running the analysis that informs program and resource prioritization, and personally driving the rollout, training, and adoption of new operational processes across the company. You'll often be the connective tissue on initiatives that don't sit cleanly inside any one function, owning ambiguous, cross-functional problems end-to-end, from first framing through implementation, and handing off a clean, sustainable process rather than a one-time fix. We are looking for our operations leaders to apply their technical expertise, problem solving skills, and dedication to quality to positively impact the future of energy!" That could be part of About the role or Responsibilities. But we have a separate "Responsibilities" heading later. After that, there is a "Responsibilities" heading (uppercase) with bullet list items. Then "Qualifications" heading with bullet list. Then "Desired Experience" heading with bullet list. Then salary line: "$155,000 - $182,000 a year" plus note about actual base salary determined individually. Then "Benefits" heading with bullet list. Then other sections: "Equal Employment Opportunity" (EEO) which is boilerplate; we should remove. Then "We may use artificial intelligence (AI) tools..." also boilerplate; remove. Then "apply for this job Xcimer Energy Home Page Jobs powered by" - remove. Thus we need sections: About the role (intro + maybe some description), Responsibilities, Qualifications, Desired Experience (could be considered Skills?), Benefits, Pay. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Schedule info (full-time on-site mentioned). Could we infer schedule? The posting says "Full-Time / On-site". That's schedule info: full-time, on-site. So we could create a Schedule section with that info. But we need to ensure we only include sections with real specific content. The posting does mention full-time and on-site. So we can include Schedule section with that. We have Pay: salary range. We have Benefits: bullet list. We have Qualifications: bullet list (including education, experience, etc.) We have Desired Experience: bullet list (could be considered Skills). The instruction says use Skills heading for skills. Could combine Desired Experience under Skills. But we need to avoid thin sections; maybe we merge Desired Experience into Qualifications or Skills. However we have both Qualifications and Desired Experience; we could treat Qualifications as mandatory qualifications, and Desired Experience as Skills (preferred). So we can have Qualifications section (mandatory) and Skills section (desired). That seems appropriate. Thus sections: - About the role (intro paragraph + maybe the description of role before Responsibilities) - Responsibilities (list) - Qualifications (list) - Skills (list) (desired experience) - Benefits (list) - Pay (maybe just a paragraph with salary range) - Schedule (full-time, on-site) We must not repeat job title as heading. Not include Job ID. We must use
for each section heading. Inside sections, use
for prose,
- for lists. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (or close). We must not drop any bullet content. Let's extract bullet points. Responsibilities (as listed): - Serve as the implementation arm for newly approved operational processes: write clear, usable process documentation, design and run the training and rollout plan, and own the post-implementation adoption review. - Own operational projects end-to-end — from problem definition through solutioning and implementation to a clean transition of ownership — coordinating finance, procurement, IT, facilities, and HR to deliver company-wide operational projects that don't sit cleanly inside a single engineering program. - Own headcount planning and demand/supply forecasting for business-operations functions, building the tooling and processes that support efficient resource allocation as Xcimer scales. - Define and evolve Xcimer's operational knowledge-management and information architecture (e.g., Confluence or similar), driving adoption and content hygiene across departments. - Maintain a prioritized backlog of identified-but-unresourced operational process gaps across the company and recommend sequencing and resourcing to close them. - Partner with other departments to map end-to-end business data workflows (e.g., Teamcenter, Boltline, ERP) and drive resolution of cross-team data and process gaps. - Work with the Chief of Staff to translate decisions and action items from executive offsites and business reviews into resourced initiatives with clear owners, timelines, and follow-through. - Identify, evaluate, and help mitigate operational risks and single points of failure across business operations functions. - Partner with Finance to build and maintain the program-level economic models that connect technical and schedule decisions to long-run plant economics, capital requirements, and investment tradeoffs — feeding the assumptions Finance uses in its capital-markets and fundraising models — to support program prioritization and make/buy decisions. - Partner with the Head of PMO to represent business-operations capacity and constraints (finance, procurement, IT, facilities, data systems) in program planning, ensuring program schedules are built against realistic support-function resourcing. - Project-manage across large, cross-functional stakeholder groups: lead working sessions, wrangle multiple threads at once, and report progress up to executive stakeholders without dropping the ball. - Prepare analysis and materials to support budget reviews, board updates, and investor reporting as requested by the COO. Qualifications (as listed): - Bachelor's degree in business, engineering, operations, or a related field; MBA or equivalent experience a plus. - 5+ years of experience in strategy, business operations, program management, or management consulting, ideally supporting a hardware, deep-tech, or complex engineering organization. - Demonstrated experience designing and rolling out operational processes end-to-end — including training and post-implementation follow-through — in a fast-growing or resource-constrained organization. - Demonstrated experience with headcount planning, demand/supply forecasting, or workforce modeling in a scaling organization. - Experience supporting facilities or space planning, ideally across multiple sites. - Strong analytical and financial modeling skills, with comfort building quantitative models that connect technical or program decisions to business and economic outcomes. - High ownership and low ego, with a bias toward proactively stepping into ambiguous, cross-functional problems rather than waiting to be assigned one. - Excellent written and verbal communication skills, with the ability to work effectively — and lead meetings — across engineering, finance, procurement, IT, and executive stakeholders. - Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee of granted asylum Desired Experience (as listed): - Experience in fusion, aerospace, defense, or other capital-intensive hardware development environments. - Familiarity with PLM/ERP and business data systems (e.g., Teamcenter, Boltline, or similar) and the challenges of integrating data across them. - Experience administering or architecting Confluence or a similar knowledge-management platform at scale. - Experience with BI/analytics platforms such as Looker, Tableau, or similar. - Experience establishing or scaling a PMO, or working closely alongside one, in a matrixed engineering organization. - Project Management Professional (PMP) or similar certification. Benefits (as listed): - medical, dental, and vision coverage; - basic and supplemental life insurance; - short- and long-term disability; - paid parental leave for employees at the time of birth or adoption; - and a 401(k) with a company match of up to 6%; - Eligible employees also receive equity, allowing them to share in the company’s long-term success. - Xcimer operates under a flexible Paid Time Off (ATO) approach. Rather than a fixed number of vacation days, employees are trusted to take the time they need to rest and recharge while meeting the expectations of their role and team. - In addition, employees receive paid sick time, 13 company-paid holidays, and an annual paid company shutdown. - Benefits are available to regular employees, including part-time and fixed-term roles, as well as interns, with eligibility varying by benefit. We may need to keep the bullet formatting; but we can convert each bullet to
- . Some sentences have semicolons; we can keep as is.
Pay: "$155,000 - $182,000 a year Candidates may be considered for other positions at Xcimer Energy, and our actual base salary will be determined on an individual basis and may vary based on job-related knowledge and skills, education, and experience. The range is published in accordance with Colorado Equal Pay for Equal Work Act and California Equal Pay Act."
We should keep that as prose in Pay section.
Schedule: "This is a full-time role based at our headquarters in Denver, CO, reporting to the Chief Operating Officer." Also earlier: "Denver, CO Operations – Business Operations / Full-Time / On-site". So schedule: Full-time, On-site.
We can put schedule as a paragraph: "Full-time, on-site role based at Xcimer Energy's headquarters in Denver, CO."
Now we need to ensure we don't include any boilerplate like EEO, AI, etc.
Now produce HTML fragment.
We need to use
for each section heading. We'll order sections logically: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Make sure not to include empty sections. Now craft HTML. We'll need to escape any HTML special characters? The content includes ampersands (&) and em dashes (—). We can keep them as is; they are okay in HTML if we use proper encoding? The ampersand should be & but if we keep as & it might be interpreted as start of entity. Safer to encode as &. However the instruction says preserve ALL substantive information; but we can encode entities. Usually they'd accept raw & as it's ambiguous but better to encode. We'll encode & as &. Also em dash — is okay as Unicode; we can keep. We'll need to ensure any < or > are not present; they aren't. Now produce. Let's draft:
About the role
Denver, CO Operations – Business Operations / Full-Time / On-site. Xcimer Energy leverages decades of research on Inertial Fusion Energy (IFE) combined with