# 2025 Engineering Benchmarks: Insights from 6.1M+ Pull Requests | LinearB Blog

> Explore insights from the 2025 Engineering Benchmarks Workshop on improving developer productivity, code quality, and alignment.

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._


```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://linearb.io/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://linearb.io/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "2025 Engineering Benchmarks: Insights from 6.1M+ Pull Requests",
      "item": "https://linearb.io/blog/2025-engineering-benchmarks-insights"
    }
  ]
}
```

[Home](https://linearb.io/)

/

[Blog](https://linearb.io/blog)

/

2025 Engineering Benchmarks: Insights from 6.1M+ Pull Requests

# 2025 Engineering Benchmarks: Insights from 6.1M+ Pull Requests

![Photo of Natalie Breuer](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Natalie_Breuer_e5764bbbac?_a=BAVMn6ID0)

By [Natalie Breuer](https://linearb.io/blog/2025-engineering-benchmarks-insights#natalie-breuer)

|

January 8, 2025

![2025_Engineering_Benchmarks_Insights_from_6_1_M_Pull_Requests_bbf2580e2b](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/2025_Engineering_Benchmarks_Insights_from_6_1_M_Pull_Requests_bbf2580e2b?_a=BAVMn6ID0)

The [2025 Engineering Benchmarks Workshop](https://linearb.io/resources/2025-engineering-benchmarks-insights) brought together thought leaders from MongoDB, CircleCI, and LinearB to discuss key trends shaping software development, with a focus on improving team performance, aligning processes with business goals, and leveraging data-driven insights to accelerate delivery cycles. With over 6.1 million pull requests analyzed across 3,000 teams, [this year’s benchmark report](https://linearb.io/resources/software-engineering-benchmarks-report) highlights actionable insights that help engineering leaders improve team performance and delivery predictability.

The conversation featured [Tara Hernandez](https://www.linkedin.com/in/tara-hernandez/), VP of Developer Productivity at MongoDB, [Rob Zuber](https://www.linkedin.com/in/robzuber/), CTO of CircleCI, and [Yishai Beeri](https://www.linkedin.com/in/yishaibeeri/), LinearB CTO, who shared their perspectives on pull request (PR) size, project management hygiene, and continuous deployment. Here, we’ll explore these insights and how they align with the 2025 Software Engineering Benchmarks Report.

## Why PR Size Drives Engineering Velocity

In our 2025 Benchmarks research, a major focus was correlating data to find insights into the PR lifecycle. One of the key takeaways we found was that PR Size is the most significant driver of engineering velocity. Smaller PRs with fewer lines of code are easier to review, less risky to merge, and contribute to faster [cycle times](https://linearb.io/blog/cycle-time). Larger PRs, in contrast, often require more in-depth scrutiny, delaying approval and increasing the likelihood of errors. 

![Hexbin plot showing the relationship between cycle time mean and PR size mean, visualizing data density using hexagonal bins for improved analysis of engineering metrics.](https://assets.linearb.io/image/upload/v1735945391/Cycle_Time_vs_PR_Size_4d9a2bb9fa.png)

As Tara Hernandez noted, "Supremely large PRs mean you probably didn’t break down the work. The takeaway is that it's a coaching opportunity for whoever produced that PR. In some team cases, I'm wondering if the correct response is to actually cancel that PR and say, 'Go back, try again, break it up,' as opposed to now someone is going to take a week to slug through this thousand file change."

This problem can create a cyclical issue: large PRs delay reviewers, and as Rob Zuber explained, "If I know no one’s going to touch my PR for three days, I might as well keep adding to it." This incremental addition during delays exacerbates the problem, leading to prolonged review times and compounding delays.

To improve team velocity, both speakers recommended adopting practices like:

* Breaking work into smaller, manageable pieces.
* Using automation to route PRs to the most relevant reviewers.
* Encouraging upfront planning to streamline the review process.

## The Balance Between Developer Productivity and Experience

PR maturity, a new metric in the 2025 Benchmarks Report, measures how well-prepared a PR is when submitted for review. Higher PR maturity correlates with faster merges and higher team velocity.

![Stacked bar chart analyzing merge rate against PR maturity ratio benchmarks, categorized into elite, strong, fair, and needs focus levels for comprehensive engineering insights.](https://assets.linearb.io/image/upload/v1735945392/Merge_Rate_vs_PR_Maturity_9b57d33096.png)

As Tara Hernandez explained, "If your PRs are pristine and get merged exactly as they were created, something’s wrong with the review process."

Rob Zuber added that the key to optimizing PR maturity lies in shared understanding and collaboration: "One of my favorite practices is putting up a sketch PR to gather feedback early, avoiding rework later." This approach encourages teams to balance productivity with long-term maintainability.

To achieve this balance, engineering leaders can:

* Foster high-trust environments where teams prioritize context-sharing.
* Use draft PRs or technical design documents to align reviewers before coding begins.
* Incorporate tools and workflows that reduce the burden of [context switching](https://linearb.io/blog/what-is-context-switching-and-how-does-it-hurt-productivity).

## Project Management Hygiene: Short-Term Speed vs. Long-Term Stability

Poor project management (PM) hygiene—such as unlinked branches and tasks without clear ownership—can lead to faster cycles but risks long-term [technical debt](https://linearb.io/blog/how-to-measure-technical-debt). The report shows that teams with lower PM hygiene often have shorter coding and merge times, but this speed can come at the cost of misaligned work and reduced quality.

"Too much process will always slow things down, but too little structure can create chaos," said Tara Hernandez. Rob Zuber expanded on this, highlighting how high-performing teams strike a balance: "In a super high-trust environment, people might skip tickets for small fixes, but over time, you need visibility to ensure alignment with business goals."

Key takeaways for improving PM hygiene include:

* Linking branches to issues for better traceability.
* Automating hygiene checks to reduce manual effort.
* Regularly reviewing processes to ensure they align with team growth and organizational goals.

## Faster Deployments and Lower Change Failure Rates: The Case for Continuous Deployment

One of the report’s most compelling insights is the correlation between faster cycle times and lower [change failure rates](https://linearb.io/blog/how-to-improve-change-failure-rate). Teams that deploy frequently and in smaller increments tend to have more stable systems.

![Bar chart comparing change failure rate (CFR) benchmarks with cycle time P75 distributions, segmented into elite, strong, fair, and needs focus categories for engineering performance evaluation](https://assets.linearb.io/image/upload/v1735945392/CFR_vs_Cycle_Time_1a0074f966.png)

Yishai Beeri likened this to riding a bike: "If you go too slowly, you’re more likely to fall over. Being able to change things fast and doing that all the time actually gets your production and your uptime to a better place."

Tara Hernandez shared a real-world example from her experience at a previous company, where the backend team transitioned from quarterly to daily deployments. "We started with just 60 tests and were failing almost every deploy," she explained. Over time, they scaled up to 2,500 tests and implemented robust monitoring, enabling reliable daily and even multiple daily deployments. The process highlighted the importance of building confidence through testing and cultural alignment within teams.

To embrace continuous deployment, engineering leaders should:

* Build robust automated testing frameworks to catch issues early.
* Adopt feature flags and progressive delivery practices to minimize risk.
* Encourage cultural shifts that prioritize frequent, small deployments.

## How to Leverage These Insights to Improve Developer Productivity 

The 2025 Engineering Benchmarks Report and insights from the workshop underscore the importance of data-driven decision-making in software development. To implement these insights, engineering leaders can focus on creating smaller, more manageable PRs, establish better traceability through linking branches to issues, and use automation to streamline workflows. Additionally, fostering a high-trust environment and adopting continuous deployment practices with robust testing can help teams achieve faster cycles and reduced failure rates. By focusing on smaller PRs, improving PM hygiene, balancing productivity with [developer experience](https://linearb.io/blog/developer-experience), and embracing continuous deployment, engineering leaders can drive significant improvements in team performance.

For a deeper dive into these insights, download the full 2025 Benchmarks Report or [schedule a demo](https://linearb.io/book-a-demo) of LinearB’s [SEI platform](https://linearb.io/blog/software-engineering-intelligence-101) to see how it can transform your engineering operations.

![Benchmarks Report 2025 3 _ 1200 x 628.png](https://assets.linearb.io/image/upload/v1733352461/Benchmarks_Report_2025_3_1200_x_628_0d52c848da.png)

## Improve developer productivity with LinearB

Find us on

[](https://www.linkedin.com/company/linearb)
[](https://devinterrupted.substack.com/)

![Natalie_Breuer_e5764bbbac](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Natalie_Breuer_e5764bbbac?_a=BAVMn6ID0)

## Natalie Breuer

Natalie Breuer, now a Senior Product Marketing Manager at LinearB, has been in the Developer Productivity Insights space since 2019\. A writer at heart, Natalie loves bringing technical topics to life with human stories – bridging the gap between data and storytelling.

## Your next read

[![Cover image for AI ROI comes from measuring engineering outcomes on day one](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_AI_ROI_comes_from_measuring_engineering_software_security_2400x1256_2c5eae0862?_a=BAVMn6ID0)](https://linearb.io/blog/kraken-nik-sudan-measure-ai-roi-engineering-outcomes)

Eng. Metrics

[AI ROI comes from measuring engineering outcomes on day one](https://linearb.io/blog/kraken-nik-sudan-measure-ai-roi-engineering-outcomes)

Kraken Engineering Operations Lead Nik Sudan details how to establish day-one data infrastructure to accurately measure AI ROI. Discover why raw token adoption...

[![Cover image for AI is rebuilding software delivery from SDLC to ADLC](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_AI_rebuilding_software_delivery_2400x1256_3fd5887e75?_a=BAVMn6ID0)](https://linearb.io/blog/sdlc-to-adlc-agentic-software-delivery-transformation)

Eng. Metrics

[AI is rebuilding software delivery from SDLC to ADLC](https://linearb.io/blog/sdlc-to-adlc-agentic-software-delivery-transformation)

Discover how engineering organizations are transitioning from the traditional SDLC to an Agentic Development Lifecycle (ADLC). Learn why rising token costs...

[![Cover image for 8 million pull requests reveal where engineering productivity breaks down](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_8_million_pull_requests_2400x1256_03724bfbb2?_a=BAVMn6ID0)](https://linearb.io/blog/8-million-prs-engineering-productivity)

Eng. Metrics

[8 million pull requests reveal where engineering productivity breaks down](https://linearb.io/blog/8-million-prs-engineering-productivity)

8.1M pull requests reveal the gap between AI adoption and engineering impact, and why code review is the bottleneck blocking real productivity gains.

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io/",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "2025 Engineering Benchmarks: Insights from 6.1M+ Pull Requests",
  "url": "https://linearb.io/blog/2025-engineering-benchmarks-insights",
  "author": {
    "@type": "Person",
    "name": "Natalie Breuer"
  },
  "datePublished": "2025-01-08T08:00:00.000Z",
  "dateModified": "2025-01-08T08:00:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1736371637/2025_Engineering_Benchmarks_Insights_from_6_1_M_Pull_Requests_bbf2580e2b.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "Explore insights from the 2025 Engineering Benchmarks Workshop on improving developer productivity, code quality, and alignment."
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Register now](https://linearb.io/event/engineering-productivity-gap)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB Library](https://linearb.io/library)
- [Engineering metrics](https://linearb.io/library/engineering-metrics)
- [Platform engineering](https://linearb.io/library/platform-engineering)
- [Engineering glossary](https://linearb.io/library/engineering-glossary)
- [Developer productivity](https://linearb.io/library/developer-productivity)
- [AI in software development](https://linearb.io/library/ai-in-software-development)
- [Engineering management](https://linearb.io/library/engineering-management)
- [Developer experience](https://linearb.io/library/developer-experience)
- [DevOps](https://linearb.io/library/devops)
- [Engineering operations and the context layer](https://linearb.io/library/engineering-operations)
- [Engineering efficiency](https://linearb.io/library/engineering-efficiency)
- [Software delivery](https://linearb.io/library/software-delivery)
- [Research and data](https://linearb.io/library/engineering-benchmarks-and-research)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)