Skip to content
RiverCore
OpenAI's Custom Chip Lead Defects to Anthropic Before IPO
OpenAI custom chipAI hardwareAnthropic hireOpenAI chip engineer joins AnthropicAI silicon talent exodus pre-IPO

OpenAI's Custom Chip Lead Defects to Anthropic Before IPO

8 Jun 20267 min readMarina Koval

The question every platform lead with a multi-year AI infrastructure commitment should be asking this week is whether OpenAI's custom silicon roadmap survives contact with a pre-IPO talent exodus. Clive Chan, who described himself as the second hardware hire on OpenAI's chip program, just announced he is moving to Anthropic. He kept his title (Member of Technical Staff) and changed his employer, which is a very specific signal about where the use in AI hardware is shifting.

This is not a junior departure. This is the person who was there before there was a team, leaving the team he helped build, to go rebuild a similar team at the company most directly competing for the same TSMC capacity, the same packaging slots, and the same compiler engineers.

What Happened

Chan posted what he called a "Personal update" on X, confirming he had left OpenAI after roughly 2.4 years and joined Anthropic this week. As The Times of India reported, he joined OpenAI in January 2024 after two and a half years at Tesla, where he worked as a senior software engineer on the Autopilot deep learning infrastructure team building out Dojo.

In his post, Chan wrote: "I've decided to leave OpenAI. I'm proud to have been part of the custom chip program and grateful to everyone I got to build with and learn from along the way." He then went out of his way to praise the team he was leaving: "The density of hardware talent on that team is extraordinary, and I don't think there's a better chip design team anywhere." On Anthropic, he said he was "deeply impressed with the team's talent, values, and ambition."

His Tesla work, per his own description, covered "machine learning training ASIC: software framework bring up, data center codesign, power efficient number formats, weekly with CEO." That is not a single discipline. That is the full stack between transistor and training loop. Tesla detailed Dojo in 2021, installed the first system in 2022 with around 3,000 D1 chips manufactured by TSMC, and has since lost senior people: Ganesh Venkataramanan, the senior director of autopilot and Dojo project lead, departed in early December, and Tesla's head of AI infrastructure Tim Zaman announced a move to Google DeepMind about a week later.

OpenAI, meanwhile, is heading toward an IPO. Losing a foundational hardware hire to your closest model rival a few quarters before an S-1 is the kind of detail bankers notice.

Technical Anatomy

To understand why this one departure matters more than a typical Member of Technical Staff transition, you have to look at how custom AI silicon programs actually get built. Google's TPU, Amazon's Trainium, and Microsoft's Maia each took the better part of a decade and survived multiple generations of personnel churn precisely because the institutional knowledge was distributed. OpenAI's chip program is younger. When Chan calls himself the second hardware hire, he is telling you the bus factor is small.

Custom ASIC design for training workloads is not just RTL. It is a tightly coupled co-design problem across at least four layers: the silicon itself (number formats, memory hierarchy, interconnect), the compiler and kernel library that maps PyTorch or JAX graphs onto that silicon, the data center power and cooling envelope, and the training framework integration that decides which ops even go to the accelerator. Chan's Tesla scope, by his own description, spanned framework bring-up, data center codesign, and power efficient number formats. That is the connective tissue between the chip team and the model team. People who can sit in both rooms are the rate limiter on these programs.

Industry chatter places custom chip growth at 44.6% in 2026, roughly 3x the pace of merchant GPUs. If that trajectory holds, the supply of engineers who have actually shipped a training ASIC into a production data center is the genuinely scarce input, not wafer starts. Anthropic, which has been deepening its silicon posture and runs its API stack documented at docs.anthropic.com, just hired a person who has done that twice.

The cost of replacing that institutional memory inside OpenAI is not the salary. It is the 12 to 18 months of context that a replacement does not have. Tape-out cycles do not pause for onboarding.

Who Gets Burned

Start with OpenAI itself. Pre-IPO companies sell narrative as much as revenue, and the narrative here was: we are not GPU-dependent forever, we are building our own engine. Every departure from the chip team weakens that story for the prospectus. The CFO at OpenAI should be asking this week how the custom silicon roadmap will be framed under S-1 risk-factor scrutiny if more chip personnel follow Chan, and whether the company needs to lock in retention grants for the remaining senior hardware staff before the filing window opens. That is a treasury question, not an HR one.

Next, downstream enterprise customers. If you are a fintech or iGaming platform that signed a multi-year capacity commitment with OpenAI on the assumption that custom silicon would drive inference unit economics down by 2027, your procurement team needs a hedge. Anthropic is now the more credible long-term silicon story on a relative basis, which has implications for how you weight your dual-vendor strategy and whether you accelerate evaluation of Claude-based agents against the patterns described in OpenAI's own platform docs.

Then there is Tesla, which has now bled Venkataramanan, Zaman, and earlier Chan from its silicon and AI infrastructure stack inside roughly two and a half years. Dojo as a competitive training platform was always a bet that Tesla could attract and retain people who would otherwise be at Nvidia, Google, or a hyperscaler. That bet is visibly weakening.

Finally, the merchant GPU incumbents. Every senior engineer who leaves one frontier lab's custom chip team for another's is a data point that the industry believes custom silicon is the strategic frontier, not a side project. That belief, more than any one tape-out, is what pressures GPU pricing power.

Playbook for AI Development

For platform leads and CTOs evaluating where to put the next eight figures of AI infrastructure spend, three concrete moves are worth making in the next 90 days.

First, treat the choice between OpenAI and Anthropic as a vendor concentration question, not a benchmark question. Model quality converges. Supply chain control diverges. Ask your account teams at both labs for explicit roadmap commitments on inference cost per million tokens for 2027 and 2028, and discount their answers based on how exposed each lab is to merchant GPU pricing versus owned silicon.

Second, audit your team's hardware literacy. The labs are bidding aggressively for compiler engineers, ML systems people, and anyone who has shipped against an ASIC. If you have these people on your platform team, your retention budget needs to reflect the new market clearing price, which is being set by Anthropic and OpenAI, not by your local salary band.

Third, if you are designing agent architectures, build them to be portable across model providers from day one. The Model Context Protocol spec at modelcontextprotocol.io exists precisely so that swapping the underlying model is a configuration change rather than a rewrite. The labs are unstable. Your abstraction layer should not be.

Key Takeaways

  • OpenAI's second hardware hire leaving for Anthropic weeks ahead of an IPO is a roadmap risk, not just a personnel event.
  • Custom AI silicon programs are constrained by senior engineers who span chip, compiler, and data center, and that talent pool is visibly migrating.
  • Tesla has now lost Chan, Venkataramanan, and Zaman from its silicon and AI infrastructure stack, weakening Dojo's competitive position.
  • Enterprise buyers should treat OpenAI versus Anthropic as a supply chain concentration decision, with custom silicon trajectory as a key input.
  • Teams evaluating multi-year AI infrastructure spend should be asking whether their agent architecture can survive a forced provider swap inside one quarter.

Frequently Asked Questions

Q: Why does one engineer leaving OpenAI matter so much?

Chan was the second hardware hire on OpenAI's custom chip program, meaning his institutional knowledge spans the entire history of the effort. Custom ASIC programs are bottlenecked by senior engineers who can work across silicon, compilers, and data center design, and replacing that context typically takes 12 to 18 months.

Q: Does this change OpenAI's IPO story?

It complicates it. Part of OpenAI's long-term margin narrative depends on reducing dependence on merchant GPUs through custom silicon. A foundational chip hire defecting to the closest model competitor weeks before an S-1 filing window is the kind of detail that ends up in risk factors and bankers' questions.

Q: Should enterprise teams switch from OpenAI to Anthropic because of this?

Not on this single signal. The right response is to treat model provider choice as a supply chain question, build agent architectures that are portable across providers using standards like MCP, and ask both labs for explicit inference cost commitments for 2027 and beyond before locking in multi-year capacity deals.

MK
Marina Koval
RiverCore Analyst · Dublin, Ireland
SHARE
// RELATED ARTICLES
HomeSolutionsWorkAboutContact
News06
Dublin, Ireland · EUGMT+1
LinkedIn
🇬🇧EN▾