Developer Experience at Capital One with Catherine McGarvey - Software Engineering Daily Recap

Podcast: Software Engineering Daily

Published: 2026-01-13

Duration: 42 minutes

Guests: Catherine McGarvey

Summary

Catherine McGarvey discusses how Capital One is enhancing developer experience by balancing speed, security, and AI tools to boost productivity. She emphasizes the shift towards more strategic roles for developers as AI handles routine tasks.

What Happened

Catherine McGarvey, SVP of Developer Experience at Capital One, outlines the company's focus on speeding up development cycles, reducing operational overhead, and increasing productivity. She explains that developer enablement at Capital One involves providing tools that accelerate development while ensuring a connection to user value. Success in this area is measured through continuous deployment metrics and customer satisfaction, indicating a balance between speed and quality.

Capital One is navigating the challenge of maintaining agility within a regulated environment. McGarvey discusses the importance of standardization to improve efficiency and facilitate smoother team migrations. The use of AI tools, such as LLM-powered coding assistants, is pivotal in enhancing developer productivity, though it requires careful introduction to address concerns about job replacement.

Training for AI tools at Capital One is use case-centric, ensuring developers understand their effective application. AI tools are especially beneficial for junior developers, aiding them in comprehending codebases and learning new frameworks. However, McGarvey emphasizes the need for quality control through rigorous code review processes.

AI tools are transforming the role of developers by shifting their focus from mundane tasks to more judgment-based and strategic roles. McGarvey envisions peak productivity as the ability to turn an idea into a user-facing product the same day, minimizing human intervention.

Tracking the wrong metrics can lead to undesirable outcomes, such as prioritizing the quantity over the quality of pull requests. Capital One is cautious about this, emphasizing metrics like cycle time from story start to end in JIRA to better understand development efficiency.

Improving developer experience also involves ensuring that tools are self-service and accessible, while reducing confusing error messages. McGarvey discusses the need to understand the established communication norms and routines when transitioning to a large organization to effectively drive change.

Key Insights