Senior Manager, Licensing
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We have content for About the role (the paragraph after "About The Role"). Responsibilities (list). Experience (maybe Requirements/Qualifications). Benefits (list). Pay (salary range). Schedule not mentioned, so omit. Skills maybe not separate; we could combine under Qualifications or Requirements. The instruction: Use headings for those section names if we have content. We need to decide which sections to include: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay. Possibly also Skills if we have specific skills listed (technical writing, AI tools, etc.) but we can incorporate into Requirements. Better to have Requirements (or Qualifications) covering experience and qualifications. We'll include Requirements. We'll not include Skills separately unless we have explicit skills list; we have "Strong technical writing skills" etc. Could be part of Requirements. We'll keep Requirements.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO statement, Export Control, Recruiting Fraud Alert. Also remove navigation etc. Keep all substantive info.
We need to preserve all substantive information: include the description about company, values, AI-first mindset etc. That is part of About the role? Actually that is general company description; could be part of About the role or maybe a separate section like "About the Company". But we only allowed headings from list; we could put that under About the role (since it's about the role and company). The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading and include the company description plus role description.
We must not include filler like "commensurate with experience". Not present.
We need to format lists with - . For responsibilities list, each bullet is a responsibility. For experience requirements, we can list as
- . Benefits list as
- . Pay as
maybe.
We must not include markdown code fences. Just raw HTML.
Let's craft:
About the role
... company description ... The Manager of Licensing supports ...
Then Responsibilities
- ... each responsibility ...
Then Requirements
- BS in Engineering or Science ...
- 8+ years of relevant engineering, project management, and/or licensing/regulatory affairs experience.
- Experience contributing to licensing/regulatory affairs efforts that resulted in regulatory outcomes ...
- Does not require having led these efforts end-to-end, but must demonstrate meaningful ownership of deliverables within them.
- Experience participating in NRC, DOE, and/or state-level regulator interactions (written and/or verbal), either as a lead or in a supporting capacity.
- Strong technical writing skills, with demonstrated experience drafting regulatory submissions, RAI responses, or technical/environmental documents for regulatory review.
- One or more of the following:
- Working knowledge of NRC regulations, requirements, guidance, and industry codes and standards.
- Experience coordinating multi-disciplinary project inputs or managing contract staff contributions.
- Experience working under a quality assurance program such as NQA-1, DOE Order 414.1D, ISO-9000, etc.
But nested lists: we can keep as separate - with sublist.
Then
Benefits
- Competitive compensation packages
- 401k with company match
- Medical, dental, vision plans
- Generous vacation policy, plus holidays
Then Pay
The estimated starting salary range for this role is $179,000 - $203,000 annually less applicable withholdings and deductions, paid on a bi-weekly basis. The actual salary offered may vary based on relevant factors as determined in the Company’s discretion, which may include experience, qualifications, tenure, skill set, availability of qualified candidates, geographic location, certifications held, and other criteria deemed pertinent to the particular role.
We should not include Schedule.
Check for any duplicated lines: we removed EEO etc.
Check that we preserved all substantive info: company description, values, AI-first mindset, trust, etc. We included that in About the role paragraph.
Let's write About the role paragraph:
"The Nuclear Company is the fastest growing AI tech-enabled startup in the nuclear and energy space, pioneering a fleet-scale approach to building the next generation of nuclear reactors. Through our design-once, build-many model, we're accelerating the deployment of safe, reliable, and affordable nuclear energy. We operate with an AI-first mindset. Every employee is expected to leverage AI, technology, and the Nuclear Operating System (NOS) as integral components of their role to improve the quality, speed, and impact of their work. We expect every team member to continuously identify opportunities to automate workflows, enhance decision-making, improve processes, and contribute to the ongoing evolution of NOS as a strategic operating capability that enables The Nuclear Company to scale with excellence. We hire people who are driven by purpose, thrive in ambiguity, and are energized by building what has never been built before. Our team combines intellectual curiosity with high agency, embraces candid feedback and continuous learning, and holds themselves and others to exceptional standards. Our values—Transparency, Responsibility, Unity, Scrappiness, and Tenacity—guide how we hire, collaborate, and make decisions every day. They are not words on a wall; they are the standard by which we operate. Trust is the foundation of our safety culture, fostering intellectual honesty, accountability, and open communication, while our values challenge every team member to execute with urgency, humility, resilience, and an unwavering commitment to our mission."
Then after that we add role description: "The Manager of Licensing supports the planning, development, and execution of licensing and permitting activities for TNC's reactor projects. This role manages day-to-day licensing workflows, coordinates cross-functional inputs for regulatory submissions, and serves as a key interface between licensing staff, project teams, and regulatory authorities. This role requires a solid foundation in nuclear regulatory processes, technical writing, and project coordination, with growing expertise in areas such as nuclear safety, environmental compliance, construction permitting, and regulatory engagement."
We can combine into one paragraph or two. Keep as containing both.
Now responsibilities list: need to extract each bullet from the responsibilities section.
Original responsibilities bullet list:
- Support the development and execution of regulatory strategy, engagement plans, and licensing application development under the direction of the Director of Licensing.
- Leverage AI-powered tools to accelerate regulatory document review, NRC submission preparation, and compliance tracking, reducing manual effort and improving accuracy across licensing applications and correspondence.
- Utilize digital platforms and data analytics to manage licensing schedules, track regulatory commitments, and monitor NRC docket activity in real time, ensuring nothing falls through the cracks during the licensing process.
- Manage assigned portions of regulatory activities (certifications, permits, approvals, and licenses) and track progress against milestones, escalating risks and issues to the Director as needed.
- Coordinate day-to-day activities across licensing disciplines to ensure application inputs are developed on schedule, are technically sound, and are consistent across submissions.
- Review documentation developed by regulatory authorities (e.g., Safety Evaluation Reports, Environmental Impact Statements) for accuracy, adequacy, and consistency, and flag issues to the Director.
- Draft regulatory responses, including responses to Requests for Additional Information (RAIs), and prepare them for submission in accordance with regulatory guidelines.
- Participate in direct interactions with regulators, including supporting regulatory audits, review meetings, and engagement plan execution alongside the Director.
- Monitor the regulatory environment for developments relevant to TNC projects and summarize implications for the licensing team and project stakeholders.
- Supervise and develop licensing staff, including assigning work, reviewing deliverables, and providing technical coaching to junior team members.
- Support development of regulatory budgets, schedules, and resource plans.
- Actively support the safety culture and ensure integration of quality in licensing processes.
We'll list each as
- .
Now Requirements: we need to include all experience/qualifications bullets.
Original Experience section:
Experience
BS in Engineering or Science (e.g., Mechanical, Nuclear, Electrical, Physics, Environmental).
8+ years of relevant engineering, project management, and/or licensing/regulatory affairs experience.
Experience contributing to licensing/regulatory affairs efforts that resulted in regulatory outcomes (e.g., safety evaluations, design approvals, license issuance). Does not require having led these efforts end-to-end, but must demonstrate meaningful ownership of deliverables within them.
Experience participating in NRC, DOE, and/or state-level regulator interactions (written and/or verbal), either as a lead or in a supporting capacity.
Strong technical writing skills, with demonstrated experience drafting regulatory submissions, RAI responses, or technical/environmental documents for regulatory review.
One or more of the following:
Working knowledge of NRC regulations, requirements, guidance, and industry codes and standards.
Experience coordinating multi-disciplinary project inputs or managing contract staff contributions.
Experience working under a quality assurance program such as NQA-1, DOE Order 414.1D, ISO-9000, etc.
Preferred Experience with new reactor licensing (Part 52 or Part 50) or advanced reactor regulatory frameworks.
Familiarity with environmental review processes (NEPA, EIS, EA).
Experience with emergency planning, nuclear security, or safeguards regulatory requirements.
Prior supervisory experience, including performance management and staff development.
Experience with nuclear project finance or commercial nuclear construction/commissioning from a regulatory perspective.
PMP certification or equivalent project management credentials.
We need to separate required vs preferred? The instruction: include sections only when posting has real specific content. We have both required and preferred. Could combine all under Requirements, but we might separate into Requirements and Preferred Qualifications. However allowed headings list includes Qualifications. Could use Qualifications for required, and maybe Skills for preferred? But better to follow the instruction: Use headings for those section names if we have content. We have content for Requirements (maybe we treat as Requirements). We also have Preferred experience etc. Could put under Requirements as well, but we could also add a Qualifications section for required and a Skills section for preferred? However the instruction says prefer a few substantive sections over many thin ones. So maybe combine all into Requirements (or Qualifications). Let's use Requirements heading and include all bullets (both required and preferred). But we need to differentiate? Not required. We'll just list all.
We must not include filler like "Preferred Experience". We'll keep the bullet as is.
We'll structure as:
Requirements
- BS in Engineering or Science (e.g., Mechanical, Nuclear, Electrical, Physics, Environmental).
- 8+ years of relevant engineering, project management, and/or licensing/regulatory affairs experience.
- Experience contributing to licensing/regulatory affairs efforts that resulted in regulatory outcomes (e.g., safety evaluations, design approvals, license issuance). Does not require having led these efforts end-to-end, but must demonstrate meaningful ownership of deliverables within them.
- Experience participating in NRC, DOE, and/or state-level regulator interactions (written and/or verbal), either as a lead or in a supporting capacity.
- Strong technical writing skills, with demonstrated experience drafting regulatory submissions, RAI responses, or technical/environmental documents for regulatory review.
- One or more of the following:
- Working knowledge of NRC regulations, requirements, guidance, and industry codes and standards.
- Experience coordinating multi-disciplinary project inputs or managing contract staff contributions.
- Experience working
- . For responsibilities list, each bullet is a responsibility. For experience requirements, we can list as
- . Benefits list as
- . Pay as
maybe. We must not include markdown code fences. Just raw HTML. Let's craft:
About the role
... company description ... The Manager of Licensing supports ...
ThenResponsibilities
- ... each responsibility ...
Requirements
- BS in Engineering or Science ...
- 8+ years of relevant engineering, project management, and/or licensing/regulatory affairs experience.
- Experience contributing to licensing/regulatory affairs efforts that resulted in regulatory outcomes ...
- Does not require having led these efforts end-to-end, but must demonstrate meaningful ownership of deliverables within them.
- Experience participating in NRC, DOE, and/or state-level regulator interactions (written and/or verbal), either as a lead or in a supporting capacity.
- Strong technical writing skills, with demonstrated experience drafting regulatory submissions, RAI responses, or technical/environmental documents for regulatory review.
- One or more of the following:
- Working knowledge of NRC regulations, requirements, guidance, and industry codes and standards.
- Experience coordinating multi-disciplinary project inputs or managing contract staff contributions.
- Experience working under a quality assurance program such as NQA-1, DOE Order 414.1D, ISO-9000, etc.
- with sublist.
Then
Benefits
- Competitive compensation packages
- 401k with company match
- Medical, dental, vision plans
- Generous vacation policy, plus holidays
Pay
The estimated starting salary range for this role is $179,000 - $203,000 annually less applicable withholdings and deductions, paid on a bi-weekly basis. The actual salary offered may vary based on relevant factors as determined in the Company’s discretion, which may include experience, qualifications, tenure, skill set, availability of qualified candidates, geographic location, certifications held, and other criteria deemed pertinent to the particular role.
We should not include Schedule. Check for any duplicated lines: we removed EEO etc. Check that we preserved all substantive info: company description, values, AI-first mindset, trust, etc. We included that in About the role paragraph. Let's write About the role paragraph: "The Nuclear Company is the fastest growing AI tech-enabled startup in the nuclear and energy space, pioneering a fleet-scale approach to building the next generation of nuclear reactors. Through our design-once, build-many model, we're accelerating the deployment of safe, reliable, and affordable nuclear energy. We operate with an AI-first mindset. Every employee is expected to leverage AI, technology, and the Nuclear Operating System (NOS) as integral components of their role to improve the quality, speed, and impact of their work. We expect every team member to continuously identify opportunities to automate workflows, enhance decision-making, improve processes, and contribute to the ongoing evolution of NOS as a strategic operating capability that enables The Nuclear Company to scale with excellence. We hire people who are driven by purpose, thrive in ambiguity, and are energized by building what has never been built before. Our team combines intellectual curiosity with high agency, embraces candid feedback and continuous learning, and holds themselves and others to exceptional standards. Our values—Transparency, Responsibility, Unity, Scrappiness, and Tenacity—guide how we hire, collaborate, and make decisions every day. They are not words on a wall; they are the standard by which we operate. Trust is the foundation of our safety culture, fostering intellectual honesty, accountability, and open communication, while our values challenge every team member to execute with urgency, humility, resilience, and an unwavering commitment to our mission." Then after that we add role description: "The Manager of Licensing supports the planning, development, and execution of licensing and permitting activities for TNC's reactor projects. This role manages day-to-day licensing workflows, coordinates cross-functional inputs for regulatory submissions, and serves as a key interface between licensing staff, project teams, and regulatory authorities. This role requires a solid foundation in nuclear regulatory processes, technical writing, and project coordination, with growing expertise in areas such as nuclear safety, environmental compliance, construction permitting, and regulatory engagement." We can combine into one paragraph or two. Keep ascontaining both. Now responsibilities list: need to extract each bullet from the responsibilities section. Original responsibilities bullet list: - Support the development and execution of regulatory strategy, engagement plans, and licensing application development under the direction of the Director of Licensing. - Leverage AI-powered tools to accelerate regulatory document review, NRC submission preparation, and compliance tracking, reducing manual effort and improving accuracy across licensing applications and correspondence. - Utilize digital platforms and data analytics to manage licensing schedules, track regulatory commitments, and monitor NRC docket activity in real time, ensuring nothing falls through the cracks during the licensing process. - Manage assigned portions of regulatory activities (certifications, permits, approvals, and licenses) and track progress against milestones, escalating risks and issues to the Director as needed. - Coordinate day-to-day activities across licensing disciplines to ensure application inputs are developed on schedule, are technically sound, and are consistent across submissions. - Review documentation developed by regulatory authorities (e.g., Safety Evaluation Reports, Environmental Impact Statements) for accuracy, adequacy, and consistency, and flag issues to the Director. - Draft regulatory responses, including responses to Requests for Additional Information (RAIs), and prepare them for submission in accordance with regulatory guidelines. - Participate in direct interactions with regulators, including supporting regulatory audits, review meetings, and engagement plan execution alongside the Director. - Monitor the regulatory environment for developments relevant to TNC projects and summarize implications for the licensing team and project stakeholders. - Supervise and develop licensing staff, including assigning work, reviewing deliverables, and providing technical coaching to junior team members. - Support development of regulatory budgets, schedules, and resource plans. - Actively support the safety culture and ensure integration of quality in licensing processes. We'll list each as
- .
Now Requirements: we need to include all experience/qualifications bullets.
Original Experience section:
Experience
BS in Engineering or Science (e.g., Mechanical, Nuclear, Electrical, Physics, Environmental).
8+ years of relevant engineering, project management, and/or licensing/regulatory affairs experience.
Experience contributing to licensing/regulatory affairs efforts that resulted in regulatory outcomes (e.g., safety evaluations, design approvals, license issuance). Does not require having led these efforts end-to-end, but must demonstrate meaningful ownership of deliverables within them.
Experience participating in NRC, DOE, and/or state-level regulator interactions (written and/or verbal), either as a lead or in a supporting capacity.
Strong technical writing skills, with demonstrated experience drafting regulatory submissions, RAI responses, or technical/environmental documents for regulatory review.
One or more of the following:
Working knowledge of NRC regulations, requirements, guidance, and industry codes and standards.
Experience coordinating multi-disciplinary project inputs or managing contract staff contributions.
Experience working under a quality assurance program such as NQA-1, DOE Order 414.1D, ISO-9000, etc.
Preferred Experience with new reactor licensing (Part 52 or Part 50) or advanced reactor regulatory frameworks.
Familiarity with environmental review processes (NEPA, EIS, EA).
Experience with emergency planning, nuclear security, or safeguards regulatory requirements.
Prior supervisory experience, including performance management and staff development.
Experience with nuclear project finance or commercial nuclear construction/commissioning from a regulatory perspective.
PMP certification or equivalent project management credentials.
We need to separate required vs preferred? The instruction: include sections only when posting has real specific content. We have both required and preferred. Could combine all under Requirements, but we might separate into Requirements and Preferred Qualifications. However allowed headings list includes Qualifications. Could use Qualifications for required, and maybe Skills for preferred? But better to follow the instruction: Use headings for those section names if we have content. We have content for Requirements (maybe we treat as Requirements). We also have Preferred experience etc. Could put under Requirements as well, but we could also add a Qualifications section for required and a Skills section for preferred? However the instruction says prefer a few substantive sections over many thin ones. So maybe combine all into Requirements (or Qualifications). Let's use Requirements heading and include all bullets (both required and preferred). But we need to differentiate? Not required. We'll just list all.
We must not include filler like "Preferred Experience". We'll keep the bullet as is.
We'll structure as:
Requirements
- BS in Engineering or Science (e.g., Mechanical, Nuclear, Electrical, Physics, Environmental).
- 8+ years of relevant engineering, project management, and/or licensing/regulatory affairs experience.
- Experience contributing to licensing/regulatory affairs efforts that resulted in regulatory outcomes (e.g., safety evaluations, design approvals, license issuance). Does not require having led these efforts end-to-end, but must demonstrate meaningful ownership of deliverables within them.
- Experience participating in NRC, DOE, and/or state-level regulator interactions (written and/or verbal), either as a lead or in a supporting capacity.
- Strong technical writing skills, with demonstrated experience drafting regulatory submissions, RAI responses, or technical/environmental documents for regulatory review.
- One or more of the following:
- Working knowledge of NRC regulations, requirements, guidance, and industry codes and standards.
- Experience coordinating multi-disciplinary project inputs or managing contract staff contributions.
- Experience working
- . Pay as
- . Benefits list as