Skip to content

Blog

Junior engineers gain the most from AI coding tools

A year-long study of 300 engineers at one company found real productivity gains from AI coding assistants, the largest for juniors, and gains that track how intensively teams adopt.

Written by

Measuring AI impact

Published: 9 October 2025 Updated: 1 min read

Everyone’s asking: “Do AI coding tools actually make developers more productive?”

The data is in. And it’s not what most people think.

A comprehensive study (opens in a new tab) just measured real productivity gains across 300 engineers at one company using an AI coding assistant. The results reveal something counterintuitive about who benefits most.

The hard numbers

  • 31.8% reduction in PR review cycle time
  • 60.1% overall increase in code shipped
  • About 20 minutes saved per developer daily

Who benefits most

  • Junior engineers: 77% productivity increase
  • Mid-level engineers: 45% productivity increase
  • Senior engineers: 44% productivity increase

The juniors are seeing nearly 2x the gains of senior engineers.

Where AI actually delivers

The top three use cases:

  • UI and frontend development (25.2%)
  • Bug fixing and debugging (21.8%)
  • Backend code generation (21.1%)

Gains track adoption intensity

The study found a direct correlation between adoption intensity and productivity gains. High adopters saw significant measurable improvements. Low adopters saw minimal or even negative impact.

This tells us something critical: AI coding productivity isn’t about the tool. It’s about strategic engagement with the tool.

What this means for engineering leaders

The teams seeing real ROI aren’t the ones with the best AI tools.

They’re the ones who’ve intentionally designed processes that use AI for pattern-heavy, high-volume work while keeping humans focused on strategic decisions.

They’re treating AI as an amplifier of existing skill, not a replacement for developing it.

And they’re measuring the right metrics: cycle time reduction, not just code volume.

The productivity gains are real. But they require deliberate strategy, not passive adoption.

The question isn’t “Should we use AI coding tools?” It’s “How are we intentionally designing practices to maximize the measurable impact of AI on our team’s delivery velocity?”

Has your team seen measurable productivity gains from AI coding tools?

Further reading

  1. GenAI creates more work before it creates less A German study of IT leaders finds 73% still have the trough of the J-curve ahead of them. Its authors call the next 18 months decisive. 2 min readShort post
  2. Measuring AI impact on engineering: what to count and what to ignore Code volume, pull requests, usage: AI pushes up every number that is easy to count. A Stanford talk and DX data put the measured gain at around 10 percent, and it swings widely from company to company. What to measure instead, where the returns come from, and why things get worse before they get better. 13 min read
  3. Why faster coding does not guarantee faster delivery Productivity research measures task time, perceived savings, pull requests, and production flow, each in its own way. Read side by side, the measures show where the constraint moves. 5 min read

All 16 posts on Measuring AI impact

ClientsClient work

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Engineering and Product Leaders
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check