Member of Technical Staff, Applied AI

StaffHybrid
CompanyPhysical Superintelligence
LocationBoston
Category-
DepartmentTechnical Staff
SeniorityStaff
WorkplaceHybrid
Posted2026-07-22
Viaashby

Description

OVERVIEW

Physical Superintelligence is a startup with roots at Google, NVIDIA, Harvard, Meta, MIT, Princeton, Oxford, Johns Hopkins, Cambridge, and the Perimeter Institute building AI systems to discover new physics at scale. We are seeking applied physicists, engineers from the traditional disciplines (mechanical, electrical, aerospace, chemical), and computational scientists to put AI to work on real engineering systems: thermal and fluid systems, electrical power distribution, structures, and the coupled models that tie them together. Models that beat the solvers they replace, and AI that designs rather than only evaluates. Applied AI at PSI is applied physics plus AI.

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.

ROLE AND RESPONSIBILITIES

  • Model real physical systems with AI. Build simulations, surrogates, and coupled multiphysics models of engineering systems, thermal, fluid, electrical, and structural, that beat traditional workflows on accuracy, speed, or both, and validate them against solvers and measured data.
  • Model each domain at engineering depth. Conjugate heat transfer and airflow, load flow, short-circuit and protection studies of power distribution, structural and vibration analysis, electrochemistry. Pair the classical studies with learned models and optimization.
  • Learn from simulators. Train models over classical simulation that run orders of magnitude faster than the solvers they replace and still hold up on inputs outside the training data. Training-set accuracy is not the bar.
  • Close the loop from analysis to design. Use models and agents to search a design space, not only to score a design someone else proposed.
  • Make simulation legible to agents. Decide where solver fidelity is required, where a learned model is enough, and how the two work together.
  • Ship to customers. Each engagement solves a customer's actual problem and ends with something they can run. Every engagement either compounds a capability we reuse across customers or it is killed at renewal. Publish the methods where it serves the mission.

WHAT WE'RE LOOKING FOR

  • A PhD, or an equivalent research record, in mechanical, electrical, aerospace, or chemical engineering, applied physics, computational science, or machine learning for science. You have modeled a physical system that mattered and validated the model against ground truth: a surrogate against a solver, a simulation against a facility, a model against measured data. You can say how you knew it was right and what you did when it was not.
  • Depth in at least one engineering domain. Thermal and fluid (CFD, conjugate heat transfer), power systems (load flow, short-circuit, protection coordination, harmonics, transient stability), structural (FEA), or electrochemistry, with the tools of that domain (OpenFOAM, SU2, ETAP, PSCAD, OpenDSS, pandapower, CalculiX, Code_Aster, or comparable) and the standards it works to. You know where the models lie.
  • Hands-on computational engineering. You have run and extended CFD, FEA, power system, or multiphysics codes, you understand discretization, convergence, and boundary conditions, and you know the trade-offs between a high-fidelity solver and a faster learned alternative.
  • Machine learning you have applied yourself: PyTorch or JAX, training runs you designed and debugged, models that held up outside the training set. You do not need a top-venue publication record. You do need to have shipped ML on a physics problem rather than on a synthetic benchmark.
  • You write production code: Python that other people run, with tests, in a repository rather than a notebook. You are comfortable in HPC and cloud GPU environments.
  • Judgment on real-world problems. You can scope a problem with a senior domain engineer, tell them what is credible and what is not, and deliver working artifacts rather than slide decks.

NICE TO HAVE

  • Neural operators, physics-informed networks, differentiable simulation, or uncertainty quantification for learned models.
  • Experience with open-source simulation codes (OpenFOAM, OpenDSS, pandapower, CalculiX, or comparable) rather than only commercial packages.
  • Domain work in thermal and fluid systems, power systems and power electronics, structures, or electrochemistry.
  • Peer-reviewed publications in computational physics, engineering, or ML for science.

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 physics depth, modeling judgment, ML fluency, and shipping velocity. We are an equal opportunity employer and value diverse perspectives in building platforms for AI-driven discovery.