Deployment Project Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions. The posting includes location, travel, responsibilities list, minimum qualifications, bonus qualifications, competencies (list of traits), compensation (salary range, benefits), travel requirements (Oklo travel requirements), about Oklo description, values, etc. We need to decide which sections to include. We have content for: - About the role: The initial paragraph describing role: "The Deployment Project Manager is a pivotal, execution-focused role responsible for advancing Oklo’s mission..." That's about the role. Could be placed under About the role. - Responsibilities: The bullet list starting "Specific responsibilities may include:" with many items. That's responsibilities. - Requirements: Minimum Qualifications list. - Qualifications: Bonus Qualifications list. - Skills: Could be competencies list (traits) or maybe "Competencies" section. The posting includes "CompetenciesWe are looking for a Deployment Project Manager that is:" then a list of traits. That could be Skills. - Benefits: The posting mentions "Oklo offers flexible time off, equity, bonuses, competitive pay, 401(k), health insurance (with employer contribution), HSA, FSA, flexible work hours, wellness credits, and other benefits." Also maybe travel requirements? But travel is separate. - Pay: Salary range: "$100,000-$160,000" - Schedule: Travel requirements: "Location: Remote, with 25%–40% travel required" and "About Oklo travel requirements: Oklo requires remote employees to travel to headquarters (Santa Clara, CA) twice a quarter annually, based on business or team needs, including attendance at team meetings, off-sites, and other company events or gatherings. For the first two weeks of onboarding, employees are required to be in person at headquarters in Santa Clara, CA." That's schedule/travel. We also have "About Oklo Inc." description and values etc. Might be considered "About the company" but not requested. We could include under About the role? Probably not needed. The instruction: "Prefer a few substantive sections over many thin ones." We could combine some. But we need to follow headings list. We can include sections that have content. We must not include headings with filler like "commensurate with experience". We have real content. Thus produce:

About the role

... (the paragraph about role)

Responsibilities

• ... each responsibility

Requirements

• ... minimum qualifications

Qualifications

• ... bonus qualifications

Skills

• ... competencies list

Benefits

• ... benefits list

Pay

Salary: $100,000-$160,000

Schedule

Location: Remote, with 25%–40% travel required. Oklo requires remote employees to travel to headquarters (Santa Clara, CA) twice a quarter annually, based on business or team needs, including attendance at team meetings, off-sites, and other company events or gatherings. For the first two weeks of onboarding, employees are required to be in person at headquarters in Santa Clara, CA.

We need to ensure we preserve all substantive info. Let's extract each piece. About the role paragraph: "The Deployment Project Manager is a pivotal, execution-focused role responsible for advancing Oklo’s mission to deliver clean, affordable, and reliable energy. This individual owns the end-to-end delivery of one or more highly complex powerhouse projects, from design integration and site development through construction, startup, commissioning, and turnover to operations. These multi-year, non-recurring projects include significant first-of-a-kind scope, substantial commercial value, evolving risks, and complex dependencies across internal teams, external partners, regulators, and other key stakeholders. The Deployment Project Manager serves as the central point of coordination, driving integrated planning, decision-making, risk management, and clear communication among project teams, executive leadership, and external parties. Success in this role requires a strategic and hands-on leader with a startup mindset - someone who can bring structure to ambiguity, operate effectively in a resource-constrained environment, and maintain momentum, accountability, and alignment throughout the full project lifecycle." That's the paragraph before location. We'll put that. Responsibilities list: after "Specific responsibilities may include:" we have a list of items each starting with a verb. Let's capture them: - Lead end-to-end execution of powerhouse facility deployments from design through startup and turnover to operations. - Support and maintain integrated project plans, schedules, milestones, and execution tools to monitor progress and drive delivery. - Identify, manage, and escalate risks, issues, dependencies, and changes to protect critical path, licensing, regulatory, and commercial objectives. - Lead project governance routines, including status reviews, stage-gate reviews, and executive reporting. - Manage project scope, risks, issues, and dependencies while proactively identifying and implementing mitigation strategies. - Communicate project status, recommendations, and strategic insights to stakeholders ranging from project teams to executive leadership. - Support permitting, licensing, facility modifications, equipment installations, and infrastructure upgrade projects. - Oversee contractor performance, procurement activities, material sourcing, and project deliverables. - Serve as the primary point of coordination among internal teams, customers, contractors, vendors, and other external stakeholders. - Contribute to technical strategy, execution planning, and continuous improvement initiatives that support organizational goals. - Ensure projects are executed safely, efficiently, and in compliance with applicable quality, regulatory, and operational requirements. We'll put each as

. Requirements (Minimum Qualifications): list: - Bachelor’s degree in Engineering, Project Management, Construction Management, Nuclear Engineering, Business, or a related technical discipline. - Minimum of 5 years of project management experience leading complex technical, engineering, construction, manufacturing, or operational projects. - Experience managing project scope, schedules, budgets, risks, milestones, and cross-functional dependencies. - Demonstrated ability to lead teams, resolve blockers, and communicate effectively with technical and business stakeholders. - Strong organizational, analytical, and problem-solving skills. - Ability to operate with agility and sound judgment in a fast-moving, evolving organization. - Proficiency with project planning, scheduling, and collaboration tools. We'll put each as

. Qualifications (Bonus Qualifications): list: - Nuclear experience in design, construction, commissioning, or operations - PMP certification is strongly preferred. - Experience managing contractor-driven projects, capital projects, facility upgrades, or equipment installation efforts. - Familiarity with quality assurance, configuration management, permitting, or regulatory compliance processes. We'll put each as

. Skills (Competencies): The list after "CompetenciesWe are looking for a Deployment Project Manager that is:" includes many traits separated by line breaks. Let's extract: - Passionate about advancing the deployment of next-generation powerhouse facilities - Creative when pursuing tasks in resource constrained environments - You’re not afraid to roll up your sleeves and deliver - You see how the pieces connect and can manage interfaces - You turn ambiguity into momentum - Eager to work on a dynamic team, receive constructive feedback, and grow with us - An active and effective communicator of priorities - Able to recognize, accept, and manage risk - Passionate about Oklo's mission to design and deploy advanced fission power plants to provide clean, reliable, and affordable energy - Willing to think differently and do things in new ways - Comfortable in a fast-paced, highly iterative startup environment - Excited to think creatively, critically, and reflectively about the problems they are solving, while not leaning only on what has been done before Then there is a "Who you are:" section with more traits: "A startup person: ..." etc. That seems also part of competencies/skills. Might be included. The instruction: "Prefer a few substantive sections over many thin ones." Could combine all traits under Skills. Let's include all traits from both "Competencies" and "Who you are:" as list items. Who you are: list: - A startup person: You aren't driven by titles or hierarchy, and prefer efficiency to excess process. You don't need or expect to have a lot of guidance but you enjoy working in a fast-paced team. If you prefer the culture and feel of a large organization, that is great, but you likely won’t enjoy working with us! There is plenty of important work and plenty of good opportunities with organizations like that. - Motivated: You are self-motivated. You bring an enthusiasm to the team, and imbue a sense of passion that goes beyond clocking in and clocking out. This isn’t about a fake or arbitrary “pieces of flair” mentality or lack of work-life balance! It is about being a part of the vision and feeling a part of reaching team goals. - A team-player: Oklo genuinely is a team. We aren’t about taking credit for ourselves, and we aren’t about pushing blame to others. We do incredible things because we work as a team. - An excellent communicator: We need a person who is not only technically competent but also a clear and upbeat communicator. - Creative: Being creative means that when things fall outside clear scopes or processes or problems arise without clear solutions, you are able to identify it as well as invent ways to solve a problem or fill a need without micromanagement. The successful person in this job will not only be creative, but also enjoy being creative and solving open-ended problems which may change day-by-day. - Detail-oriented: This focus is a big part of excellence, consistency, and quality. Excellent grammar and spelling matter for both good communication as well as the image of the company that we put forward. We'll include these as list items as well. Benefits: list from "Oklo offers flexible time off, equity, bonuses, competitive pay, 401(k), health insurance (with employer contribution), HSA, FSA, flexible work hours, wellness credits, and other benefits." We'll split into items. Pay: Salary range. Schedule: location and travel details. We must not include boilerplate like "About Oklo Inc.", values, recruitment fraud disclaimer, etc. Also must not include "This position may involve access to information subject to U.S. export control laws..." That's substantive? It's a legal requirement; maybe we should keep? It's not in the requested sections but could be placed under Requirements? It's a eligibility condition. Might be considered a requirement. The instruction: preserve ALL substantive information. So we should include that somewhere. Could add a paragraph under Requirements or a separate section like "Eligibility". But we only have allowed headings list; we could add a

under Requirements after the list. Or we could add a short paragraph under Requirements. Since we cannot create new headings not in list, we can embed it as a paragraph within Requirements section after the list. That's acceptable. Also "About Oklo Inc.: Oklo Inc. is developing fast fission power plants..." That's company description; could be placed under About the role? Might be considered extra but substantive. Could add a paragraph under About the role after the role description. That preserves info. Also values (#CHOP: Oklo’s Values ...) could be omitted? It's substantive but not requested headings. Could add under About the role as well. But we must avoid too many thin sections. Probably okay to include as a paragraph under About the role. Recruitment Fraud Disclaimer: also substantive but could be placed as a paragraph at end maybe under a generic "Notes"? Not in headings. Could add as a paragraph under Requirements? Might be odd. Perhaps