Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Psi

Member of Technical Staff, AI Research

  • Seen live on Psi's site today
  • Senior
  • Remote
Pay
Not stated
Location
Boston
Open for
11+ days
First seen
Oct 24, 2026
Apply on Psi's site (opens in a new tab)

Posting record

No flags

Open 11+ days

The posting's record, oldest first
  1. Psi's site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Psi, so its true age is longer.

Last checked Nov 4, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the 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 AI researchers to build the agents and training systems that learn to do physics.

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

  • Do original research on agents and training systems that learn to do physics, and publish it where it serves the mission.
  • Build what you research: training runs, evaluations and harnesses that ship as working systems, not isolated artifacts.
  • Go deep in one lane: reinforcement learning and post-training; agents, evaluation and verification; model architectures and training dynamics; scientific and generative modeling.
  • Work with the physicists who design verification harnesses and the engineers who build training infrastructure.

What We're Looking For

  • Three or more years of research experience, with recent publications at top venues (NeurIPS, ICML, ICLR, or comparable physics-ML venues). You can defend the result and you can name the claim you would retract.
  • Three or more years of hands-on research engineering with the modern ML stack: PyTorch or JAX, training and post-training frameworks, inference engines for rollouts, experiments run on multi-GPU clusters. You write research code that others reuse, and at least one system you built this way beat a non-trivial baseline and shipped as a working artifact rather than a notebook.
  • Depth in at least one of the following. We hire for one lane and expect you to work across the others:
  • Reinforcement learning and post-training: policy optimization, reward design, RLHF, RLVR, GRPO, RL for language models and for control.
  • Agents, evaluation and verification: tool use, long-horizon reasoning, memory and harnesses, evals, verifiers, reward models, instrumentation that separates reasoning from gaming.
  • Model architectures and training methods: transformers, state-space and graph models, neural operator and surrogate architectures for physical fields and meshes, scaling laws, optimization, training dynamics.
  • Scientific and generative modeling: learning from simulators, physics-informed and conservation-aware models, out-of-distribution behaviour, diffusion and generative models, code generation with checkable results.

Nice to Have

  • A physics or mathematics background: you can hold a substantive conversation with a domain physicist.
  • Distributed training at cluster scale: single GPU to cluster without rewriting, and what breaks at each step.
  • Experience applying agents to simulators, scientific tools, games, or rigorous benchmark suites.
  • Open-source contributions or research artifacts the community has adopted.

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 hybrid, three days a week in person in our Cambridge, MA office. 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 research depth, experimental rigor, systems fluency, and shipping velocity. We are an equal opportunity employer and value diverse perspectives in building platforms for AI-driven discovery.

Something wrong with this posting?