Member of Technical Staff, Infrastructure & Operations

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, Infrastructure & Operations to own the path from commit to production for a codebase where most commits are written by AI agents, faster than any human reads them. Human review does not scale against that. CI does, and what CI enforces is the real architecture of how we ship: you decide what it enforces, and you build it, across an estate that spans GCP and specialist GPU providers, on a network you design and a failover you rehearse. You are building this from a thin starting point rather than inheriting a mature one. Every other team here ships through what you build.

Role and Responsibilities

• Own the path from commit to production. Pipelines, staged environments, promotion with real gates. The artifact that passed the tests is the artifact that runs.

• Run the cloud estate as code across GCP and specialist GPU providers: org structure, IAM, quotas, and provisioning engineers use without filing a ticket. Repo and permission management counts as infrastructure here.

• Design and operate the network underneath all of it: VPCs and subnets across providers, interconnects, DNS, cross-cloud failover. The failover gets rehearsed.

• Make onboarding a system. How fast a new engineer becomes productive is an infrastructure property, not an HR one. You build the paved road: environments, docs-as-code, and the defaults that make the right thing the easy thing.

What We're Looking For

• Five or more years building and operating production infrastructure at companies known for engineering rigor. Deep fluency in infrastructure as code, CI/CD systems, Kubernetes, and at least one major cloud platform. You have shipped infrastructure other engineers depend on daily.

• You have built CI/CD from zero to one, not just maintained a mature system. You can explain mechanically how you cut a build or registry bill. Container build and registry economics are something you reason about before they show up on an invoice.

• You have run a multi-account cloud estate as code, and you can say what you stopped people from doing. Ideally a multi-cloud network too, including the failover you rehearsed.

• You have led incidents and reduced toil with code, and you prefer self-service abstractions to tickets. Pipelines exist so engineers ship. The goal is safe speed, not fewer deploys.

Nice to Have

• Built CI/CD or release engineering from scratch at a fast-growing company.

• A strong FinOps instinct. You reason about cloud cost at the account and architecture level: commitments, egress, idle spend, unit economics. The bill is a design input, not a month-end surprise.

• Specialist GPU-cloud providers, and the account, quota, and network realities of running across them alongside a major cloud.

• Production observability on OpenTelemetry, Prometheus, Grafana, or comparable.

• You have supported machine-generated or unusually high-velocity commit patterns.

How We Work

We hold a high technical bar and give people full ownership of their work, from spec to ship to on-call. We write contracts before logic, test against real systems instead of mocks, and favor simple designs that ship over clever ones that do not. Our development process is AI-native: we work with agentic coding tools daily, write specs that are legible to humans and agents alike, and lead with leverage.

Location and Compensation

This role is based in Boston. We will consider remote candidates on a case-by-case basis. We offer competitive compensation including salary, benefits, and meaningful early-stage equity. We evaluate on technical breadth, systems thinking, scientific curiosity, and shipping velocity. We are an equal opportunity employer and value diverse perspectives in building platforms for AI-driven discovery.