Technical Program Manager

About the role

Built to set the gold standard for integrated AI infrastructure Crux AI is a newly formed, U.S.-based integrated AI infrastructure company created to remove the physical and operational constraints on consequential AI ambitions. Crux brings together power, high-density data centers, TPU silicon, networking, orchestration software, and ongoing operations as one integrated system. Crux is being capitalized to plan every layer together, develop each one to demanding standards, and operate the whole system with efficiency and reliability. That gives hyperscalers, frontier AI labs, sovereign customers, enterprises, and AI-native companies greater freedom to pursue the AI they are here to create.

Responsibilities

• Own the translation layer between Crux's Finance function and its infrastructure delivery pipeline.
• Report to Crux's Chief Program Manager.
• Run the program discipline that keeps a multi‑billion‑dollar build pipeline legible to Finance, Development, and Operations at once: translating capacity plans, cost and margin models, and deal terms into a common, defensible view that leadership can act on without relitigating every project from scratch.
• This is a process‑from‑scratch seat — there is no inherited PMO playbook to run, only the mandate to build one, fast, without adding headcount to compensate for missing rigor.
• Own the program cadence connecting Finance, Development, and Operations on every active data center and capacity commitment — one integrated view of cost, schedule, and deal status, not three disconnected ones.
• Translate capacity plan of record and cost/margin model of record inputs into Finance‑ready outputs, and translate Finance's constraints back into terms Development and Operations can execute against.
• Build and run the intake, review, and escalation gates for the active project portfolio, so nothing material moves without the right functions weighing in at the right stage.
• Track commitments made in program reviews to closure — flag deviations, at‑risk milestones, and sequencing conflicts before they become delays, not after.
• Partner directly with Finance's financial modeling team to ensure their models are fed by current, reconciled program data rather than stale inputs.
• Build the reporting and status mechanisms that let leadership see risk early — a program that surfaces its own bad news is the goal, not the exception.
• Default to AI‑agentic workflows for status tracking, reconciliation, and reporting — this function does not scale by adding coordinators.
• After 60 Days: Program cadence and escalation gates are stood up and running across at least one active workstream; first integrated Finance/Development/Operations status view is in use, replacing ad hoc updates.
• After 6 Months: Commitments‑to‑closure tracking is live across the full active portfolio, with zero silently