Senior Director, Commissioning and Startup

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Equal opportunities statement" etc. Also remove "For information on how Nscale handles candidate personal data..." etc. Also remove "Nscale may offer a competitive benefits package..." etc? Actually benefits are listed earlier: "Highly competitive US compensation package (base + bonus + equity), with performance reviews every 12 months Comprehensive medical, dental, and vision coverage 401(k) retirement plan with company match Generous PTO plus US federal holidays A career-defining opportunity...". That's benefits. Also "Salary Range $160,000—$290,000 USD" is pay. Schedule: location and travel: "Location: Houston, TX. Remote candidates within the US will be considered, with regular travel to project sites (up to 50% during active startup campaigns)." That's schedule? Could be schedule/location. We'll treat as Schedule section. We need sections: About the role (already have a paragraph about role). Responsibilities: list of duties from "What you'll be doing" bullet points. Requirements: maybe from "About you" bullet list? Actually "About you" includes experience requirements. Qualifications: maybe education etc. Skills: maybe technical knowledge. But we need to avoid duplication. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide what content goes where. We have content: - About Nscale (intro) maybe not needed? The instruction: "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." The "About Nscale" is not a required heading; we could include as a paragraph before About the role? But they said "Prefer a few substantive sections over many thin ones." Could include About Nscale as a paragraph under About the role? Actually "About the role" is a heading we must include if we have content. The posting already has "About the role" heading. So we should keep that as

About the role

and then include the paragraph(s) under it (location, description). The "About Nscale" intro could be considered part of About the role? Might be separate but we could include as a paragraph under About the role before responsibilities. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine About Nscale and About the role into one section? But they said use heading About the role for section headings (e.g. About the role, Responsibilities...). So we should have About the role heading and include both the intro about Nscale and role description. Responsibilities: from "What you'll be doing" bullet list. Requirements: maybe from "About you" bullet list (experience, etc). Qualifications: maybe education and PE license. Skills: maybe technical knowledge across mechanical, electrical, controls etc. But we could also combine Requirements and Qualifications. However we need to avoid thin sections. Let's see what we have: About you bullet list: - 15+ years of experience in commissioning, startup, and operations of power generation or comparable heavy process facilities, with senior leadership of at least one major greenfield startup from mechanical completion through commercial operation. - Deep, hands-on technical knowledge across mechanical, electrical, and controls systems, including engine or turbine generation, medium- and high-voltage switchgear and protection, BESS, fuel gas systems, and plant control systems. - Direct experience with energization planning, first fire, performance testing, and reliability demonstrations, ideally including island-mode or behind-the-meter generation. - Strong process safety grounding: PSSR, permit-to-work, MOC, and safe energization practices as working disciplines, not paperwork. - Proven ability to direct EPC contractors and OEM commissioning teams, and to resolve technical disputes on the basis of data and engineering judgment. - Experience engaging in design development and design reviews from an operations and startup perspective. - Track record of building teams, standards, and processes in a fast-scaling environment, and comfort operating with ambiguity while doing so. - Bachelor's degree in Mechanical, Electrical, or Chemical Engineering or a related field; PE license or equivalent professional credential is an advantage. - Willing and able to travel to project sites regularly (up to 50% during active startup campaigns). We could treat the first 7 bullets as Requirements (experience, knowledge, etc). The Bachelor's degree and PE as Qualifications. Travel as Schedule? Actually travel is location/travel. But we already have location/houston and remote etc. Travel could be part of Schedule. Skills: maybe the technical knowledge across mechanical, electrical, controls etc could be Skills. But we already have deep technical knowledge as a requirement. Might be overlapping. Better to follow typical structure: About the role (intro), Responsibilities (what you'll be doing), Requirements (experience needed), Qualifications (education/credentials), Skills (technical competencies), Benefits, Pay, Schedule. Let's extract: About the role: combine About Nscale intro + role description paragraph(s) (location, etc). We'll need to strip boilerplate like "About Nscale At Nscale, we are building..." etc. Keep that. Responsibilities: list from "What you'll be doing" bullet points (the ones after that heading). We'll need to convert each bullet to

. Requirements: from "About you" bullets that are experience/knowledge etc (maybe first 6 bullets). Qualifications: Bachelor's degree etc. Skills: maybe the deep technical knowledge across mechanical, electrical, controls etc? But that's already in requirements. Could instead treat Skills as the technical knowledge list (engine or turbine generation, switchgear, BESS, fuel gas, plant control systems). But we already have that as part of deep technical knowledge. Might be redundant. However we need to avoid thin sections; maybe we can omit Skills if not distinct. But instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But they ask to use headings for those if content exists. We could have Requirements (including experience and education) and Qualifications maybe omitted if thin. But we have education and PE license; that's substantive enough for Qualifications. Skills: maybe we could list specific technical skills: "engine or turbine generation, medium- and high-voltage switchgear and protection, BESS, fuel gas systems, plant control systems, energization planning, first fire, performance testing, reliability demonstrations, process safety (PSSR, permit-to-work, MOC), directing EPC/OEM teams, design reviews, team building." That's a lot; could be Skills. But we already have many of those in Requirements. To avoid duplication, we could assign Requirements as experience/leadership, Qualifications as education/credential, Skills as technical competencies. Let's parse: Experience bullets: - 15+ years experience in commissioning, startup, operations of power generation or comparable heavy process facilities, with senior leadership of at least one major greenfield startup from mechanical completion through commercial operation. - Proven ability to direct EPC contractors and OEM commissioning teams, and to resolve technical disputes on the basis of data and engineering judgment. - Experience engaging in design development and design reviews from an operations and startup perspective. - Track record of building teams, standards, and processes in a fast-scaling environment, and comfort operating with ambiguity while doing so. Technical knowledge bullets: - Deep, hands-on technical knowledge across mechanical, electrical, and controls systems, including engine or turbine generation, medium- and high-voltage switchgear and protection, BESS, fuel gas systems, and plant control systems. - Direct experience with energization planning, first fire, performance testing, and reliability demonstrations, ideally including island-mode or behind-the-meter generation. - Strong process safety grounding: PSSR, permit-to-work, MOC, and safe energization practices as working disciplines, not paperwork. Education bullet: - Bachelor's degree in Mechanical, Electrical, or Chemical Engineering or a related field; PE license or equivalent professional credential is an advantage. Travel bullet: - Willing and able to travel to project sites regularly (up to 50% during active startup campaigns). Thus we can assign: Requirements: experience bullets (leadership, directing EPC, design reviews, building teams). Also maybe include the 15+ years experience. Qualifications: education bullet. Skills: technical knowledge bullets (deep technical knowledge, energization planning, process safety). Could also include travel? No travel goes to Schedule. Schedule: location and travel: "Location: Houston, TX. Remote candidates within the US will be considered, with regular travel to project sites (up to 50% during active startup campaigns)." Benefits: list from "What we can offer you": highly competitive US compensation package (base + bonus + equity), performance reviews every 12 months; comprehensive medical, dental, vision; 401(k) with match; generous PTO plus US federal holidays; career-defining opportunity; human-first approach flexible workplace. Pay: Salary Range $160,000—$290,000 USD. We must not include boilerplate like "Equal opportunities statement", "For information on how Nscale handles candidate personal data", "Nscale may offer a competitive benefits package..." (but we already captured benefits). Also remove "The responsibilities outlined..." etc. Now produce HTML fragment with headings

and content. Structure:

About the role

About Nscale, we are building the infrastructure for the AI revolution. Nscale is developing cutting-edge, sovereign generative AI solutions powered by a new generation of high-performance, sustainable data centers and GPUs built specifically for AI workloads. The rapid growth of artificial intelligence is driving unprecedented global demand for compute and GPU infrastructure. Positioned at the heart of this transformation, Nscale is delivering the platforms that will enable the next decade of innovation. Working closely with the world's most advanced AI technology providers, including Microsoft and NVIDIA, Nscale integrates next-generation compute hardware and GPU clusters across both partner and self-delivered facilities. This is a unique opportunity to join Nscale's journey, play a pivotal role in delivering transformative AI infrastructure, and help shape a company designed to scale rapidly across North America, Europe, and beyond.

Location: Houston, TX. Remote candidates within the US will be considered, with regular travel to project sites (up to 50% during active startup campaigns). We are hiring a Senior Director, Commissioning and Startup to own the transition of Nscale's power generation assets from mechanical completion to commercial operation. Nscale's Power & Energy group develops and delivers multi-gigawatt generation colocated with our data center campuses: large reciprocating engine fleets, fuel cells, battery energy storage systems, high-voltage switchgear and substations, and the fuel gas, water, and controls infrastructure that supports them. Getting these assets from "built" to "running reliably" is one of the highest-leverage phases of the entire program, and this role owns it. This is not a role that starts when construction ends. You will engage early in pre-construction to shape designs for commissionability and startability: influencing system boundaries and turnover sequencing, energization and first-fire logic, tie-in and temporary utility strategy, and testability of performance guarantees. You will bring an operations perspective into the design process, so that decisions made on paper hold up in the field and in year five of operation. You will report to the SVP, Technology (Power) and work across the full asset lifecycle: with engineering and technology teams on one side, operations teams on the other, and EPC partners, permitting consultants, and equipment OEMs in between. For equipment with complex commissioning sequences (generator sets, battery energy storage systems, switchgear and protection systems,