About Corvex

Corvex, Inc. (Nasdaq: MOVE) builds and operates GPU cloud infrastructure at the scale modern AI demands. We run dense accelerated-compute clusters on bare metal, powered by NVIDIA and AMD accelerators and K8s, stitched together with high-performance Ethernet and InfiniBand fabrics, and we deliver them to customers as reliable, secure, high-throughput platforms. We are scaling rapidly across new data center sites, and the infrastructure team sits at the center of that growth, building the systems that turn racks of hardware into a product customers depend on.

The role

We are hiring a Principal Infrastructure Engineer to build the foundation of our greenfield v2 cloud platform: the bare-metal provisioning and control-plane substrate that turn new racks of GPU hardware into reliable, secure, customer-ready capacity.This is a build-focused, hands-on role and the most senior individual contributor on the platform build. You will own the recommendation and the call on the infrastructure layer (we're currently in POC across different vendors) and the build-vs-buy decision that goes with it, with our Cloud Platform Architect pressure-testing it. You will drive integration across the other domains and define how infrastructure is templated, multi-tenanted, and handed to customers. You will define the architecture and the standards the rest of the team builds to, while still being deep in the code yourself. Day-to-day operations are not your focus, getting the platform designed and built right is.

You will work at the center of new cluster and new-site buildouts, partnering closely with our network, SRE, and security engineers. They own the fabric and day-to-day operations; you own getting the platform built right. Because the systems you design become the foundation customer GPU workloads run on, getting the architecture and automation right the first time matters more here than almost anywhere.

What you'll own

• Platform architecture and technical direction: own the architecture of the cloud platform control plane and orchestration layer for new GPU clusters, making the foundational decisions and setting the technical standards the rest of the platform is built on.

• Bare-metal provisioning automation: build the automated pipeline that takes a node from rack-and-stack handoff to a fully configured, real acceptance gates before a node is marked customer-ready, firmware to the qualified recipe, GPU burn-in, NCCL/RCC runs, and fabric checks, plus a golden-image build-and-qualify pipeline in CI repeatedly across sites and at scale.

• Infrastructure as code and automation: treat the platform as code from day one. Build the Terraform and Ansible that provision, configure, and validate the platform, so the build is reproducible rather than hand-assembled.

• Control-plane substrate: build the control plane that turns provisioned bare metal into cluster-ready capacity, and own the clean handoff to the Kubernetes layer. You own tenant isolation at the network and hardware layer; the Kubernetes and namespace isolation model belongs to the Principal Kubernetes Platform Engineer.

• DPU and SmartNIC integration: design how we leverage BlueField DPUs in the platform, offload, provisioning, isolation, and the SuperNIC/DPU-mode configurations that let us get the most out of the hardware.

• Platform reliability by design. Build observability, guardrails, and progressive-rollout mechanisms into the platform from the start. As you build it and design to our SOC 2, ISO 27001, and HIPAA obligation.

• Security Built-in: instrument the platform as you build it and design to our SOC 2, ISO 27001, and HIPAA obligations. Vault-based secrets model from the start. BIOS and system prep for trusted domain execution, secure boot, and backend-fabric hardening.

• Confidential-compute-ready platform (growth area): Design the tenancy and scheduling so it fits our confidential-compute roadmap: whole-GPU per tenant, and TDX with GPU passthrough. Deep CC background is a plus, not a requirement.

• New site buildouts: take a critical role in standing up the platform at new data center sites, turning green-field facilities into production capacity.

• Technical leadership: set patterns, review designs, and raise the engineering bar across the infrastructure team multiplying the impact of other engineers and mentoring senior ICs, without becoming a people manager.

What we're looking for

Required

• 10+ years building production infrastructure at scale, including deep green-field and platform-build experience, for cloud, hosting, or high-performance compute environments.

• A track record of setting technical direction on complex platforms, architecture others adopt, standards others follow, and influence that extends well beyond your own keyboard.

• Strong Linux systems fundamentals, you can reason about the kernel, networking stack, storage, and performance, not just the command line.

• Fluency in infrastructure as code and automation: Terraform, Ansible, and a real programming language used to build durable platform tooling, not just one-off scripts.

• Production Kubernetes experience: building, deploying, and operating clusters and the platform services that run on them.

• A demonstrated bias toward building things right the first time: sound architecture, reproducible automation, and durable design over short-term shortcuts.

• Strong written communication, you document designs and decisions clearly and leave systems more understandable than you found them.

Strongly preferred

• DPU / SmartNIC experience, especially leveraging offload, DPU/SuperNIC modes, and platform designs that exploit them. This is a meaningful differentiator for us.

• Experience with GPU and accelerated-compute infrastructure across NVIDIA and AMD, including ROCm and firmware lifecycle, or HPC/AI infrastructure.

• Bare-metal provisioning at scale (Redfish/BMC automation, NetBox or a similar source of truth).

• Experience standing up cloud-platform control-plane stacks in a green-field setting.

• Networking depth, BGP, VLANs, fabric concepts, and the ability to debug connectivity and throughput issues. You won't own the network, but the more fluently you can partner with our network engineers, the better.

• Familiarity with high-performance fabrics: RoCE Ethernet / InfiniBand

• HashiCorp Vault, and building within a SOC 2 / ISO 27001 / HIPAA compliance posture.

How we work

• Small, senior, high-trust teams. We hire people who can own and solve problems end to end and we give them the room to do it.

• Code over clicks. The platform is defined, reviewed, and versioned. Manual changes are the exception and they get automated away.

• Build it right. We invest in sound architecture and durable design so the platform scales cleanly instead of accumulating debt.

• Customers are real. The platform exists to serve customer workloads, and we build to the reliability and white-glove standard that implies.

• We document. Designs, decisions, and architecture are written down so the team compounds knowledge instead of re-learning it.

AI as a force multiplier

We expect our engineers to use AI to move faster and operate at higher leverage, and we build our environment to make that the default rather than an afterthought. We maintain CLAUDE.md and AGENTS.md context files across our repositories, run MCP servers against our operational systems (Jira, NetBox, Checkmk), and use agentic coding tools such as Claude Code directly in our infrastructure and platform workflows.

You don't need to be an AI expert, but you should be eager to fold these tools into how you design, build, and automate — and to help us push the frontier of what an AI-leveraged infrastructure team can do.

What success looks like

First 30 days

• Ramped on our environment: the platform stack, provisioning approach, and target architecture. able to navigate the codebase and design docs independently.

• Shipped your first meaningful contribution to the platform build with the team's review.

• Aligned with network, SRE, and security on where your work meets theirs.

First 90 days

• Owning a defined component of the platform build end to end, from design through delivery.

• Delivered a meaningful piece of provisioning or platform automation that made the build faster, more reproducible, or more reliable.

• Shaped at least one foundational architecture decision that the platform is built on.

First 12 months

• The recognized technical authority for the cloud platform build, setting direction and trusted across network, SRE, security, and platform engineering.

• Designed and delivered a significant piece of the cloud platform or its automation that raised the team's leverage and the platform's reliability.

• Took a lead role in bringing at least one new data center site online.