Director, Operations Programs & Standards

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to extract content from posting. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive info. Let's parse posting: - 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 What We Offer Competitive salary, bonus and equity opportunities Comprehensive health and wellness benefitsRetirement savings with company contributionEmployee referral program" That's general company description; could be "About the role"? Actually "About the role" is more about the specific job. The intro is about company; maybe we can put under "About the role" or maybe we can omit because it's generic? But we need to preserve all substantive information. The instruction: "Prefer a few substantive sections over many thin ones." We could combine company overview into "About the role" or maybe a separate "About Keel" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those. Thus: - About the role: could include company description and why Keel, what it feels like, what we offer (benefits). But Benefits separate. Better: About the role: summary of role, purpose, context. Responsibilities: key accountabilities. Requirements: qualifications? Actually Qualifications separate. Requirements maybe similar to qualifications but we can treat Qualifications as required experience/skills. Skills maybe not present. Benefits: what we offer (competitive salary, bonus, equity, health, retirement, referral). Pay: salary range. Schedule: hybrid remote (3 days per week in office). Also maybe location. We must not repeat job title as heading. Job ID not present. We must not include placeholder text like "commensurate with experience". Not present. We must not include boilerplate like EEO. Now extract specifics: Role: Director, Operations Programs & Standards Role Summary: Owns the Keel operational standard across the entire site portfolio — the templates, acceptance criteria, KPI definitions, and document governance that every site and every FM operator performs against, beginning with Moses Lake (Grant Node) and extending to Sharon and the PA/Canada pipeline. The FM operator drafts, populates, and executes within contracted scope; this role controls what “acceptable” means and keeps the program standard owned by Keel rather than proprietary to any single operator. This role is the operations-side counterpart to the Director of Data Center Commissioning & Quality Assurance in the Keel delivery organization: that role owns delivery standards and turnover documentation from the construction side; this role owns the operations VDR standard and the acceptance criteria that turnover and operator program content must meet to enter operations. The two roles meet, as peers, at the standards interface and the transition-to-operations gate. Key Accountabilities (list): - Own the Ops VDR (vendor data requirements) standard and submittals program portfolio-wide: templates, document control, and acceptance authority over operator-drafted content (MOPs, SOPs, EOPs, site programs). Issue the standard ahead of the first Moses Lake turnover packages so acceptance occurs against Keel templates. - Define and maintain the KPI framework all sites verify against, including measurement definitions, evidence standards, and the linkage points the FM Commercial function uses for KPI-tied commercial mechanisms. - Own CMMS and document management governance from the owner side: configuration standards, data ownership, export and audit access, CMMS population acceptance criteria, and cross-site consistency . - Serve as the operations standards counterpart to the delivery organization: align the Ops VDR standard with the Director of Cx & QA’s turnover documentation templates so handover packages land acceptance-ready. - Provide the program-level remote audit backstop to onsite QA/QC: periodic audits of CMMS data, PM completion trends, and reporting integrity across sites. - Standardize the operating model across the portfolio as new builds come online; codify the operations transition playbook with the Site Director and delivery organization after Moses Lake. - Publish periodic operations program and standards performance reporting to Operations leadership. - Explicitly not in scope: Drafting site operating procedures (operator scope, to Keel templates); commissioning standards, test scripts, and construction QA/QC (Director, Data Center Commissioning & Quality Assurance scope); site-level daily governance and tenant interface (Site Director scope); CMMS day-to-day administration (operator scope); FM invoice validation and contract commercial mechanics (FM Commercial function). - Scope demarcation — FM operations provider and Keel delivery organization Keel Operations governs and accepts; the FM operator executes operations; the Keel delivery organization (Infrastructure, including the Director of Data Center Commissioning & Quality Assurance) executes and attests delivery. The table defines the boundaries so this role duplicates neither. FM operator counterpart titles are indicative pending the staffing exhibit in the executed FM services agreement. - Function: This role (Keel Ops) owns Counterpart owns Program documents Templates, acceptance criteria, and acceptance authority; document control, portfolio-wide The FM operator drafts and maintains site procedures and program content within contracted scope Turnover documentation standards Ops VDR standard and the acceptance criteria turnover content must meet to enter operations Keel delivery org (Director, Cx & QA) owns delivery-side turnover templates, Cx documentation, and the handover process KPI framework Definition, evidence standards, and portfolio consistency The FM operator measures, self-reports, and remediates against the framework CMMS governance Owner-side configuration standards, data ownership, audit/export rights, population acceptance criteria The FM operator administers the platform and performs all operational data entry Quality assurance Operations program-level remote audit; trend analysis across sites the FM operator corporate/site QA performs the operator’s internal quality program; delivery org owns construction-phase QA/QC Cross-site standards Single Keel operations standard applied to all operators and sites The FM operator applies its own corporate playbooks only where they meet or exceed the Keel standard Qualifications: - 10+ years in critical facilities operations, operations programs, or asset management, with direct ownership of procedure/document governance and CMMS program standards at a portfolio or multi-site level. - Experience on the owner side of an outsourced FM relationship strongly preferred; must understand the difference between operating a program and governing one. - Demonstrated experience building program infrastructure — standards, templates, acceptance processes — from the ground up. - Strong document control, audit, and standards-writing capability; comfortable holding acceptance positions on operator-drafted and delivery-drafted content as a peer to senior delivery leadership. - Executive-quality written reporting. Other: - This role works hybrid remote out of Keel HQ in the financial district NYC (3 days per week in office) - Our compensation package consists of the listed base salary range here, a year end bonus, sign on equity, and participates in our yearly equity grant. NYC: $185,000 USD - $225,000 USD What We Offer (from earlier): - Competitive salary, bonus and equity opportunities - Comprehensive health and wellness benefits - Retirement savings with company contribution - Employee referral program Thus we have: About the role: could include company description and why Keel, what it feels like, what we offer? But we have Benefits separate. Maybe About the role: includes the role summary and maybe company context. Responsibilities: key accountabilities. Requirements: maybe not needed; we have Qualifications. Qualifications: as above. Skills: not explicitly listed; maybe we can omit. Benefits: list from What We Offer. Pay: salary range. Schedule: hybrid remote (3 days per week in office) plus location. We must not create sections with placeholder text. All sections have real content. Now produce HTML fragment. Structure:

About the role

... company description and role summary ...

Responsibilities

• ... each accountability ...

Qualifications

• ... each qualification ...

Benefits

• ... each benefit ...

Pay

NYC: $185,000 USD - $225,000 USD base salary range, plus year-end bonus, sign-on equity, and participation in yearly equity grant.

Schedule

Hybrid remote: 3 days per week in office at Keel HQ in the Financial District, NYC.

We need to ensure we don't repeat job title as heading. Not. We need to preserve all substantive information. Let's include company description in About the role. Company description: "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-on; smart, driven people solving real challenges together; work that directly supports AI and next-generation infrastructure; room to grow, stretch, and take on more." We can combine. Now Responsibilities: list each accountability as bullet. We need to ensure we don't include overly verbose sentences that are not needed but we must preserve all substantive info. We'll condense but keep meaning. Let's craft bullets: - Own the Ops VDR (vendor data requirements) standard and submittals program portfolio-wide: templates, document control, and acceptance authority over operator-drafted content (MOPs, SOPs, EOPs, site programs); issue the standard ahead of the first Moses Lake turnover packages so acceptance occurs against Keel templates. - Define and maintain the KPI framework all sites verify against, including measurement definitions, evidence standards, and linkage points the FM Commercial function uses for KPI‑tied commercial mechanisms. - Own CMMS and document management governance from the owner side: configuration standards, data ownership, export and audit access, CMMS population acceptance criteria, and cross‑site consistency. - Serve as the operations standards counterpart to the delivery organization: align the Ops VDR standard with the Director of Cx & QA’s turnover documentation templates so handover packages land acceptance‑ready. - Provide the program‑level remote audit backstop to onsite QA/QC: periodic audits of CMMS data, PM completion trends, and reporting integrity across sites. - Standardize the operating model across the portfolio as new builds come online; codify the operations transition playbook with the Site Director and delivery organization after Moses Lake. - Publish periodic operations program and standards performance reporting to Operations leadership. - Explicitly not in scope: drafting site operating procedures (operator scope, to Keel templates); commissioning standards, test scripts, and construction QA/QC (Director, Data