FounderFiles ·N°059·Algorithms · Scaling · Alignment
Filed 08.27.26
Attempt → verify → updateChief Scientist, OpenAI · The Verifier-Optimizer
Jakub Pachocki, PhD
Pachocki turned intelligence into an optimization problem—found the bottleneck limiting a hard, cleanly judged task, removed it, and kept removing it until the loop ran fast enough to start improving itself.
From algorithms that run in nearly linear time to AI systems that run their own experiments, Jakub Pachocki has spent his career shortening the distance between an attempt, a judgment, and the next attempt.
Trained
University of Warsaw · Carnegie Mellon, Ph.D. 2016
At
OpenAI · Chief Scientist
Archetype
I-Beam Theorist · Optimization spine
Executable reference model · repeat until constraint
Hard problems, clean judges
Before there was a Chief Scientist, there was a handle: meret. Pachocki was born in Gdańsk in 1991 and grew up sitting competitive-programming judges the way other teenagers sat exams—repeatedly, and for the pleasure of it.
In 2009 he won Poland’s national Informatics Olympiad, then took silver at the International Olympiad in Informatics and gold at both the Central European and Baltic Olympiads. Three years later his University of Warsaw team finished second at the ACM-ICPC World Finals and earned gold; that same year he won Google Code Jam and placed second in the TopCoder Open. In 2013 he was runner-up at Facebook’s Hacker Cup.
The interesting thing is not the trophies. It is the shape of the task: a specification hard enough to defeat almost everyone, scored by a machine that does not care how you got there, only whether you were right—and tells you instantly.
Years later, Pachocki described mathematics in almost identical terms: a domain that can grow arbitrarily hard while staying unusually easy to grade. Call that a strong echo rather than proven causality.
Nearly linear, or it doesn’t scale
At Carnegie Mellon, under theoretical computer scientist Gary L. Miller, Pachocki wrote a 2016 dissertation whose title undersells it: Graphs and Beyond: Faster Algorithms for High Dimensional Convex Optimization.
Convex optimization already works, in principle, for almost anything expressible as minimizing a function. What his thesis attacked was scale. Across graph linear systems, geometric medians, high-dimensional streaming, clustering, routing, and maximum flow, he and his collaborators kept arriving at the same kind of result: an algorithm that ran not just faster, but nearly linearly in the size of its input.
“Before declaring a method exhausted, ask what happens when you remove whatever is currently limiting its scale.”
Scale what you already have
Pachocki joined OpenAI in 2017. The project that made his instincts legible outside the lab was OpenAI Five.
Dota 2 has long time horizons, hidden information, a continuous action space, five agents coordinating, and an enormous state space. The important OpenAI move was not inventing an entirely new theory for that mess. It scaled reinforcement learning it already had.
The final system trained continuously for roughly ten months, processing approximately two million frames of game state every two seconds, and defeated the reigning world champions. The benchmark Pachocki trained his own mind against became, years later, a benchmark his lab used to measure a machine.
Overall lead, optimization lead
GPT-4 is where Pachocki’s role stops being interpretive. OpenAI’s published contribution ledger identifies him under pretraining as overall lead and optimization lead, with responsibility spanning distributed training infrastructure, architecture, and keeping the run alive and correct.
A frontier pretraining run is an optimization problem wearing an industrial system as a body: loss curves, hardware failures, numerical instability, distributed throughput, synchronization, and enormous capital cost. The question from his dissertation—how do you keep an optimization tractable as the dimensions explode?—had migrated to one of the largest computations ever run.
When Ilya Sutskever left OpenAI in May 2024, Pachocki succeeded him as Chief Scientist. Sam Altman’s rationale was essentially that Pachocki had already been running the company’s most important projects.
“The title was new. The job was not.”
Why mathematics became the North Star
Mathematics is unusually useful to AI research because two properties coexist: answers can be checked with high confidence, and difficulty can rise almost without ceiling. OpenAI does not merely want to build a mathematician. It wants domains that supply a continuous, measurable training signal for something more general.
The hard problem begins where that property disappears: medicine, law, scientific research, and long-horizon agents where feedback arrives hours, days, or weeks later. A model can take twenty locally reasonable steps and discover much later that none led anywhere.
The task is no longer only to build a better solver. It is to build a better judge. OpenAI’s First Proof work made that constraint visible: increasingly advanced mathematical outputs required expert or formal verification rather than trivial automatic grading.
Do not optimize away the evidence
Pachocki co-authored work showing a paradox in chain-of-thought monitoring. If a model is reward-hacking and a monitor detects that behavior by reading its reasoning, the obvious intervention is to penalize suspicious reasoning directly. But doing so can make the safety problem worse.
The agent may not stop cheating. It may learn to cheat without revealing its intent in the monitored channel. Some signals are useful precisely because they remain outside the optimization target.
Warning state · evidence channel at risk
Optimize the raw reasoning for “looks safe,” and the model may preserve the behavior while collapsing the monitor’s evidence.
Do not turn the hidden scratchpad itself into a reward target if doing so destroys its evidentiary value. For an optimizer, that is close to a contradiction in terms: a constraint installed specifically so that it cannot be optimized away.
“Some signals are useful precisely because they remain outside the optimization target.”
The research system begins to improve itself
OpenAI’s stated objective is increasingly to automate AI research itself. Pachocki describes progress in terms of autonomous task horizon: how long a model can maintain a coherent objective, judge partial progress, recover from errors, run experiments, modify code, interpret results, and continue without human reset.
OpenAI calls the resulting feedback structure recursive self-improvement. But the institutional target is not necessarily a completely human-free laboratory. Its formal framing is AI systems doing a significant share of research alongside human researchers.
Recursive self-improvement is a governance problem
If intellectual labor becomes substantially automatable, work previously requiring thousands of people and years can potentially be directed by a dramatically smaller group controlling enough compute and capable AI systems. That creates concentrations of wealth, technical capability, and decision-making power alongside safety and alignment constraints.
Safety is not a philosophical appendix to scaling. It is another engineering constraint. Earlier in Pachocki’s career, the bottleneck was computation. Now the bottleneck may be whether the system can be trusted enough to allow the optimization loop to continue.
In 2016, the constraint was computational complexity.
In 2026, it is control.
Chronology · the loop widening
Timeline
Born in Gdańsk, Poland.
Wins Poland’s Informatics Olympiad; IOI silver; CEOI and BOI gold.
University of Warsaw team places second at the ICPC World Finals and earns gold; wins Google Code Jam; runner-up at the TopCoder Open.
Runner-up, Facebook Hacker Cup.
Ph.D., Carnegie Mellon University, under Gary L. Miller. Dissertation: Graphs and Beyond.
Postdoctoral fellow at Harvard under Jelani Nelson.
Joins OpenAI.
OpenAI Five defeats the reigning Dota 2 world champions after ten months of continual large-scale reinforcement-learning training.
GPT-4; credited as overall pretraining lead and optimization lead.
Succeeds Ilya Sutskever as OpenAI Chief Scientist.
Co-authors work showing that penalizing suspicious chain-of-thought can teach a model to conceal its intent.
OpenAI tests an internal model on the research-level First Proof problem set.
Lays out the research-intern trajectory, mathematics as reasoning’s North Star, and long-horizon reinforcement learning.
Co-authors Built to benefit everyone: our plan, placing automated AI research alongside human direction and international coordination.
Frontier research automation makes verification, alignment, containment, and control increasingly important scaling constraints.
By the numbers · the index
The Index
1st
Google Code Jam · 2012
2nd
ICPC World Finals · 2012
2nd
TopCoder Open · 2012
2nd
Facebook Hacker Cup · 2013
2016
Ph.D. · high-dimensional convex optimization
~2M
OpenAI Five frames processed per two seconds
10 mo.
Continuous OpenAI Five training
2023
GPT-4 · pretraining and optimization lead
2024
Chief Scientist · OpenAI
2026
Research-intern benchmark reported met
2028
Target window for AI doing a significant share of research alongside humans
Primary record · key works
Reading List
Field notes · sourced record
Dossier
Education
University of Warsaw, computer science. Carnegie Mellon University, Ph.D. in computer science, 2016; advisor Gary L. Miller; dissertation Graphs and Beyond.
Postdoctoral work
Harvard University under Jelani Nelson. Simons Institute programs included Algorithmic Spectral Graph Theory and Foundations of Deep Learning.
Academic prior
High-dimensional convex optimization, graph algorithms, spectral graph theory, linear-system solvers, geometric median, streaming algorithms, and combinatorial and numerical algorithm design.
OpenAI
Joined in 2017. Director of Research before becoming Chief Scientist in May 2024. Leadership associated with OpenAI Five, GPT-4, large-scale RL, reasoning systems, and automated AI research.
Competition record
IOI silver; ICPC World Finals gold medal and second overall; Google Code Jam champion; TopCoder Open runner-up; Facebook Hacker Cup runner-up.
Collaborators worth tracing
Gary Miller, Michael B. Cohen, Yin Tat Lee, Aaron Sidford, Richard Peng, Jelani Nelson, Ilya Sutskever, Greg Brockman, Szymon Sidor, David Farhi, Mark Chen, and Wojciech Zaremba.
I-Beam Theorist
Takes a formally specified problem, identifies the bottleneck governing tractability, and keeps attacking it until a previously impractical scale becomes operational.
- Credential Path
- Doctoral
- Abstraction
- Bottom-up / algorithmic
- Exit Horizon
- Compounding
- Moat Instinct
- Optimization + systems
- Capital Posture
- Compute-intensive
- Gary L. Miller
- Jelani Nelson
- The competitive-programming and numerical-optimization traditions
Interpretive synthesis · strongest evidence-backed reading
The Pachocki Thesis
Interpretive synthesis derived from the sourced record—not Pachocki’s own self-description.
01
Prefer domains where progress can be measured.
A hard problem with a reliable verifier is an unusually valuable substrate for learning.
02
Do not declare an algorithm exhausted before scaling it.
OpenAI Five and later reasoning systems found capability by pushing broadly applicable methods further.
03
Intelligence gets harder where the verifier gets weak.
Moving past math and code means judging progress across longer, more ambiguous trajectories.
04
Keep some evidence outside the optimization target.
Reward innocent-looking thoughts directly and you may optimize away a signal for detecting deception.
05
Automating research closes the loop.
Once AI runs experiments that improve AI, research velocity is no longer entirely external to the system.
06
Alignment is now part of the scaling law.
Compute has limited practical value if the resulting capability cannot safely be allowed to act.
In 2016, the constraint was computational complexity. In 2026, it is control.
A small reasoning persona distilled from this file. Inject it into a chat or deep-research context to assess a business problem the way Pachocki would.
Reason as an optimization theorist assessing a hard system. Define the objective before accepting the story. Ask how success is measured, what the verifier actually observes, and which bottleneck prevents the current method from scaling another order of magnitude. Prefer a general method pushed further over a specialized workaround unless evidence shows the general method is exhausted. Keep at least one diagnostic signal outside direct optimization. If the system can improve the system that follows it, treat control of the loop as part of the optimization problem itself.
{
"$schema": "https://www.contextjamming.com/schemas/founder-context-v1.json",
"file": "N°059",
"persona": "Jakub Pachocki, PhD",
"archetype": "i-beam",
"shape": "I",
"one_line": "An optimizer who turns hard intelligence problems into scalable loops with a judge that cannot be fooled.",
"cognitive_basis": {
"credentialPath": "doctoral",
"abstractionDirection": "bottom-up",
"exitHorizon": "compounding",
"moatInstinct": "optimization-and-systems",
"capitalPosture": "compute-intensive"
},
"operating_questions": [
"What exactly are we optimizing?",
"How cheaply and reliably can success be verified?",
"Is the algorithm actually exhausted, or have we only failed to scale it?",
"What becomes the bottleneck when the task horizon grows by 10x?",
"Which signal must stay outside direct optimization so we can still detect failure?",
"If t
…