Skip to main content

About the role

Hybrid Remote • Houston, TXDescription The SeniorCloud Engineer builds, automates, and operates Fervo's Azure-native cloud platform, turning architectural designs into repeatable, well-governed infrastructure. The role centers on infrastructure as code, GitHub-based delivery, self-service platform capabilities, and automated configuration of Linux and Windows systems. Success requires hands-on engineering, demonstrated coding ability, and the discipline to manage infrastructure through version-controlled, peer-reviewed practices rather than manual change.
Requirements
Responsibilities: Infrastructure as Code & Delivery Build and maintain infrastructure as code (Terraform and/or Bicep) and reusable modules to provision Azure resources consistently across environments and sites Build CI/CD pipelines in GitHub Actions and enforce GitOps workflows where changes flow through version control, pull requests, and peer review Platform Engineering & Self-Service Build and iterate golden paths and self-service capabilities, with guardrails codified as policy to keep provisioning within security, cost, and tagging standards Document platform capabilities so internal teams can consume them without one-to-one engineering support Systems Configuration & Fleet Management Manage Linux and Windows configuration through automation—Ansible and SUSE Manager (or equivalent) for Linux; Microsoft Intune and/or Group Policy for Windows—rather than manual, host-by-host changes Maintain baseline images and standards so new hosts, including field and edge compute, are provisioned in a known, compliant state Operations, Security & Compliance Operate Azure landing zones and platform services within an Entra ID / Zero Trust model, with observability across monitoring, logging, alerting, and cost Ensure changes flow through auditable pipelines supporting SOX ITGC, and apply NERC CIP-aligned controls where platform components support in-scope systems Qualifications RequiredBachelor's degree in computer science, engineering, or related field (or equivalent experience) 8 years in infrastructure support or engineering with demonstrated progression 6+ years in cloud engineering, infrastructure automation, or platform engineering Production experience with infrastructure as code (Terraform and/or Bicep), including reusable modules and state management Hands-on experience with Git/GitHub and GitHub Actions for CI/CD or similar product Demonstrated coding ability in Python and/or PowerShell, evidenced by repositories or work samples Experience managing both Linux and Windows systems through automation (e.g., Ansible, Microsoft Intune and/or Group Policy) Preferred Platform engineering experience: internal developer platforms, golden paths, and self-service provisioning Google Cloud Platform (GCP) experience; Azure remains the primary platform SUSE Manager (or equivalent, such as Red Hat Satellite) and Microsoft Intune at scale Policy-as-code (Azure Policy, Open Policy Agent) and secrets management (Azure Key Vault, HashiCorp Vault) Regulated-sector experience and familiarity with NIST CSF, ISO 27001, or NERC CIP Certifications such as Azure Administrator Associate (AZ-104), Azure DevOps Engineer Expert (AZ-400), or HashiCorp Terraform Associate

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this