How Coinbase scaled AI to 1,000+ engineers | Chintan Turakhia

How Coinbase scaled AI to 1,000+ engineers | Chintan Turakhia

How I AIMar 2, 202658m

Claire Vo (host), Chintan Turakhia (guest)

Making AI adoption “stick” in large orgsHands-on leadership vs mandatesToil-first use cases (tests, linting, PR creation)PR speed runs and social proof in SlackMeasuring impact: ticket-to-user cycle timeCursor analytics cohorting and playbooksInternal agents: Slack + Linear + MCP integrations

In this episode of How I AI, featuring Claire Vo and Chintan Turakhia, How Coinbase scaled AI to 1,000+ engineers | Chintan Turakhia explores 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.

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.

Key Takeaways

AI 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. ...

Get the full analysis with uListen AI

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.

Get the full analysis with uListen AI

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.

Get the full analysis with uListen AI

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. ...

Get the full analysis with uListen AI

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. ...

Get the full analysis with uListen AI

Measure AI impact with end-to-end cycle time, not vanity metrics.

He criticizes metrics like “AI lines of code” and instead tracks time from ticket to landed change for users, including PR authoring, review latency, and release steps.

Get the full analysis with uListen AI

Internal agents become powerful when anchored to a shared context system.

Coinbase used Linear as the “source of context,” then built an in-house Slack bot that can generate PRs and query tools (Datadog, Sentry, Amplitude, Snowflake) via MCPs—especially important under security constraints.

Get the full analysis with uListen AI

Notable Quotes

It’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

Questions Answered in This Episode

In your early “trough of sorrow,” what specific prompting/workflow changes turned Cursor from “kinda sucked” into daily value for you personally?

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.

Get the full analysis with uListen AI

For the PR speed run: what guardrails did you set (scope, review expectations, rollback rules) to prevent chaos while still “breaking the rules”?

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.”

Get the full analysis with uListen AI

You reduced PR review cycle time ~10× (150 hours to ~15 hours). What concrete process/tool changes caused the biggest drop?

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.

Get the full analysis with uListen AI

How do you prevent “agent-generated PR spam” from overwhelming reviewers and CI/CD, especially after large-scale speed runs?

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.

Get the full analysis with uListen AI

What Cursor rules or templates were the highest leverage for your team (unit tests, linting, PR descriptions, repo conventions)?

Get the full analysis with uListen AI

Transcript Preview

Claire Vo

People are skeptical that large, established, highly technical, highly capable engineering organizations can deploy AI at scale and get any effect. But I think you've proven it's possible.

Chintan Turakhia

It's not only possible, it's adapt or die. It's just been such a huge superpower for the team.

Claire Vo

How many engineers are we talking about here?

Chintan Turakhia

A thousand plus.

Claire Vo

So we're not messing around here.

Chintan Turakhia

The company tried to adopt other AI tools, and we saw this uptick in adoption. People opened it up, checked the box, did kind of like a hello world thing, but it didn't stick. My biggest thing is how do I make this damn thing stick? Because there's something here.

Claire Vo

I do think that it's really important when you're doing this organizational transformation that you have a single person with incredible conviction at the leadership level who is also hands-on the metal.

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." Come on, no one's gonna listen to you.

Claire Vo

[upbeat music] Welcome back to How I AI. I'm Claire Vo, product leader and AI obsessive here on a mission to help you build better with these new tools. Today we have Chintan Turakhia, senior director of engineering at Coinbase, and he's gonna show us, yes, it is possible to drive AI adoption and higher velocity in an engineering organization of thousands of engineers. He's also gonna show us the new expectations for engineering managers and engineering leaders, which is less meetings and more code. Let's get to it. This episode is brought to you by WorkOS. AI has already changed how we work. Tools are helping teams write better code, analyze customer data, and even handle support tickets automatically. But there's a catch. These tools only work well when they have deep access to company systems. Your copilot needs to see your entire code base. Your chatbot needs to search across internal docs. And for enterprise buyers, that raises serious security concerns. That's why these apps face intense IT scrutiny from day one. To pass, they need secure authentication, access controls, audit logs, the whole suite of enterprise features. Building all that from scratch, it's a massive lift. That's where WorkOS comes in. WorkOS gives you drop-in APIs for enterprise features so your app can become enterprise-ready and scale upmarket faster. Think of it like Stripe for enterprise features. OpenAI, Perplexity, and Cursor are already using WorkOS to move faster and meet enterprise demands. Join them and hundreds of other industry leaders at WorkOS.com. Start building today. Chintan, thank you so much for joining. What I love about what we're gonna talk about today is we spend so much time talking about the individual vibe coder or the non-technical person becoming a software engineer, and still people are skeptical that large, established, highly technical, highly capable engineering organizations can deploy AI at scale and get any effect. There's still so much skepticism, but I think you've proven it's possible, and you're hopefully gonna show us the way.

Install uListen to search the full transcript and get AI-powered insights

Get Full Transcript

Get more from every podcast

AI summaries, searchable transcripts, and fact-checking. Free forever.

Add to Chrome