# Why Developers Are Disengaged (And How to Bring Them Back) | LinearB Blog

> Stack Overflow says 80% of developers feel disengaged. Learn how to boost happiness by reducing friction, addressing tech debt, and empowering teams to thrive.

_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": "Why Developers Are Disengaged (And How to Bring Them Back)",
      "item": "https://linearb.io/blog/why-developers-are-disengaged"
    }
  ]
}
```

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

/

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

/

Why Developers Are Disengaged (And How to Bring Them Back)

# Why Developers Are Disengaged (And How to Bring Them Back)

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

By [Dan Lines](https://linearb.io/blog/why-developers-are-disengaged#dan-lines)

|

January 2, 2025

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

If you’ve been following developer surveys like [the latest from Stack Overflow](https://survey.stackoverflow.co/2024/), you might already know the grim reality: [only 1 in 5 developers are genuinely happy at work.](https://devinterrupted.substack.com/p/are-only-20-of-devs-happy-stack-overflows) Let that sink in for a moment.

_20%!_

That means a staggering _80%_ of your team might be anywhere between mildly disengaged and actively plotting their escape. You can’t build culture if your people are constantly looking for a way out.

As someone who’s spent years navigating the trenches of software development and leadership, these stats hit hard. But they’re not exactly surprising.

## Why Developers Are Checked Out

Reflecting on these numbers, the first thought that comes to mind is, are we setting developers up to thrive, or just to survive? As a former engineer turned leader, I can tell you there are three pillars of developer happiness that organizations are consistently getting wrong:

* **Leadership Disconnect:** The hard truth is that a team leader makes or breaks your experience as a developer. If your manager isn’t advocating for you, cutting the noise, and protecting your focus, you’re fighting an uphill battle every single day.
* **Too Much Friction:** From bloated PR reviews to excruciatingly slow builds, the amount of friction in modern development workflows is killing productivity and morale. It’s like we’re making developers climb a mountain with ankle weights, and then wondering why they don’t reach the summit with enthusiasm.
* **Interesting Work:** Developers want to work on interesting challenges that lead to career advancement, not just slapping patches on last year’s spaghetti code or shipping “yet another corporate app” no one cares about. If your engineers are stuck in a grind of uninspiring tasks, of course they’re checking out.

## The Real Villain Developers Face Every Day Is Inefficiency

In my role at LinearB, we see it all the time: engineers bogged down by process debt. Think slow code reviews, redundant status meetings, and endless context-switching. It’s not glamorous to talk about, but these inefficiencies quietly erode job satisfaction.

Here’s the kicker: this isn’t just about “bad managers” or “lazy engineers.” It’s structural. If your systems and processes don’t allow developers to do their best work, you’ve failed before you’ve begun. Fixing it starts with uncovering friction, empowering your developers to unblock their workflows, and monitoring the right metrics to justify your investments into developer experience.

## Unmasking Technical Debt as a Business Problem

One of the survey’s findings that I couldn’t agree with more is how tech debt is the top frustration among developers. But here’s the thing: tech debt isn’t just some static issue you can sweep under the rug. It’s a direct consequence of prioritizing speed over sustainability.

If you’re a leader, the question isn’t whether to address tech debt but how to frame it in a way the business understands. Instead of calling it “technical debt,” frame it as “lost time to market” or “future revenue risk.” Suddenly, it’s not a developer gripe, it’s a business problem. 

The rest of the business isn’t interested in improving developer experience. As an engineering leader, it’s your job to articulate how reducing tech debt leads to efficiency improvements and productivity gains. This is how you make space for your developers to focus on improving their quality of life.

## What Needs to Change

If we want happier, more engaged engineers, here’s the playbook:

1. **Fight for Focus:** Engineering leaders need to shield developers from churn and advocate for uninterrupted coding time. This isn’t just about productivity, it’s about creating an environment where people can do their best work. Reduce toil and invest in AI-powered workflows to keep teams focused on what matters.
2. **Measure What Matters:** Stop obsessing over metrics like “velocity.” Instead, focus on indicators like pull request throughput, quality, and predictability to signal healthy workflows.
3. **Empower Managers:** Too often, team leads are thrown into the deep end with no training or support. These are your frontline leaders. Invest in their growth if you want better results across the board, particularly if you have a ton of new managers.

## The Takeaway

For every engineering leader reading this: the 20% engagement stat isn’t just a red flag, it’s a call to action. Your developers deserve better than a career defined by slow feedback loops, bureaucratic roadblocks, and uninspired projects. And honestly? So does your business.

The fix isn’t easy, but it’s simple. Remove the blockers. Advocate for your team. Treat developer satisfaction like the strategic priority it is. The companies that do will thrive, while others struggle to keep up.

## Improve developer productivity with LinearB

Find us on

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

## Your next read

[![Cover image for AI as a value multiplier: a human-centric approach to engineering leadership](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Servant_Leadership_2400x1256_0cfd4e2a0c?_a=BAVMn6ID0)](https://linearb.io/blog/ai-as-value-multiplier-human-centric-leadership)

Leadership

[AI as a value multiplier: a human-centric approach to engineering leadership](https://linearb.io/blog/ai-as-value-multiplier-human-centric-leadership)

Super.com's Matt Culver explains why AI should be used as a value multiplier, not a cost-cutter, advocating for a human-centric approach to engineering...

[![Cover image for The Moneyball approach to engineering leadership](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Balancing_Technical_Depth_2400x1256_b56d93a733?_a=BAVMn6ID0)](https://linearb.io/blog/moneyball-approach-engineering-leadership)

Leadership

[The Moneyball approach to engineering leadership](https://linearb.io/blog/moneyball-approach-engineering-leadership)

Rethink engineering leadership with Transcend's Minh Nguyen and learn how to balance hands-on technical work with strategic leadership, communicate with a...

[![Cover image for Strategic lessons from Google on improving engineering teams](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Strategic_Lessons_From_Google_2400x1256_1_cd28b7242d?_a=BAVMn6ID0)](https://linearb.io/blog/strategic-lessons-google-engineering-teams)

Leadership

[Strategic lessons from Google on improving engineering teams](https://linearb.io/blog/strategic-lessons-google-engineering-teams)

Learn key lessons from Google on aligning engineering with business goals, boosting developer productivity, and building sustainable team culture.

## 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": "Why Developers Are Disengaged (And How to Bring Them Back)",
  "url": "https://linearb.io/blog/why-developers-are-disengaged",
  "author": {
    "@type": "Person",
    "name": "Dan Lines"
  },
  "datePublished": "2025-01-02T08:00:00.000Z",
  "dateModified": "2025-01-02T08:00:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1734652281/Why_Developers_Are_Disengaged_And_How_to_Bring_Them_Back_3665805ff7.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "Stack Overflow says 80% of developers feel disengaged. Learn how to boost happiness by reducing friction, addressing tech debt, and empowering teams to thrive."
}
```

## 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)
- [Watch 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)