Site Director - Moses Lake (Grant Node)
Bitfarms · Moses Lake, WA · 1 mo ago
On-siteManagement$180k–$220k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description: "Careers at Keel Keel Infrastructure is a publicly traded energy and digital infrastructure company..." That's about company. Then "Why Keel" etc. Then "What It Feels Like to Work Here". Then "What We Offer". Then role summary etc. Then "Key accountabilities". Then "Explicitly not in scope". Then "Scope demarcation". Then "Function". Then "Qualifications". Then salary.
We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must only include sections when posting has real specific content. We need to map content to these headings.
- About the role: could be role summary description. Use that.
- Responsibilities: key accountabilities.
- Requirements: qualifications? Or maybe "Qualifications" heading is separate. The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications separate. Possibly Requirements = mandatory experience, Qualifications = preferred? But we have qualifications section with bullet points. Could split: Requirements = mandatory (10+ years etc). Qualifications = preferred (liquid-cooled experience, temperament). However they also have "Temperament:" etc. We'll decide.
- Skills: maybe not explicitly listed; we could omit if no specific skills.
- Benefits: from "What We Offer": Competitive salary, bonus and equity opportunities; Comprehensive health and wellness benefits; Retirement savings with company contribution; Employee referral program. Also maybe salary is separate Pay.
- Pay: salary range: WA $180,000—$220,000 USD.
- Schedule: not mentioned; omit.
We must not include empty sections.
We need to preserve all substantive info; not invent.
We need to use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must only include sections when posting has real specific content. We need to map content to these headings.
- About the role: could be role summary description. Use that.
- Responsibilities: key accountabilities.
- Requirements: qualifications? Or maybe "Qualifications" heading is separate. The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications separate. Possibly Requirements = mandatory experience, Qualifications = preferred? But we have qualifications section with bullet points. Could split: Requirements = mandatory (10+ years etc). Qualifications = preferred (liquid-cooled experience, temperament). However they also have "Temperament:" etc. We'll decide.
- Skills: maybe not explicitly listed; we could omit if no specific skills.
- Benefits: from "What We Offer": Competitive salary, bonus and equity opportunities; Comprehensive health and wellness benefits; Retirement savings with company contribution; Employee referral program. Also maybe salary is separate Pay.
- Pay: salary range: WA $180,000—$220,000 USD.
- Schedule: not mentioned; omit.
We must not include empty sections.
We need to preserve all substantive info; not invent.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We must not repeat job title as heading; we can omit.
We must not include Job ID etc.
We must strip boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to output only HTML fragment.
Let's craft:
About the role
... role summary ...
Responsibilities
- ... each accountability ...
Requirements
- 10+ years critical facilities operations with at least 3 in a site leadership or owner's representative capacity at a datacenter or equivalent critical environment.
- Direct experience receiving a facility through commissioning into operations — turnover acceptance, operator mobilization, or operational readiness — on at least one greenfield or major-expansion project.
- Demonstrated client-facing or colocation service-delivery experience; able to represent the owner credibly to a sophisticated hyperscale/AI tenant operations team.
- Working knowledge of FM outsourcing structures (MSA/SoW governance, KPI regimes, vendor management) and CMMS-based verification.
Qualifications
- Liquid-cooled or high-density environment experience preferred.
- Temperament: able to hold acceptance and governance positions under schedule pressure — from the delivery organization at the transition gate and from the operator in steady state — while sustaining productive working relationships with both.
Benefits
- Competitive salary, bonus and equity opportunities
- Comprehensive health and wellness benefits
- Retirement savings with company contribution
- Employee referral program
Pay
WA $180,000—$220,000 USD
We should not include Schedule.
Check that we preserved all substantive info: role summary text, key accountabilities, qualifications, benefits, pay. Also we omitted "What It Feels Like to Work Here", "Why Keel", "What We Offer" (we used benefits). Also omitted "Function" and "Scope demarcation" etc. Those are substantive but maybe they duplicate responsibilities. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must include that info somewhere. If we omit those sections, we lose info. We need to incorporate that info into appropriate sections (maybe Responsibilities or About the role). The "Function" section includes a table mapping responsibilities; that's essentially same as key accountabilities but more detailed. We could incorporate that into Responsibilities as additional bullet points. The "Scope demarcation" and "Explicitly not in scope" also important. We could add bullet points under Responsibilities for what is NOT in scope? Might be better to add a separate section like "Exclusions" but not allowed headings. Could incorporate into Responsibilities as notes.
We need to preserve all substantive info; we can add bullet points under Responsibilities covering the function table and scope demarcation and explicit not in scope.
Let's extract:
From "Function" table: This role (Keel Ops) owns Counterpart owns Commissioning & handover Operations acceptance at the transition gate; operations input to IST scenarios; readiness verification (drills, spares, training competence) Keel delivery org (Director, Cx & QA) owns the Cx program, CxA management, L4/L5 execution, turnover documentation, and delivery attestation Operator mobilization Acceptance gate: CMMS population quality, PM seeding, shift validation, mobilization milestones before steady-state billing FM operator mobilization/transition lead recruits, onboards, and trains operator staff and stands up its processes; delivery org coordinates training delivery Plant operation Governance, verification, and acceptance; authority to escalate and to approve/deny changes FM operator site leadership (site/critical facilities manager) runs 24x7 operations, shift coverage, and staff supervision Incident response Incident command interface, tenant/executive communications, post-incident review acceptance The FM operator executes emergency response per EOPs; operator site leadership manages first-line command of its crew Maintenance program Approval of windows, deviations, and deferrals; selective witnessing; KPI verification The FM operator chief engineer / site team plans and executes the PM program and manages subcontracted LTSA vendors Tenant interface Primary tenant POC; SLA reporting delivery; QBRs; escalations The FM operator has no direct tenant relationship except as technically directed through Keel-approved channels Site staffing Verification that deployed operator staffing matches contracted levels (feeds commercial true-up) The FM operator hires, schedules, trains, and manages its site organization
That's a lot; many of these are already covered in key accountabilities but some are extra like "operations input to IST scenarios", "readiness verification (drills, spares, training competence)", "Plant operation Governance, verification, and acceptance; authority to escalate and to approve/deny changes", "Incident response...", "Maintenance program Approval of windows, deviations, and deferrals; selective witnessing; KPI verification", "Tenant interface Primary tenant POC; SLA reporting delivery; QBRs; escalations", "Site staffing Verification that deployed operator staffing matches contracted levels". We should incorporate these as bullet points under Responsibilities.
Also "Explicitly not in scope" list: Commissioning program ownership, test script development, CxA management, L4/L5 test execution, and construction quality assurance (Director, Data Center Commissioning & Quality Assurance scope); directing FM operator technicians or shift staff (direction flows exclusively through FM operator site leadership); executing maintenance, operations, or vendor work; FM invoice adjudication and contract commercial negotiation (FM Commercial function); lease negotiation (leasing team, with Ops review input). We could add as bullet points under Responsibilities maybe with a note "Not in scope:" but still preserve.
"Scope demarcation — FM operations provider and Keel delivery organization" basically repeats the function table.
Thus we can create Responsibilities bullets covering all these.
We also need to keep the "What It Feels Like to Work Here" and "Why Keel" etc. Those are cultural description; could go under About the role or maybe a separate section like "About Keel" but not allowed headings. We could incorporate into About the role paragraph.
Thus About the role paragraph can include company description, why Keel, what it feels like, what we offer (benefits) but we already have Benefits section. Might duplicate. Better to keep About the role as role summary and company overview; Benefits separate.
Let's craft About the role paragraph: combine company description, why Keel, what it feels like, what we offer (maybe brief). But we must not repeat benefits details that we will list in Benefits section; we can summarize.
We'll write:
Keel Infrastructure is a publicly traded energy and digital infrastructure company that develops and owns data centers and power assets across North America. At Keel, you're helping build the infrastructure behind the future of compute. The company sits at the intersection of energy and technology, offering fast‑moving, high‑growth, hands‑on work with smart, driven people solving real challenges that directly support AI and next‑generation infrastructure, with room to grow and take on more. Keel offers a competitive salary, bonus and equity opportunities, comprehensive health and wellness benefits, retirement savings with company contribution, and an employee referral program.
That covers company description, why Keel, what it feels like, what we offer.
Now Responsibilities: we need to list all duties from role summary, key accountabilities, function table, etc.
Let's compile bullet list:
- Hold operations acceptance authority at the formal transition-to-operations gate, as dual signatory alongside the Director of Data Center Commissioning & Quality Assurance: delivery attestation by the delivery organization; operational readiness acceptance by this role, on documented evidence.
- Gate FM operator mobilization: ensure CMMS population quality using turnover asset data, PM schedule seeding, shift structure validation, badge and access provisioning, and acceptance of mobilization milestones prior to steady-state operations and billing.
- Verify operational readiness before energization: validate MOPs/SOPs/EOPs through witnessed tabletop and live drills; independently verify FM operator training competence (beyond training delivery); confirm critical spares on shelf against the approved list, including long-lead liquid-cooling wet-side spares.
- Contribute operations scenarios (including thermal transient and CDU failure modes) to the integrated systems test scripts owned by the delivery organization.
- Govern FM operator performance in steady state through independent verification against the Keel-owned KPI framework rather than operator self-reporting; convert findings into corrective action through the operator's site leadership and, where commercial, through the FM Commercial function.
- Hold change management authority: approve maintenance windows, MOP deviations, deferral requests, and configuration changes above operator-delegated thresholds.
- Serve as Keel incident command interface during abnormal events; own tenant and executive communications; conduct post-incident review acceptance.
- Own the anchor tenant relationship: deliver SLA reporting, serve as escalation interface to the tenant operations team, conduct quarterly business reviews, and maintain the working relationship that protects occupancy economics.
- Maintain the site duty rotation and delegated-authority matrix with the Site Operations Coordinator; ensure the tenant holds a documented escalation path at all times.
- Supervise the Site Operations Coordinator.
- Provide operations input to integrated system test scenarios and readiness verification (drills, spares, training competence).
- Govern plant operation: verification, acceptance, authority to escalate and to approve/deny changes.
- Manage incident response: act as incident command interface, handle tenant/executive communications, accept post-incident reviews.
- Oversee maintenance program: approve windows, deviations, and deferrals; perform selective witnessing; verify KPI compliance.
- Serve as primary tenant point of contact: deliver SLA reporting, conduct QBRs, handle escalations.
- Verify deployed operator staffing matches contracted levels (feeds commercial true-up).
- Not in scope: commissioning program ownership, test script development, CxA management, L4/L5 test execution, construction quality assurance; directing FM operator technicians or
for prose. We must not repeat job title as heading; we can omit. We must not include Job ID etc. We must strip boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment. Let's craft:
About the role
... role summary ...
Responsibilities
- ... each accountability ...
Requirements
- 10+ years critical facilities operations with at least 3 in a site leadership or owner's representative capacity at a datacenter or equivalent critical environment.
- Direct experience receiving a facility through commissioning into operations — turnover acceptance, operator mobilization, or operational readiness — on at least one greenfield or major-expansion project.
- Demonstrated client-facing or colocation service-delivery experience; able to represent the owner credibly to a sophisticated hyperscale/AI tenant operations team.
- Working knowledge of FM outsourcing structures (MSA/SoW governance, KPI regimes, vendor management) and CMMS-based verification.
Qualifications
- Liquid-cooled or high-density environment experience preferred.
- Temperament: able to hold acceptance and governance positions under schedule pressure — from the delivery organization at the transition gate and from the operator in steady state — while sustaining productive working relationships with both.
Benefits
- Competitive salary, bonus and equity opportunities
- Comprehensive health and wellness benefits
- Retirement savings with company contribution
- Employee referral program
Pay
WA $180,000—$220,000 USD
We should not include Schedule. Check that we preserved all substantive info: role summary text, key accountabilities, qualifications, benefits, pay. Also we omitted "What It Feels Like to Work Here", "Why Keel", "What We Offer" (we used benefits). Also omitted "Function" and "Scope demarcation" etc. Those are substantive but maybe they duplicate responsibilities. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must include that info somewhere. If we omit those sections, we lose info. We need to incorporate that info into appropriate sections (maybe Responsibilities or About the role). The "Function" section includes a table mapping responsibilities; that's essentially same as key accountabilities but more detailed. We could incorporate that into Responsibilities as additional bullet points. The "Scope demarcation" and "Explicitly not in scope" also important. We could add bullet points under Responsibilities for what is NOT in scope? Might be better to add a separate section like "Exclusions" but not allowed headings. Could incorporate into Responsibilities as notes. We need to preserve all substantive info; we can add bullet points under Responsibilities covering the function table and scope demarcation and explicit not in scope. Let's extract: From "Function" table: This role (Keel Ops) owns Counterpart owns Commissioning & handover Operations acceptance at the transition gate; operations input to IST scenarios; readiness verification (drills, spares, training competence) Keel delivery org (Director, Cx & QA) owns the Cx program, CxA management, L4/L5 execution, turnover documentation, and delivery attestation Operator mobilization Acceptance gate: CMMS population quality, PM seeding, shift validation, mobilization milestones before steady-state billing FM operator mobilization/transition lead recruits, onboards, and trains operator staff and stands up its processes; delivery org coordinates training delivery Plant operation Governance, verification, and acceptance; authority to escalate and to approve/deny changes FM operator site leadership (site/critical facilities manager) runs 24x7 operations, shift coverage, and staff supervision Incident response Incident command interface, tenant/executive communications, post-incident review acceptance The FM operator executes emergency response per EOPs; operator site leadership manages first-line command of its crew Maintenance program Approval of windows, deviations, and deferrals; selective witnessing; KPI verification The FM operator chief engineer / site team plans and executes the PM program and manages subcontracted LTSA vendors Tenant interface Primary tenant POC; SLA reporting delivery; QBRs; escalations The FM operator has no direct tenant relationship except as technically directed through Keel-approved channels Site staffing Verification that deployed operator staffing matches contracted levels (feeds commercial true-up) The FM operator hires, schedules, trains, and manages its site organization That's a lot; many of these are already covered in key accountabilities but some are extra like "operations input to IST scenarios", "readiness verification (drills, spares, training competence)", "Plant operation Governance, verification, and acceptance; authority to escalate and to approve/deny changes", "Incident response...", "Maintenance program Approval of windows, deviations, and deferrals; selective witnessing; KPI verification", "Tenant interface Primary tenant POC; SLA reporting delivery; QBRs; escalations", "Site staffing Verification that deployed operator staffing matches contracted levels". We should incorporate these as bullet points under Responsibilities. Also "Explicitly not in scope" list: Commissioning program ownership, test script development, CxA management, L4/L5 test execution, and construction quality assurance (Director, Data Center Commissioning & Quality Assurance scope); directing FM operator technicians or shift staff (direction flows exclusively through FM operator site leadership); executing maintenance, operations, or vendor work; FM invoice adjudication and contract commercial negotiation (FM Commercial function); lease negotiation (leasing team, with Ops review input). We could add as bullet points under Responsibilities maybe with a note "Not in scope:" but still preserve. "Scope demarcation — FM operations provider and Keel delivery organization" basically repeats the function table. Thus we can create Responsibilities bullets covering all these. We also need to keep the "What It Feels Like to Work Here" and "Why Keel" etc. Those are cultural description; could go under About the role or maybe a separate section like "About Keel" but not allowed headings. We could incorporate into About the role paragraph. Thus About the role paragraph can include company description, why Keel, what it feels like, what we offer (benefits) but we already have Benefits section. Might duplicate. Better to keep About the role as role summary and company overview; Benefits separate. Let's craft About the role paragraph: combine company description, why Keel, what it feels like, what we offer (maybe brief). But we must not repeat benefits details that we will list in Benefits section; we can summarize. We'll write:Keel Infrastructure is a publicly traded energy and digital infrastructure company that develops and owns data centers and power assets across North America. At Keel, you're helping build the infrastructure behind the future of compute. The company sits at the intersection of energy and technology, offering fast‑moving, high‑growth, hands‑on work with smart, driven people solving real challenges that directly support AI and next‑generation infrastructure, with room to grow and take on more. Keel offers a competitive salary, bonus and equity opportunities, comprehensive health and wellness benefits, retirement savings with company contribution, and an employee referral program.
That covers company description, why Keel, what it feels like, what we offer. Now Responsibilities: we need to list all duties from role summary, key accountabilities, function table, etc. Let's compile bullet list: - Hold operations acceptance authority at the formal transition-to-operations gate, as dual signatory alongside the Director of Data Center Commissioning & Quality Assurance: delivery attestation by the delivery organization; operational readiness acceptance by this role, on documented evidence. - Gate FM operator mobilization: ensure CMMS population quality using turnover asset data, PM schedule seeding, shift structure validation, badge and access provisioning, and acceptance of mobilization milestones prior to steady-state operations and billing. - Verify operational readiness before energization: validate MOPs/SOPs/EOPs through witnessed tabletop and live drills; independently verify FM operator training competence (beyond training delivery); confirm critical spares on shelf against the approved list, including long-lead liquid-cooling wet-side spares. - Contribute operations scenarios (including thermal transient and CDU failure modes) to the integrated systems test scripts owned by the delivery organization. - Govern FM operator performance in steady state through independent verification against the Keel-owned KPI framework rather than operator self-reporting; convert findings into corrective action through the operator's site leadership and, where commercial, through the FM Commercial function. - Hold change management authority: approve maintenance windows, MOP deviations, deferral requests, and configuration changes above operator-delegated thresholds. - Serve as Keel incident command interface during abnormal events; own tenant and executive communications; conduct post-incident review acceptance. - Own the anchor tenant relationship: deliver SLA reporting, serve as escalation interface to the tenant operations team, conduct quarterly business reviews, and maintain the working relationship that protects occupancy economics. - Maintain the site duty rotation and delegated-authority matrix with the Site Operations Coordinator; ensure the tenant holds a documented escalation path at all times. - Supervise the Site Operations Coordinator. - Provide operations input to integrated system test scenarios and readiness verification (drills, spares, training competence). - Govern plant operation: verification, acceptance, authority to escalate and to approve/deny changes. - Manage incident response: act as incident command interface, handle tenant/executive communications, accept post-incident reviews. - Oversee maintenance program: approve windows, deviations, and deferrals; perform selective witnessing; verify KPI compliance. - Serve as primary tenant point of contact: deliver SLA reporting, conduct QBRs, handle escalations. - Verify deployed operator staffing matches contracted levels (feeds commercial true-up). - Not in scope: commissioning program ownership, test script development, CxA management, L4/L5 test execution, construction quality assurance; directing FM operator technicians or