Energy Marshal, Multi-Site

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Fluidstack", "How We Operate", "The HSE Team", "Examples of key problems the team is working on", "Role Scope", "What We're Looking For". Also compensation range given. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can only include sections when posting has real specific content. We need to map content to appropriate headings. We have: - About Fluidstack: description of company mission. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Fluidstack" which is about company. Could map to "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use those headings if appropriate. We need to decide which sections to include based on content. We have content about company mission, how we operate, HSE team examples, role scope, what we're looking for (requirements/qualifications), compensation range. Thus we can have sections: - About the role? Could combine company description and how we operate? Might be better to have "About the role" for role scope and responsibilities. But we have separate "Role Scope" which is responsibilities. So we can have:

About the role

maybe containing description of role scope? But we also have "How We Operate" which is company culture; could be part of "About the role" or maybe "About Fluidstack" not needed. We need to avoid headings with filler. We must include only sections with real content. Potential sections: - About the role (could include role scope and responsibilities) - Responsibilities (maybe separate) - Requirements / Qualifications (what we're looking for) - Pay (compensation range) - Benefits? Not mentioned. - Schedule? Not mentioned. We must not invent sections like Benefits or Schedule if not present. Thus we can have:

About the role

with paragraph summarizing role scope? But we also have detailed responsibilities list. Could put responsibilities under

Responsibilities

with

. Similarly, qualifications under

Qualifications

with
. Pay under

Pay

with

. We also have "How We Operate" which is company culture; could be part of "About the role" or maybe a separate section like "About Fluidstack"? Not in allowed headings but we could still use

About Fluidstack

? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could still use other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. Safer to stick to those. Thus we need to map content to those headings. We have: - About the role: could include company mission and how we operate? Might be okay. - Responsibilities: role scope details. - Requirements: what we're looking for (experience, credentials). - Qualifications: maybe same as requirements? Could combine but we need to avoid duplication. Could treat "What We're Looking For" as Requirements, and maybe also include "Bonus:" as Qualifications? But better to have one section for Requirements/Qualifications. We could have:

About the role

Fluidstack exists to make humanity more free... (company description) ... How We Operate: Be a barrel... (culture).

Responsibilities

list of role scope items.

Requirements

list of what we're looking for (mandatory) plus maybe bonus as separate? Could include bonus as part of same list but note it's bonus.

Pay

Compensation Range: $199K - $247K

We should not include Benefits or Schedule. We must preserve all substantive information, not invent or summarize away detail. Need to keep details like specific tasks: "Own hazardous energy control across multiple concurrent gigawatt-scale data center builds, from first temporary power through construction, Level 1 to Level 5 commissioning, and handoff to operations." etc. We need to convert bullet points into
• . We must remove boilerplate: EEO, equal opportunity, application instructions, confirmation email, etc. Also remove "We are committed to pay equity and transparency." maybe keep? It's not boilerplate? It's a statement about pay equity; could be considered part of Pay section? Might be okay to keep as part of Pay paragraph. But it's not required; we can keep if not boilerplate. It's a statement about pay equity; not required to remove. However it's generic; but it's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. It's about pay equity, could stay. We must not include "Fluidstack is an Equal Employment Opportunity Employer..." etc. Remove that. Also remove "You will receive a confirmation email..." etc. Now craft HTML. Let's extract sections. About Fluidstack paragraph: "We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!" How We Operate: "Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role. Insane urgency. We drive everything forward as fast as possible. Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins. Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward. Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world." We can combine these into About the role paragraph. Now Role Scope bullet points (list): - Own hazardous energy control across multiple concurrent gigawatt-scale data center builds, from first temporary power through construction, Level 1 to Level 5 commissioning, and handoff to operations. - Write, review, and approve every switching plan, LOTO procedure, energization sequence, and zero-energy verification before medium-voltage or low-voltage gear is landed, tested, or turned on. - Run the pre-energization and energization kick-off meetings, and hold sole authority to authorize, pause, or stop any energization, isolation, or restoration across the GC, electrical contractors, commissioning agents, and the utility. - Audit the electrical safety program in the field: JHAs, energized work permits, boundary controls, PPE, arc flash labeling, and the gap between the written control and what the crew actually does at the gear. - Create and run the Kirk key program: collect, log, and control every Kirk key as switchgear, transformers, and generators are delivered to site, and turn the full key inventory over to operations at handoff. - Maintain the tamper seal program on all energized and isolated equipment, and act as the only person who can authorize breaking a tamper seal. - Manage the contract site-level Energy Marshals at every active campus: select and onboard them, set the standard they work to, audit their switching plans and field practice, and remove anyone who does not meet it. - Build the multi-site Energy Marshal standard, including the templates, energization tracker, and training, so a new campus stands up its energization program in days rather than months. Now What We're Looking For bullet points (mandatory): - You've performed as an Energy Marshal or Controlling Energy Marshal for a minimum of five years on data center or mission-critical construction, and have run energizations end to end on more than one site at a time. - You hold current NFPA 70E qualified-person training and a recognized electrical safety credential (NFPA CESCP or CESW), plus OSHA 30 Construction and current First Aid/CPR/AED. - You've personally written and approved switching orders and LOTO procedures on MV (above 1000V) and LV distribution: utility service, MV switchgear, transformers, generators, UPS, PDUs, and busway. - You've stopped an energization when the paperwork was signed but the field didn't match it, and you can walk through the call and how you got the work restarted safely. - You've directed other Energy Marshals or electrical safety leads across more than one site, held them to a single standard, and replaced one who fell short of it. - You've coordinated GC, electrical subcontractor, commissioning agent, utility, and owner operations teams on a live campus where construction and energized systems share walls. - You've run a Kirk key interlock or tamper seal program on live gear and can account for every key and seal from delivery through turnover. - You keep the energization log, permit records, and isolation registers current enough that an auditor or incident investigation can reconstruct any switching event on any site. - You explain arc flash boundaries, incident energy, and approach distances to an apprentice and to a VP with the same clarity. Bonus: - Electrician licensure (journeyman or master). - Utility safety leadership (CUSP). - Commissioning credentials (CxA, QCxP). - Arc flash and coordination study review (SKM, ETAP). - Behind-the-meter generation and multi-state utility interconnection. Now Pay: "Compensation Range: $199K - $247K" We may also include the pay equity statement: "We are committed to pay equity and transparency." Could be included in Pay paragraph. Now produce HTML. We'll wrap each section in

  and then content. For About the role:

  containing both Fluidstack description and How We Operate? Could be two paragraphs. Let's do:

  About the role

  Fluidstack exists to make humanity more free. ... (the long paragraph).

  How We Operate: Be a barrel. Full autonomy.... (the culture paragraph).

  Then Responsibilities
  with each bullet. Then Requirements
  with mandatory items. Could also include bonus as a note? Maybe add a

  Bonus: ...

  inside Requirements? But better to keep as part of Requirements but note bonus. Could add a

  Bonus qualifications:

  then
  . However that would be a separate sub-section but still under Requirements heading. That's okay. Then Pay

  Pay

  Compensation Range: $199K - $247K. We are committed to pay equity and transparency.

  Make sure not to include any extra boilerplate. Now produce final HTML. Check for any leftover boilerplate: removed EEO, confirmation email, etc. Now