Apple Sends 200 Siri Engineers to Multi-Week AI Coding Bootcamp

If Apple, the company with more cash than some countries, thinks its engineers have an AI coding skill gap serious enough to mandate bootcamps, what does that say about your team?

MacRumors reports that Apple is sending approximately 200 Siri engineers to a multi-week AI coding bootcamp ahead of WWDC 2026 (June 8-12). The remaining 60 engineers stay on core Siri, another 60 shift to testing. Here's the detail that caught my eye: some Apple divisions already have large budgets for Claude Code while Siri engineers lagged behind. The skill gap isn't between Apple and the rest of the industry. It's inside Apple itself.

This mirrors the 20/60/20 split Steve Yegge described at Google: 20% power users, 60% chat-mode users, 20% refusers. Apple apparently looked at their Siri division and decided the 60% in the middle needed forced intervention. A multi-week bootcamp isn't a lunch-and-learn. It's an acknowledgment that the gap between AI-proficient and AI-resistant engineers has real product consequences.

The timing matters. WWDC is eight weeks away. Apple's Siri has been embarrassingly behind for years. Whatever they're planning to show requires engineers who can build with AI tools, not just build AI features. The distinction is important. Building WITH Claude Code is different from building an AI product. Apple needs both, and their Siri team apparently had neither.

I've been saying for months that the bottleneck isn't writing code anymore, it's orchestrating AI. This is Apple proving it with their budget. They're not buying a new tool or hiring new people. They're retraining existing engineers to work differently. That's the hardest kind of organizational change, and Apple decided it was worth pulling 200 engineers off active development for weeks to do it.

Duolingo's CEO tried the opposite approach, mandating AI usage in performance reviews, then reversed course after backlash. Meta requires agent-assisted code changes. Apple chose bootcamps. Three different companies, three different strategies for the same problem: how do you get your existing engineers to adopt AI tools?

What builders should do: Audit your team's AI coding proficiency honestly. Not "do they have access to Copilot?" but "can they run an agentic coding session with context engineering, custom instructions, and multi-step workflows?" If the answer is no for most of your team, you have the same problem Apple has. The investment is training, not tooling.