Skip to main content
Software Engineering Daily

Developer Experience at Capital One with Catherine McGarvey

41 min episode · 2 min read
·

Episode

41 min

Read time

2 min

Topics

Software Development

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.

Know someone who'd find this useful?

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 — Free

Keep Reading

More from Software Engineering Daily

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Software Engineering 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 up to 3 shows.

Start My Monday Digest

No credit card · Unsubscribe anytime