Research Engineer / Research Scientist, Remote Compute Accounting

Remote: yes Posted: 2026-09-22

THE TEAM

Some of the most consequential decisions of the AI era will depend on answering one question: can we verify what is happening inside AI datacenters? Answering it could unlock international cooperation, help countries protect their sovereignty, and enable trustworthy adoption of AI in high-stakes industries. Building tools that can earn trust across borders is an urgent technical and political challenge.

SASH’s Verification team builds and tests tools to verify agreements about AI. We prototype new verification mechanisms, lead international research collaborations, and work with policymakers around the world to show what these tools can do and inform how they’re used.

You’d join a small team combining technical expertise with international AI policy experience. Our technical team is led by Pascal Berrang, an Associate Professor at University of Birmingham, and brings experience from the Singapore Government. Our policy team brings experience from Oxford and the Centre for the Governance of AI, while our partners include experts from the Future of Life Institute and the University of Oxford.

THE PROBLEM

The hardest question in verification is not whether a datacenter is running the model it says it is. It is whether it is also running something else. A cluster can serve declared inference all day and train an undeclared model on the capacity left over.

We are interested in software-only approaches to this problem. If a verifier can keep a cluster's accelerators demonstrably occupied (i.e., their high-bandwidth memory holding the state they claim to hold, their compute answering challenges that cannot be faked or precomputed in advance), then there is no spare capacity for an undeclared training run. Physics supplies the lever: information cannot travel faster than light, and some computations cannot be performed faster than the hardware allows, so the time a cluster takes to answer is itself evidence about what hardware it has and what that hardware is doing.

The nearest concrete version is a memory-state challenge protocol. The prover commits frequently to workload checkpoints, the verifier fires N unique nonces simultaneously, and each device must return a function of its claimed memory state within a deadline (a function designed to demand serious memory bandwidth and matrix multiplication). Round-trip times are recorded and a random sample is proven genuine. A related family, proof of useful work, pushes further: the declared workload's own computation becomes the evidence, so the accounting costs almost nothing to produce.