By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
How I AIHow Coinbase scaled AI to 1,000+ engineers | Chintan Turakhia
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
Great conversations run long. Their best ideas don't have to.
uListen is free on iPhone, iPad, Android, Chrome, and Claude.
See howAt a glance
WHAT IT’S REALLY ABOUT
Coinbase’s playbook for scaling AI adoption across 1,000+ engineers
- Chintan Turakhia explains how Coinbase moved from superficial AI trials ("hello world" usage that didn’t stick) to sustained adoption across 1,000+ engineers by treating AI as an “adapt or die” accelerant rather than a mandate.
- The approach centered on a high-conviction, hands-on leader demonstrating real wins, focusing first on eliminating engineering toil (tests, linting, PR setup) and creating social proof via shared channels and live “PR speed runs.”
- He emphasizes measuring impact through end-to-end cycle time—ticket to production/user value—then compressing each stage (draft PR creation, review time, release) to unlock customer feedback loops.
- The episode also demos practical systems: using Cursor analytics to cohort users and generate a playbook, and an internal Slack/Linear agent (“Claude Bot”) that turns live feedback into tickets and PRs while meeting security requirements.
IDEAS WORTH REMEMBERING
5 ideasAI adoption fails when it’s trialed, not operationalized.
Coinbase saw early Copilot/tool adoption spikes that faded because engineers tried it once, found it lacking, and wrote it off. The fix was persistent, daily use until repeatable workflows emerged.
A single credible, hands-on champion can change the culture faster than policy.
Chintan argues leaders must “show, not tell” by using the tools in real coding work, learning failure modes, and demonstrating concrete wins—engineers ignore decrees but follow evidence.
Start with soul-sucking toil to create immediate trust and pull demand.
Targeting unit tests, linting, and other “paper cut” tasks made AI valuable quickly and freed engineers to do higher-leverage work, building momentum for broader use.
Create viral visibility of wins (and losses) inside existing communication hubs.
A dedicated channel (“cursor-wins”) let engineers broadcast successes, prompting peers to copy techniques. Keeping the magic in Slack makes it observable and shareable, driving organic spread.
Time-boxed “PR speed runs” convert skepticism into belief in minutes.
By having everyone ship a trivial PR during an all-hands, teams experienced a rapid, tangible output spike (e.g., 70 PRs in 15 minutes; later 300–400 PRs in 30 minutes company-wide), making velocity real and undeniable.
WORDS WORTH SAVING
5 quotesIt’s not only possible, it’s adapt or die.
— Chintan Turakhia
Show the engineers, not just tell. And the worst thing any eng leader could do is just be like, 'I decree you must use AI.'
— Chintan Turakhia
No one’s getting bonus points for memorizing Git commands.
— Claire Vo
It was really sort of a death to status updates, long live building moment.
— Chintan Turakhia
My calendar’s empty… the coordination overhead… No, you just do things.
— Chintan Turakhia
Ask ChatGPT about this episode
Get its key ideas, plus a summary of each chapter linked to that point in the video, right in your chat.
Add uListen AI to ChatGPT.
Install uListen AI in ChatGPT (opens in a new tab)Needs a ChatGPT account.Paste this prompt into a new chat.
Use uListen AI to give me this episode's key ideas and a chapter-by-chapter summary, with timestamps: https://www.youtube.com/watch?v=tidINuXB7PA
High quality AI-generated summary created from speaker-labeled transcript.
