Mark Chen
7 statements across 1 episodes · 5 bullish · 1 bearish · 1 people on the record · first statement Jun 25, 2026 by Mark Chen · said 4 times in 2 episodes since 2025 · across every show →
On the record as a speaker too: Mark Chen's record, appearances and statements → this page counts the times other people say the name.
Mentions by year
brought up most by Alex Lupsasca (3)
tap a year for its mentions
2026 3 mentions in 1 episode
Everything said about Mark Chen, oldest first
Jun 25, 2026 negative
OpenAI's Mark Chen: AI is in an evals crisis with saturated benchmarks
“So I think beyond that, the other scary thing in the field is the number of canonical gold standard benchmarks is low. And we really are kind of in an evals crisis, right? Where all the really great evals that we all know, like growing up, like taking the SAT …”
Jun 25, 2026 bullish
Jun 25, 2026 neutral
OpenAI's Chen: Reinforcement learning struggles in subjective, hard-to-grade fields
“RLs traditionally had headwinds when it's come to fields that, you know, it's more kind of, Subjective than objective. So if you kind of think of, you know, one kind of, you know example of this is creative writing, where, you know, you could take two pieces o…”
Jun 25, 2026 positive
Jun 25, 2026 bullish
OpenAI's Chen: AI models already discover novel theorems and advance sciences
“The initial direction we took was you should move it to real world research, right? And we've seen that the models, they've gotten a lot better at just kind of discovering novel theorems and pushing the frontiers of hard sciences. Even today, right, that's no …”
Jun 25, 2026 positive
Chen: Compaction shortcuts expensive native long context in coding products
“Many, many coding products today have features like compaction, right? Where you can compress kind of either insights or working state and stuff like that, you know, it just shortcuts a lot of the very brutally difficult and expensive permit is that you have t…”
Jun 25, 2026 positive
Chen: Eval teams and model optimization teams must remain separate
“Yeah, I think there's a kind of interesting philosophy of separate the teams that are creating the evals from the teams that are optimizing the models themselves, because that way you don't, like, co-incentivize them, right? Like, the way the evals theme can w…”