On-call never shows up in exit interviews. But across half a dozen consulting engagements, I've watched it quietly hollow out engineering teams. The pattern is always the same, and it's always fixable.
- Published On
on call
- A client's on-call rotation was burning people out — not because of real incidents, but because of noise. Here's how we cut alerts by 87% without missing anything that actually required a human.
- Published On
Tags
consulting (81)debugging (35)architecture (32)developer-experience (24)reliability (20)devops (14)ai (12)performance (11)observability (9)code-quality (7)security (6)databases (6)microservices (6)postgres (6)engineering-culture (6)technical-debt (6)database (6)kubernetes (5)api-design (4)ci-cd (4)infrastructure (4)testing (4)productivity (4)nodejs (3)dependencies (3)javascript (3)postgresql (3)tooling (3)on-call (2)distributed-systems (2)refactoring (2)configuration (2)resilience (2)cost-optimization (2)code-review (2)deployment (2)opentelemetry (2)monitoring (2)goals (2)github-actions (1)data-integrity (1)retention (1)authentication (1)node.js (1)data (1)websockets (1)project-management (1)mcp (1)finops (1)multi-tenant (1)authorization (1)terraform (1)dns (1)opinion (1)memory (1)error-handling (1)secrets-management (1)webhooks (1)containers (1)environments (1)queues (1)cloud (1)orm (1)alerting (1)incident-management (1)typescript (1)caching (1)platform-engineering (1)feature-flags (1)api (1)contracts (1)logging (1)mongodb (1)migration (1)workflow (1)nestjs (1)angular (1)sandbox (1)sonarcube (1)learning (1)journey (1)mdx (1)