Developer Experience at Capital One with Catherine McGarvey
Episode
41 min
Read time
2 min
Topics
Productivity, Investing, Fundraising & VC
AI-Generated Summary
Key Takeaways
- ✓Make compliance easy: Capital One defaults developers to pre-approved, secure tools and databases rather than requiring manual security reviews for each choice. Teams can request exceptions when needed, but the default path is both fastest and most secure, reducing friction while maintaining controls.
- ✓Measure outcomes, not output: Track time between deployments and user satisfaction scores rather than lines of code or PR counts. Focus on whether tools actually solve developer problems and enable continuous deployment. Metrics like time-to-first-commit for onboarding reveal if teams have what they need to contribute quickly.
- ✓AI coding assistants provide asymmetric value: Junior developers gain the most lift from AI tools for understanding codebases, learning new languages, and getting unbiased answers. Senior developers see more value in automated migrations, test generation, and eliminating low-value tasks like dependency updates rather than core development work.
- ✓Standardize selectively for leverage: Only standardize tools when multiple teams adopt similar solutions or when open standards exist. In rapidly evolving areas like LLMs, use abstraction layers and consistent evaluation criteria across pilots rather than locking into one vendor, enabling teams to switch models as technology improves.
What It Covers
Catherine McGarvey, SVP of Developer Experience at Capital One, explains how the company enables 14,000 technologists to move faster while maintaining security and compliance through standardization, AI-powered coding assistants, and continuous deployment practices.
Key Questions Answered
- •Make compliance easy: Capital One defaults developers to pre-approved, secure tools and databases rather than requiring manual security reviews for each choice. Teams can request exceptions when needed, but the default path is both fastest and most secure, reducing friction while maintaining controls.
- •Measure outcomes, not output: Track time between deployments and user satisfaction scores rather than lines of code or PR counts. Focus on whether tools actually solve developer problems and enable continuous deployment. Metrics like time-to-first-commit for onboarding reveal if teams have what they need to contribute quickly.
- •AI coding assistants provide asymmetric value: Junior developers gain the most lift from AI tools for understanding codebases, learning new languages, and getting unbiased answers. Senior developers see more value in automated migrations, test generation, and eliminating low-value tasks like dependency updates rather than core development work.
- •Standardize selectively for leverage: Only standardize tools when multiple teams adopt similar solutions or when open standards exist. In rapidly evolving areas like LLMs, use abstraction layers and consistent evaluation criteria across pilots rather than locking into one vendor, enabling teams to switch models as technology improves.
Notable Moment
McGarvey compares resisting AI tools to taking an open-book test but choosing not to use the book. She argues engineers who fear these changes likely enjoy tasks that automation now handles, and should find roles aligned with their preferences rather than missing productivity gains.
You just read a 3-minute summary of a 38-minute episode.
Get Software Engineering Daily summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from Software Engineering Daily
NanoClaw and the Rise of Personal AI Agents
Jul 21 · 63 min
Latent Space
Why AI Infrastructure must evolve for Agent Experience — Akshat Bubna, Modal CTO
Jul 8
More from Software Engineering Daily
Agentic DevOps at AWS
Jul 16 · 49 min
The TWIML AI Podcast
How Capital One Delivers Multi-Agent Systems with Rashmi Shetty - #765
Apr 16
More from Software Engineering Daily
We summarize every new episode. Want them in your inbox?
NanoClaw and the Rise of Personal AI Agents
Agentic DevOps at AWS
AURA and Open-Source Agents for Production Operations
Eric Ries on Why Good Companies Go Bad
SED News: Restricted Models, IDE Wars, and the DeepMind Mafia
Similar Episodes
Related episodes from other podcasts
Latent Space
Jul 8
Why AI Infrastructure must evolve for Agent Experience — Akshat Bubna, Modal CTO
The TWIML AI Podcast
Apr 16
How Capital One Delivers Multi-Agent Systems with Rashmi Shetty - #765
Odd Lots
Jun 27
How Lenovo's CFO Is Allocating Capital During One of History's Biggest Booms
NVIDIA AI Podcast
Jun 24
Inside Instacart's AI-Powered Smart Shopping Cart | NVIDIA AI Podcast Ep. 302
Eye on AI
Jun 13
One Company Now Has More AI Agents Than Human Employees | Ryan Gavin of Slack
Explore Related Topics
This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's Investing & Markets Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into Software Engineering Daily.
Every Monday, we deliver AI summaries of the latest episodes from Software Engineering Daily and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime