Technical Program Manager

OVERVIEW Physical Superintelligence is a startup with roots at Google, NVIDIA, Harvard, Meta, MIT, Oxford, Johns Hopkins, Cambridge, and the Perimeter Institute building AI systems to discover new physics at scale. Our mission is to discover and commercialize transformative physics breakthroughs at scale with artificial superintelligence, safely, verifiably, and for broad public benefit. The last century's golden age of physics gave us transistors, lasers, and nuclear energy. We believe artificial superintelligence will unlock the next one. We're creating the infrastructure to industrialize scientific discovery and usher in this new era. We have one product: new physics, at scale. Data centers are where that product meets the market first. Our platform, Emmy, builds a coupled physics twin of a customer's site and finds capacity and energy the operator did not know they had. Every engagement runs through the same steps: NDA, scoping study, data-requirements document, pilot, contract. The physics moves fast. What stalls is everything around it: a redline waiting on customer legal, a data export waiting on a security review, a site walk waiting on a badge, a facilities engineer waiting for someone who can explain what the twin needs and why. We are seeking a Technical Program Manager to own each data center engagement end to end: the person who can explain what Emmy does, what it cannot yet do, and why, and who makes sure no engagement ever waits on a non-technical dependency. ROLE AND RESPONSIBILITIES The role has two halves. You do both. Represent PSI technically. You are the technical face of PSI on the engagement. You hold a technical conversation with the customer's facilities and infrastructure engineers and are taken seriously. You hold the same conversation with our engineers and researchers: what Emmy can do today, what is on the roadmap, why we built it the way we did, and how it applies to this site. You know where the data lives on a customer's site, what it takes to get it through their IT security review, and when an export is not usable. You turn the customer's requirements and constraints into the data-requirements document and the instrumentation plan our engineers need, and you explain results back to the customer accurately. You do not build the models or write production code. Run the engagement. Run each engagement from first conversation through signed contract and pilot. Hold the plan and the dependency list for every active customer. Know at any moment what the next blocker is, who owns it on each side, and when it clears. Own the non-technical workstreams: NDAs, engagement agreements and exhibits, data-sharing and security questionnaires, site access, insurance and compliance requests, invoicing milestones. Commercial terms and technical scope are set elsewhere; you make sure they get signed, and you chase whoever is late, on either side. Own the outcome. When a customer strikes the clause that protects our…