Site Operations Coordinator - Moses Lake
Keel Infrastructure · Moses Lake, WA · 1 mo ago
On-siteManagement$85k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to preserve all substantive info, not invent. Remove boilerplate etc.
Let's parse the posting:
- Intro about Keel: "Careers at Keel Keel Infrastructure is a publicly traded energy and digital infrastructure company..." This is about company. Could be "About the role"? Actually "About the role" is for role description. But we have a "Why Keel" section describing company values. Could be "About the role"? Might be better to treat "Why Keel" as about company, but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
We have:
- Role Summary: description of role, responsibilities. That could go under Responsibilities.
- Key Accountabilities: list of duties. That's responsibilities.
- Scope demarcation etc: also responsibilities.
- Qualifications: bullet list: 3–6 years experience, CMMS fluency, detail orientation, customer-service aptitude, growth profile.
- Other: mentions year end cash bonus, LTIP equity grant, WA salary range.
- What We Offer: Competitive salary, bonus and equity opportunities; Comprehensive health and wellness benefits; Retirement savings with company contribution; Employee referral program. That's benefits.
- Pay: salary range given: WA: $85,000 USD - $120,000 USD. Also mention year end cash bonus (prorated) and LTIP equity grant.
- Schedule: not mentioned.
- Skills: maybe we can infer from qualifications: CMMS fluency, detail orientation, customer-service aptitude, written reporting. Could be a Skills section.
We need to avoid filler like "commensurate with experience". Not present.
We must not repeat job title as heading. Job title is "Site Operations Coordinator - Moses Lake". Not to be used as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to output only HTML fragment, no /, no markdown fences.
We need to use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to preserve all substantive info, not invent. Remove boilerplate etc.
Let's parse the posting:
- Intro about Keel: "Careers at Keel Keel Infrastructure is a publicly traded energy and digital infrastructure company..." This is about company. Could be "About the role"? Actually "About the role" is for role description. But we have a "Why Keel" section describing company values. Could be "About the role"? Might be better to treat "Why Keel" as about company, but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
We have:
- Role Summary: description of role, responsibilities. That could go under Responsibilities.
- Key Accountabilities: list of duties. That's responsibilities.
- Scope demarcation etc: also responsibilities.
- Qualifications: bullet list: 3–6 years experience, CMMS fluency, detail orientation, customer-service aptitude, growth profile.
- Other: mentions year end cash bonus, LTIP equity grant, WA salary range.
- What We Offer: Competitive salary, bonus and equity opportunities; Comprehensive health and wellness benefits; Retirement savings with company contribution; Employee referral program. That's benefits.
- Pay: salary range given: WA: $85,000 USD - $120,000 USD. Also mention year end cash bonus (prorated) and LTIP equity grant.
- Schedule: not mentioned.
- Skills: maybe we can infer from qualifications: CMMS fluency, detail orientation, customer-service aptitude, written reporting. Could be a Skills section.
We need to avoid filler like "commensurate with experience". Not present.
We must not repeat job title as heading. Job title is "Site Operations Coordinator - Moses Lake". Not to be used as heading.
We must not put Job ID/requisition numbers as headings (none present).
We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to output only HTML fragment, no /, no markdown fences.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information.
Let's structure:
About the role
maybe include role summary? But we have a "Why Keel" describing company culture. Could be "About the role" includes role summary and why Keel? However "About the role" usually describes the role itself. We have role summary and key accountabilities. So we can put role summary in under About the role. Then Responsibilities section can list key accountabilities as
. But we might double count. Better: About the role: short paragraph describing purpose. Responsibilities: detailed list.
Let's extract role summary paragraph: "The second Keel seat onsite, existing to do what a single-person owner presence cannot: independently verify the FM operator’s work while the Site Director governs and represents, and keep tenant service delivery moving without consuming Director capacity. The role also provides onsite continuity — duty coverage with defined delegated authorities when the Site Director is unavailable. This is a verification and coordination role, not an operations role: the FM operator executes all maintenance and plant operation under its own supervision."
That's good for About the role.
Responsibilities: list of key accountabilities (bullet points). Also maybe include scope demarcation? But that's more clarification. We'll include key accountabilities as list.
Requirements: maybe we can have a section for Requirements (like experience). But we have Qualifications section already. The instructions list both Requirements and Qualifications as possible headings. We need to decide which to use. Since posting has "Qualifications" heading, we should use that. Requirements could be omitted if not distinct. But we could treat the experience and skills as Qualifications. We'll use Qualifications
with list.
Skills: maybe we can separate out skills like CMMS fluency, detail orientation, customer-service aptitude, clear written reporting. But those are already in qualifications. Could combine. To avoid thin sections, we could have Qualifications include both experience and skills. But we have separate headings allowed; we can choose to not create Skills if it's redundant. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine experience and skills into Qualifications.
Benefits: we have "What We Offer" list: Competitive salary, bonus and equity opportunities; Comprehensive health and wellness benefits; Retirement savings with company contribution; Employee referral program. That's benefits.
Pay: we have salary range and bonus/LTIP. So we can have Pay section.
Schedule: not present, so omit.
We must not include placeholder like "commensurate with experience". Not present.
Now we need to ensure we preserve all substantive information: include company description? The intro about Keel: "Careers at Keel 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 not just joining a company, you’re helping build the infrastructure behind the future of compute. Why Keel We’re at the intersection of energy and technology, two industries transforming in real time. The work is complex. The pace is fast. The impact is real. You’ll Be Part Of a Team That Values Ownership— we take responsibility and follow through Collaboration— we work across teams, functions, and borders Curiosity— we ask questions and keep learning Endurance— we build for the long term What It Feels Like To Work Here Fast-moving, high-growth, and hands-onSmart, driven people solving real challenges together Work that directly supports AI and next-generation infrastructureRoom to grow, stretch, and take on more"
This is substantive about company culture and mission. Should we include it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. Where? Could be under About the role? But that is about role, not company. Could add a section "About Keel" but not in allowed headings. However we can still use for section headings only from the list; we cannot create other headings. So we must fit this info into allowed sections. Perhaps we can put it under About the role as a preamble? But About the role is supposed to be about the role, but we can include company description there as part of role context. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections. It doesn't explicitly forbid other headings, but to be safe we should stick to those. So we need to incorporate company description into one of those sections. Probably About the role is appropriate to include both role and company context. We'll include a paragraph about Keel and why Keel, then role summary.
Thus About the role will have multiple paragraphs: company description, why Keel, what it feels like, then role summary.
Now Responsibilities: list of key accountabilities.
Qualifications: list of experience and skills.
Benefits: list from What We Offer.
Pay: salary range, bonus, LTIP.
Now ensure we don't repeat any info.
Let's extract bullet points for responsibilities:
Key Accountabilities (as listed):
- Audit FM operator preventive maintenance: completion verification, spot-witnessing of critical PMs, and work order quality review in the site CMMS.
- Own CMMS data-quality acceptance from the Keel side — the integrity layer that enables central program-level auditing.
- Assemble tenant SLA reporting packages for Site Director delivery; coordinate routine tenant service requests to closure through the operator.
- Administer Keel-side access control and badging approvals; coordinate with the security systems program.
- Provide duty coverage under the site rotation with delegated authorities per the site authority matrix (emergency MOP deviation approval and operator emergency spend authorization to defined thresholds).
- Maintain site records supporting compliance, drills, and audit readiness.
Also note "Explicitly not in scope" list but that's not responsibilities; it's clarifying what not to do. Could be included as note but not required. We'll keep responsibilities as above.
Now Qualifications bullet points:
- 3–6 years in critical facilities, datacenter operations support, service delivery coordination, or QA/QC roles; CMMS fluency required.
- Detail orientation sufficient to audit maintenance records against OEM and procedural standards.
- Customer-service aptitude for tenant-facing coordination; clear written reporting.
- Growth profile: this seat is deliberately structured as succession depth for site leadership.
Also maybe mention "Other: This role includes a year end cash bonus (prorated joining mid-year) and participates in our LTIP (equity grant)" but that's more compensation, goes to Pay.
Now Benefits bullet points:
- Competitive salary, bonus and equity opportunities
- Comprehensive health and wellness benefits
- Retirement savings with company contribution
- Employee referral program
Now Pay: we have salary range: WA: $85,000 USD - $120,000 USD. Also year end cash bonus (prorated) and LTIP equity grant.
We'll put that in Pay section.
Now ensure we don't create Schedule section.
Now produce HTML:
About the role
... paragraphs ...
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
Make sure to preserve all info.
Now craft the About the role paragraph(s). We'll combine multiple sentences into maybe two paragraphs.
Paragraph 1: Company description and Why Keel.
"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 not just joining a company, you’re helping build the infrastructure behind the future of compute. We’re at the intersection of energy and technology, two industries transforming in real time. The work is complex, the pace is fast, and the impact is real. You’ll be part of a team that values ownership, collaboration, curiosity, and endurance."
Paragraph 2: What it feels like to work here.
"What it feels like to work here: fast‑moving, high‑growth, and hands‑on environment with smart, driven people solving real challenges together; work that directly supports AI and next‑generation infrastructure; and room to grow, stretch, and take on more."
Paragraph 3: Role summary.
"The Site Operations Coordinator – Moses Lake serves as the second Keel seat onsite, independently verifying the FM operator’s work while the Site Director governs and represents, and maintaining tenant service delivery without consuming Director capacity. The role provides onsite continuity — duty coverage with defined delegated authorities when the Site Director is unavailable. This is a verification and coordination role, not an operations role; the FM operator executes all maintenance and plant operation under its own supervision."
Now Responsibilities list as above.
Qualifications list as above.
Benefits list as above.
Pay paragraph: "The position offers a salary range of $85,000 USD to $120,000 USD (Washington), plus a year‑end cash bonus (prorated for mid‑year hires
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information. Let's structure:
About the role
maybe include role summary? But we have a "Why Keel" describing company culture. Could be "About the role" includes role summary and why Keel? However "About the role" usually describes the role itself. We have role summary and key accountabilities. So we can put role summary inunder About the role. Then Responsibilities section can list key accountabilities as
- . But we might double count. Better: About the role: short paragraph describing purpose. Responsibilities: detailed list.
Let's extract role summary paragraph: "The second Keel seat onsite, existing to do what a single-person owner presence cannot: independently verify the FM operator’s work while the Site Director governs and represents, and keep tenant service delivery moving without consuming Director capacity. The role also provides onsite continuity — duty coverage with defined delegated authorities when the Site Director is unavailable. This is a verification and coordination role, not an operations role: the FM operator executes all maintenance and plant operation under its own supervision."
That's good for About the role.
Responsibilities: list of key accountabilities (bullet points). Also maybe include scope demarcation? But that's more clarification. We'll include key accountabilities as list.
Requirements: maybe we can have a section for Requirements (like experience). But we have Qualifications section already. The instructions list both Requirements and Qualifications as possible headings. We need to decide which to use. Since posting has "Qualifications" heading, we should use that. Requirements could be omitted if not distinct. But we could treat the experience and skills as Qualifications. We'll use
- ... ...
- ... ...
- ... ...
Qualifications
with list. Skills: maybe we can separate out skills like CMMS fluency, detail orientation, customer-service aptitude, clear written reporting. But those are already in qualifications. Could combine. To avoid thin sections, we could have Qualifications include both experience and skills. But we have separate headings allowed; we can choose to not create Skills if it's redundant. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine experience and skills into Qualifications. Benefits: we have "What We Offer" list: Competitive salary, bonus and equity opportunities; Comprehensive health and wellness benefits; Retirement savings with company contribution; Employee referral program. That's benefits. Pay: we have salary range and bonus/LTIP. So we can have Pay section. Schedule: not present, so omit. We must not include placeholder like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive information: include company description? The intro about Keel: "Careers at Keel 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 not just joining a company, you’re helping build the infrastructure behind the future of compute. Why Keel We’re at the intersection of energy and technology, two industries transforming in real time. The work is complex. The pace is fast. The impact is real. You’ll Be Part Of a Team That Values Ownership— we take responsibility and follow through Collaboration— we work across teams, functions, and borders Curiosity— we ask questions and keep learning Endurance— we build for the long term What It Feels Like To Work Here Fast-moving, high-growth, and hands-onSmart, driven people solving real challenges together Work that directly supports AI and next-generation infrastructureRoom to grow, stretch, and take on more" This is substantive about company culture and mission. Should we include it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. Where? Could be under About the role? But that is about role, not company. Could add a section "About Keel" but not in allowed headings. However we can still usefor section headings only from the list; we cannot create other headings. So we must fit this info into allowed sections. Perhaps we can put it under About the role as a preamble? But About the role is supposed to be about the role, but we can include company description there as part of role context. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections. It doesn't explicitly forbid other headings, but to be safe we should stick to those. So we need to incorporate company description into one of those sections. Probably About the role is appropriate to include both role and company context. We'll include a paragraph about Keel and why Keel, then role summary. Thus About the role will have multiple paragraphs: company description, why Keel, what it feels like, then role summary. Now Responsibilities: list of key accountabilities. Qualifications: list of experience and skills. Benefits: list from What We Offer. Pay: salary range, bonus, LTIP. Now ensure we don't repeat any info. Let's extract bullet points for responsibilities: Key Accountabilities (as listed): - Audit FM operator preventive maintenance: completion verification, spot-witnessing of critical PMs, and work order quality review in the site CMMS. - Own CMMS data-quality acceptance from the Keel side — the integrity layer that enables central program-level auditing. - Assemble tenant SLA reporting packages for Site Director delivery; coordinate routine tenant service requests to closure through the operator. - Administer Keel-side access control and badging approvals; coordinate with the security systems program. - Provide duty coverage under the site rotation with delegated authorities per the site authority matrix (emergency MOP deviation approval and operator emergency spend authorization to defined thresholds). - Maintain site records supporting compliance, drills, and audit readiness. Also note "Explicitly not in scope" list but that's not responsibilities; it's clarifying what not to do. Could be included as note but not required. We'll keep responsibilities as above. Now Qualifications bullet points: - 3–6 years in critical facilities, datacenter operations support, service delivery coordination, or QA/QC roles; CMMS fluency required. - Detail orientation sufficient to audit maintenance records against OEM and procedural standards. - Customer-service aptitude for tenant-facing coordination; clear written reporting. - Growth profile: this seat is deliberately structured as succession depth for site leadership. Also maybe mention "Other: This role includes a year end cash bonus (prorated joining mid-year) and participates in our LTIP (equity grant)" but that's more compensation, goes to Pay. Now Benefits bullet points: - Competitive salary, bonus and equity opportunities - Comprehensive health and wellness benefits - Retirement savings with company contribution - Employee referral program Now Pay: we have salary range: WA: $85,000 USD - $120,000 USD. Also year end cash bonus (prorated) and LTIP equity grant. We'll put that in Pay section. Now ensure we don't create Schedule section. Now produce HTML:
About the role
... paragraphs ...
Responsibilities
Qualifications
Benefits
Pay
...
Make sure to preserve all info. Now craft the About the role paragraph(s). We'll combine multiple sentences into maybe two paragraphs. Paragraph 1: Company description and Why Keel. "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 not just joining a company, you’re helping build the infrastructure behind the future of compute. We’re at the intersection of energy and technology, two industries transforming in real time. The work is complex, the pace is fast, and the impact is real. You’ll be part of a team that values ownership, collaboration, curiosity, and endurance." Paragraph 2: What it feels like to work here. "What it feels like to work here: fast‑moving, high‑growth, and hands‑on environment with smart, driven people solving real challenges together; work that directly supports AI and next‑generation infrastructure; and room to grow, stretch, and take on more." Paragraph 3: Role summary. "The Site Operations Coordinator – Moses Lake serves as the second Keel seat onsite, independently verifying the FM operator’s work while the Site Director governs and represents, and maintaining tenant service delivery without consuming Director capacity. The role provides onsite continuity — duty coverage with defined delegated authorities when the Site Director is unavailable. This is a verification and coordination role, not an operations role; the FM operator executes all maintenance and plant operation under its own supervision." Now Responsibilities list as above. Qualifications list as above. Benefits list as above. Pay paragraph: "The position offers a salary range of $85,000 USD to $120,000 USD (Washington), plus a year‑end cash bonus (prorated for mid‑year hires