USA remote
Member of Technical Staff, Software Engineering
About this role
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. We are seeking engineers to build platform infrastructure at the intersection of computational science, AI systems, and software engineering. 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. We are seeking a Member of Technical Staff, Product to build every surface a human touches at PSI: the tools users run physics campaigns through, the SDK engineers build on, and the interfaces partners see.
Everything else we build gets judged at this layer, by people who have somewhere else to be. The measure of the work is whether they came back. ROLE AND RESPONSIBILITIES - Build the user's path through the platform: chat, SDK, campaign management, and the budget and spend tooling underneath. All of it thin clients over one contract, so what we build once shows up everywhere. - Own time-to-first-result as a product metric.
A new user should get from arriving to a real result with no engineer in the room. Every default, error message, and empty state either shortens that path or is in the way. - Build partner-facing surfaces from the same contract as everything else. One product with many faces. The public site counts: owned as a product, shipped fast, treated as the first thing a candidate or a customer sees, because it is. - Build the design system as infrastructure.
A constrained component library that humans and AI agents both compose against, so agent-written front-end code comes out consistent the way a linter makes any generated code come out clean. WHAT WE'RE LOOKING FOR - Three or more years building product full stack: React and TypeScript in front, Python services behind. You have shipped surfaces real users depended on daily, and you have owned one from design through its first rough weeks in production.