Coinbase CEO fires engineers who skip AI onboarding in a week

Coinbase CEO Brian Armstrong announced on the “Cheeky Pint” podcast that several engineers were terminated after failing to onboard to the company’s AI coding tools within a week, signaling a hardline stance on AI adoption at the crypto exchange [1].

The AI mandate and its enforcement

Armstrong told the podcast that he had posted a Slack message demanding all engineers onboard to AI tools by the end of the week and warned of a Saturday meeting for non‑compliant staff. When the meeting took place, a small group attended; those with legitimate excuses (e.g., returning from a trip) were spared, while the rest were dismissed [1][2]. The CEO framed the move as “going rogue” to reinforce that AI is not optional at Coinbase.

How the policy fits into Coinbase’s broader AI push

Coinbase has secured enterprise licenses for both GitHub Copilot and Cursor to cover every engineer, and the firm now runs monthly “AI speed‑run” sessions where teams share creative AI uses [2]. Armstrong said the ultimate aim is to have half of the company’s code generated by AI by the end of the current quarter, a timeline that contrasts with earlier internal estimates that adoption would take “a quarter or two” to reach 50 % [1]. He also emphasized that AI‑generated code must still undergo human review and checks, especially for money‑moving systems [1].

Industry context

Coinbase’s aggressive stance mirrors broader tech‑sector pressure. Google’s leadership has similarly urged staff to embed AI in daily work, and a Gallup survey found that 33 % of “managers of managers” use AI several times a week—nearly double the rate of individual contributors [1]. While many engineers see productivity gains from AI (a GitHub study reported 92 % of U.S. programmers using AI tools, with 70 % citing a competitive edge), forcing adoption can be disruptive, as noted by observers who compare the approach to other firms that later reversed AI‑driven layoffs [2].

What to watch

• AI adoption metrics: Coinbase’s internal reporting on the percentage of code written with AI, especially any quarterly updates.
• Employee sentiment: Signals from internal forums or public comments that could indicate broader morale impacts.
• Regulatory scrutiny: Any statements from regulators about AI use in crypto‑related code, given the heightened focus on operational risk.

The episode highlights a growing divide between CEOs who view AI as a non‑negotiable productivity lever and engineers who may be wary of rapid, enforced adoption. Whether Coinbase’s “heavy‑handed” approach accelerates its AI roadmap or fuels internal pushback remains to be seen.