Maintain portfolio-level situational awareness across NPI programs, active production deployments, and cloud foundations work, holding an accurate mental model of cross-domain risks and dependencies without being in the weeds of every program simultaneously
Integrate infrastructure economics with program decisions: how a GPU generation transition affects the capacity plan, how a commissioning gate failure cascades into customer commitment delays, how a firmware lifecycle choice has direct revenue implications
Evolve the Site Operations PM to Cloud TPM engagement model as Crusoe scales from current deployment volume to significantly higher throughput
Partner with VP and SVP-level stakeholders on programs with significant organizational risk, framing trade-offs and surfacing decision-ready analysis
Drive the TPM organization from reactive to predictable: define leading indicators, build portfolio visibility, and coach Staff and Senior TPMs on technical depth, risk identification, and executive communication
Set the standard for AI tool integration across the TPM team: identify where AI materially changes program tracking, risk detection, and executive communication, and drive adoption
Generation-level GPU architecture fluency: you understand what changes architecturally between GPU generations, including networking topology, storage implications, power and cooling requirements, and commissioning gate evolution, and can reason through second-order infrastructure effects
Deep software/firmware lifecycle knowledge: BIOS/BMC/GPU firmware, DOCA targets, driver stacks, GPU validation and burn-in, and why firmware versioning matters for fleet reliability at scale
Networking and storage depth: cluster-leaf topology evolution, ZTP requirements, fabric commissioning, storage architecture implications (e.g., VAST integration), and how these must be updated for each new generation
Direct hardware partner engagement: personal ownership of NVIDIA or OEM certification and validation timelines, not coordination feeding into someone else's relationship
Active daily use of AI tools to drive program-level outcomes: risk detection, dependency mapping, and executive communication, not just personal productivity
Your NPI experience has been primarily at the workstream or commissioning level rather than owning a new SKU or generation end-to-end
You have not directly engaged hardware partners (NVIDIA, OEMs) on certification and validation timelines, and your role has been coordinating into someone else's partner relationship instead
Your infrastructure background is primarily software-defined or post-deployment support rather than build-side hardware and firmware programs
You prefer well-defined frameworks handed to you rather than defining what the framework should be