Vice President Information Technology
Patmos · Kansas City, MO · 3 wk ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, maybe Pay/Schedule not present. Also include maybe "How You Operate" but that's part of description; we can treat as part of About the role? The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract substantive content: The job summary includes location, full-time. About Patmos paragraph. The Role paragraph. How You Operate bullet list. Responsibilities (with sub-bullets). Qualifications (with bullet list). What Success Looks Like (maybe could be part of Qualifications? but it's separate content; we could include as a section maybe "What Success Looks Like" but not in prescribed headings list; but we can still use
for any section heading? 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 can use other headings if needed. However they say prefer a few substantive sections over many thin ones. Could combine some.
We need to include Benefits section because they list benefits. So we need Benefits heading with list.
We need to include About the role heading (maybe combine About Patmos and The Role and How You Operate). Could be one section.
Responsibilities heading with list.
Requirements heading (maybe combine Requirements and Qualifications? They are separate: Requirements list bullet items; Qualifications list bullet items. Could combine into one Requirements section? But they are distinct; we could have Requirements heading and Qualifications heading. Both are substantive.
We also have "What Success Looks Like" which is descriptive; could be part of Qualifications or separate section "Success Metrics". Might be okay to include as its own section.
We must not include boilerplate like equal opportunity, etc. Remove duplicated lines.
We need to preserve all substantive information: include location, full-time, About Patmos description, The Role description, How You Operate bullet points, Responsibilities bullet points, Qualifications bullet points, Requirements bullet points, What Success Looks Like bullet points, Benefits list.
Also include maybe "About Us" and "Why Join Us" sections? Those are substantive but could be considered boilerplate? They are about company mission; maybe we can include as "About the Company" but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include those paragraphs as well. However they might be considered boilerplate? They are not navigation/legal/EEO etc. They are substantive about mission. So we should keep them.
But we need to avoid too many thin sections. Could combine About Patmos, About Us, Why Join Us into a single "About the Company" section.
Let's plan sections:
- About the role (includes The Role paragraph and How You Operate bullet list)
- Responsibilities (list)
- Requirements (list)
- Qualifications (list)
- What Success Looks Like (list or paragraph)
- Benefits (list)
- About the Company (combines About Patmos, About Us, Why Join Us, maybe also location and employment type)
We need to ensure we don't repeat job title.
We need to output only HTML fragment, no /, no markdown.
We'll use for each section heading.
Inside sections, we will use
for prose,
- for lists.
We need to preserve all substantive info: let's extract.
From posting:
Job SummaryPatmos | Kansas City, MO (on-site) | Full-time
About PatmosPatmos is the only profitable independent multi-megawatt AI hosting owner-operator in the country. We convert brownfield industrial sites into environmentally sustainable, community-improving, high-density data centers — delivering speed-to-power that the hyperscalers cannot match. Our web hosting and professional services divisions create a freer internet for businesses of all sizes. We are employee-owned, we move fast, and our internal operations need to run as well as the facilities we build for clients.
The RoleThe VP of Information Technology owns execution of technology and internal operations for Patmos. The CEO and the executive team set the priorities. This role has full authority to determine how those priorities get done — buy, build, integrate, or retire — within budgets developed in partnership with Finance.This is an enterprise operator, not a specialist who owns a slice of the stack. You are accountable for the systems the company runs on, the security posture that protects it, the operating discipline of the teams that deliver it, and the outcomes those teams produce. Software that serves the business, internal IT, identity, integrations, and company-wide security sit with you. You partner with the VP of Infrastructure and provide guidance on execution at the facilities layer so corporate technology and operational technology stay aligned.Success is the success of your people. We need a selfless leader who gets results through others, who builds a team that can run without heroics, and who still has the technical and operational judgment to point more junior people at the right work and coach them to a finished outcome. You will still get your hands in the work when the situation demands it. You will not confuse being busy with leading.You report to the CEO. You sit on the executive team and work alongside the Director of Engineering (who builds what you specify) and the Director of Program Management (who drives rollout and adoption of what you ship). For the right person, this seat is the proving ground for company-wide technology leadership as Patmos scales.
How You Operate• Job zero is execution against priorities the business has already named. Strategy without delivery is not the job.• You have full authority over method: architecture, vendor selection, sequencing, and operating model — inside agreed budgets and with Finance as a standing partner, not an after-the-fact reviewer.• You lead through the team. Outcomes are measured by whether the function performs when you are not in the ticket.• You partner with the VP of Infrastructure. You set standards and give execution guidance; facility operators run the plant. Boundaries are clear. Accountability is shared where the layers meet.• You specify; engineering builds. You do not accumulate a shadow product org, and you do not wait for perfect specs while the business is blocked.• You default to integrate and administer. You build only when the business case is real and the operating cost of custom is understood.
ResponsibilitiesLeadership and operating discipline• Lead, develop, and hold accountable the internal technology organization — priorities, standards, growth paths, and performance.• Install operating rhythm: ticket SLAs, on-call, documentation, runbooks, and visible status so the function runs on process, not heroics.• Build a bench. Your job is to make the next layer of the team capable of owning outcomes without you in the middle of every decision.• Own the IT budget end to end and report it cleanly. No surprises.Systems, data, and integration• Own the application portfolio — accounting and billing, CRM, project management, procurement, HR and payroll — as one integrated operating platform, not a pile of subscriptions.• Establish a single source of truth for core company data: customers, contracts, assets, sites, and people. Eliminate duplicate systems of record.• Own integrations. Specify the custom tooling and glue Engineering should build. Manage the SaaS estate: licensing, renewals, consolidation, and spend.• Deliver the systems that physical security, physical infrastructure, and the commercial organization depend on — built, integrated, and run to a standard the rest of the company can trust.Security — company-wide• Own the security program from end to end: corporate IT, internally built tools, and the OT layer of live facilities (BMS, power monitoring, physical access, client environment boundaries). Set the standard. Verify compliance in partnership with infrastructure operators.• Identity and access everywhere: SSO, MFA, role-based access, quarterly reviews, and airtight onboarding and offboarding.• Incident response, tested backups, patching, and vulnerability management across the estate.• Own client security questionnaires and lead the company to third-party attestation (SOC 2 or equivalent). Questionnaires become a sales asset, not a fire drill.Corporate technology operations• Endpoint and device management, corporate network, and the collaboration stack.• An employee support experience with measured response standards and a reputation for closing work.• Stay close enough to the work that you can diagnose, direct, and unblock — without becoming the bottleneck.
Qualifications• 15+ years across IT, systems, and technology operations, with at least 10 years leading a team that owned a full stack — not a function inside someone else’s stack.• You have run execution, not just advised on it. You have shipped operating models, integrations, and security programs that other people now run.• Comfortable in a fast-moving, employee-owned company where you are measured on whether things work — and on whether your team can make them work without you.
What Success Looks Like• Within 6 months: the technology organization runs on defined process; access management is airtight; leadership can see system status without asking; the team is visibly stronger than the day you arrived.• Within 12 months: core systems are integrated around a single source of truth; we have passed or are on a clear path to pass a third-party security assessment; questionnaires are routine.• Ongoing: business priorities move from decision to production without you becoming the critical path; your people own outcomes; infrastructure and corporate technology execute against a shared standard.
RequirementsEnterprise IT Operations and LeadershipSecurity Program Management (SOC 2, ISO 27001, or equivalent)Identity and Access Management (SSO, MFA, RBAC)Team Leadership and DevelopmentExecution and Operational DisciplineNice to HaveSaaS and Application Portfolio ManagementIndustrial/OT Environments and Data Center OperationsStakeholder Collaboration and Alignment
How We Hire... (we can drop as boilerplate? It's about hiring culture; maybe keep as part of About the Company? It's substantive but could be considered boilerplate? It's not legal/EEO; it's about hiring philosophy. Might keep.)
About Us... (keep)
Why Join Us... (keep)
Benefits include:● Unlimited PTO● 401(k) match (4%)● Health, dental, & vision insurance● Short and long term disability● Life insurance (company paid and supplemental available)● Generous parental leave, baby bonuses, marital bonuses, and other family-friendly perks● 14 observed paid holidays that include solemnities
We need to output HTML.
Let's craft sections:
About the Company
Patmos is the only profitable independent multi-megawatt AI hosting owner-operator in the country. We convert brownfield industrial sites into environmentally sustainable, community-improving, high-density data centers — delivering speed-to-power that the hyperscalers cannot match. Our web hosting and professional services divisions create a freer internet for businesses of all sizes. We are employee-owned, we move fast, and our internal operations need to run as well as the facilities we build for clients.
Patmos Hosting, Inc. delivers Freedom as a ServiceTM, providing organizations with an independent alternative to Big Tech's commercial constraints, censorship, cancellation and deplatforming.
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: The job summary includes location, full-time. About Patmos paragraph. The Role paragraph. How You Operate bullet list. Responsibilities (with sub-bullets). Qualifications (with bullet list). What Success Looks Like (maybe could be part of Qualifications? but it's separate content; we could include as a section maybe "What Success Looks Like" but not in prescribed headings list; but we can still use
for any section heading? 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 can use other headings if needed. However they say prefer a few substantive sections over many thin ones. Could combine some.
We need to include Benefits section because they list benefits. So we need Benefits heading with list.
We need to include About the role heading (maybe combine About Patmos and The Role and How You Operate). Could be one section.
Responsibilities heading with list.
Requirements heading (maybe combine Requirements and Qualifications? They are separate: Requirements list bullet items; Qualifications list bullet items. Could combine into one Requirements section? But they are distinct; we could have Requirements heading and Qualifications heading. Both are substantive.
We also have "What Success Looks Like" which is descriptive; could be part of Qualifications or separate section "Success Metrics". Might be okay to include as its own section.
We must not include boilerplate like equal opportunity, etc. Remove duplicated lines.
We need to preserve all substantive information: include location, full-time, About Patmos description, The Role description, How You Operate bullet points, Responsibilities bullet points, Qualifications bullet points, Requirements bullet points, What Success Looks Like bullet points, Benefits list.
Also include maybe "About Us" and "Why Join Us" sections? Those are substantive but could be considered boilerplate? They are about company mission; maybe we can include as "About the Company" but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include those paragraphs as well. However they might be considered boilerplate? They are not navigation/legal/EEO etc. They are substantive about mission. So we should keep them.
But we need to avoid too many thin sections. Could combine About Patmos, About Us, Why Join Us into a single "About the Company" section.
Let's plan sections:
- About the role (includes The Role paragraph and How You Operate bullet list)
- Responsibilities (list)
- Requirements (list)
- Qualifications (list)
- What Success Looks Like (list or paragraph)
- Benefits (list)
- About the Company (combines About Patmos, About Us, Why Join Us, maybe also location and employment type)
We need to ensure we don't repeat job title.
We need to output only HTML fragment, no /, no markdown.
We'll use for each section heading.
Inside sections, we will use
for each section heading. Inside sections, we will use
for prose,
- for lists.
We need to preserve all substantive info: let's extract.
From posting:
Job SummaryPatmos | Kansas City, MO (on-site) | Full-time
About PatmosPatmos is the only profitable independent multi-megawatt AI hosting owner-operator in the country. We convert brownfield industrial sites into environmentally sustainable, community-improving, high-density data centers — delivering speed-to-power that the hyperscalers cannot match. Our web hosting and professional services divisions create a freer internet for businesses of all sizes. We are employee-owned, we move fast, and our internal operations need to run as well as the facilities we build for clients.
The RoleThe VP of Information Technology owns execution of technology and internal operations for Patmos. The CEO and the executive team set the priorities. This role has full authority to determine how those priorities get done — buy, build, integrate, or retire — within budgets developed in partnership with Finance.This is an enterprise operator, not a specialist who owns a slice of the stack. You are accountable for the systems the company runs on, the security posture that protects it, the operating discipline of the teams that deliver it, and the outcomes those teams produce. Software that serves the business, internal IT, identity, integrations, and company-wide security sit with you. You partner with the VP of Infrastructure and provide guidance on execution at the facilities layer so corporate technology and operational technology stay aligned.Success is the success of your people. We need a selfless leader who gets results through others, who builds a team that can run without heroics, and who still has the technical and operational judgment to point more junior people at the right work and coach them to a finished outcome. You will still get your hands in the work when the situation demands it. You will not confuse being busy with leading.You report to the CEO. You sit on the executive team and work alongside the Director of Engineering (who builds what you specify) and the Director of Program Management (who drives rollout and adoption of what you ship). For the right person, this seat is the proving ground for company-wide technology leadership as Patmos scales.
How You Operate• Job zero is execution against priorities the business has already named. Strategy without delivery is not the job.• You have full authority over method: architecture, vendor selection, sequencing, and operating model — inside agreed budgets and with Finance as a standing partner, not an after-the-fact reviewer.• You lead through the team. Outcomes are measured by whether the function performs when you are not in the ticket.• You partner with the VP of Infrastructure. You set standards and give execution guidance; facility operators run the plant. Boundaries are clear. Accountability is shared where the layers meet.• You specify; engineering builds. You do not accumulate a shadow product org, and you do not wait for perfect specs while the business is blocked.• You default to integrate and administer. You build only when the business case is real and the operating cost of custom is understood.
ResponsibilitiesLeadership and operating discipline• Lead, develop, and hold accountable the internal technology organization — priorities, standards, growth paths, and performance.• Install operating rhythm: ticket SLAs, on-call, documentation, runbooks, and visible status so the function runs on process, not heroics.• Build a bench. Your job is to make the next layer of the team capable of owning outcomes without you in the middle of every decision.• Own the IT budget end to end and report it cleanly. No surprises.Systems, data, and integration• Own the application portfolio — accounting and billing, CRM, project management, procurement, HR and payroll — as one integrated operating platform, not a pile of subscriptions.• Establish a single source of truth for core company data: customers, contracts, assets, sites, and people. Eliminate duplicate systems of record.• Own integrations. Specify the custom tooling and glue Engineering should build. Manage the SaaS estate: licensing, renewals, consolidation, and spend.• Deliver the systems that physical security, physical infrastructure, and the commercial organization depend on — built, integrated, and run to a standard the rest of the company can trust.Security — company-wide• Own the security program from end to end: corporate IT, internally built tools, and the OT layer of live facilities (BMS, power monitoring, physical access, client environment boundaries). Set the standard. Verify compliance in partnership with infrastructure operators.• Identity and access everywhere: SSO, MFA, role-based access, quarterly reviews, and airtight onboarding and offboarding.• Incident response, tested backups, patching, and vulnerability management across the estate.• Own client security questionnaires and lead the company to third-party attestation (SOC 2 or equivalent). Questionnaires become a sales asset, not a fire drill.Corporate technology operations• Endpoint and device management, corporate network, and the collaboration stack.• An employee support experience with measured response standards and a reputation for closing work.• Stay close enough to the work that you can diagnose, direct, and unblock — without becoming the bottleneck.
Qualifications• 15+ years across IT, systems, and technology operations, with at least 10 years leading a team that owned a full stack — not a function inside someone else’s stack.• You have run execution, not just advised on it. You have shipped operating models, integrations, and security programs that other people now run.• Comfortable in a fast-moving, employee-owned company where you are measured on whether things work — and on whether your team can make them work without you.
What Success Looks Like• Within 6 months: the technology organization runs on defined process; access management is airtight; leadership can see system status without asking; the team is visibly stronger than the day you arrived.• Within 12 months: core systems are integrated around a single source of truth; we have passed or are on a clear path to pass a third-party security assessment; questionnaires are routine.• Ongoing: business priorities move from decision to production without you becoming the critical path; your people own outcomes; infrastructure and corporate technology execute against a shared standard.
RequirementsEnterprise IT Operations and LeadershipSecurity Program Management (SOC 2, ISO 27001, or equivalent)Identity and Access Management (SSO, MFA, RBAC)Team Leadership and DevelopmentExecution and Operational DisciplineNice to HaveSaaS and Application Portfolio ManagementIndustrial/OT Environments and Data Center OperationsStakeholder Collaboration and Alignment
How We Hire... (we can drop as boilerplate? It's about hiring culture; maybe keep as part of About the Company? It's substantive but could be considered boilerplate? It's not legal/EEO; it's about hiring philosophy. Might keep.)
About Us... (keep)
Why Join Us... (keep)
Benefits include:● Unlimited PTO● 401(k) match (4%)● Health, dental, & vision insurance● Short and long term disability● Life insurance (company paid and supplemental available)● Generous parental leave, baby bonuses, marital bonuses, and other family-friendly perks● 14 observed paid holidays that include solemnities
We need to output HTML.
Let's craft sections:
About the Company
Patmos is the only profitable independent multi-megawatt AI hosting owner-operator in the country. We convert brownfield industrial sites into environmentally sustainable, community-improving, high-density data centers — delivering speed-to-power that the hyperscalers cannot match. Our web hosting and professional services divisions create a freer internet for businesses of all sizes. We are employee-owned, we move fast, and our internal operations need to run as well as the facilities we build for clients.
Patmos Hosting, Inc. delivers Freedom as a ServiceTM, providing organizations with an independent alternative to Big Tech's commercial constraints, censorship, cancellation and deplatforming.