Companies that use Pagerduty

Source: Analysis of job postings that mention Pagerduty (using the Bloomberry Jobs API)

I noticed that PagerDuty buyers are overwhelmingly technical operations leaders responsible for reliability, incident management, and service delivery. Director of DevOps/SRE roles make up 20% of leadership positions, followed by Directors of Technical Operations at 15% and Heads of Customer Support at 12%. These leaders are focused on building resilient infrastructure, managing incidents at scale, and maintaining always-on digital experiences. Their hiring priorities center on operational excellence, automation, and reducing mean time to resolution.

The day-to-day users span SRE teams, DevOps engineers, NOC operators, and technical support staff who handle incident response and service reliability. Individual contributor roles like Senior Site Reliability Engineers and DevOps Engineers represent 20% of total postings, working hands-on with monitoring tools, alert management, and on-call rotations. These practitioners integrate PagerDuty into their observability stack alongside tools like Datadog, Prometheus, and Splunk to manage critical production incidents.

The core pain point across these organizations is incident fatigue and the need for faster resolution. Companies repeatedly mention goals like "managing incidents at scale," "ensuring timely response and effective resolution," and building "scalable, repeatable motion" for service delivery. One posting emphasized the need to "compress sales cycles" while another highlighted "reducing MTTR with automation." These teams are moving from reactive firefighting to proactive reliability engineering, seeking tools that enable them to "prevent issues before customers notice" and maintain service availability for millions of users.

Source: Analysis of Linkedin bios of 5,729 companies that use Pagerduty

I noticed that PagerDuty's typical customers are companies building and operating complex technical infrastructure that absolutely cannot go down. These aren't just software companies writing code. They're organizations running real-time systems where downtime has immediate, tangible consequences: healthcare providers managing patient care, financial institutions processing transactions, manufacturers coordinating production lines, retailers handling e-commerce at scale, and infrastructure companies keeping utilities and communications running. Many are in highly regulated industries where uptime isn't just about revenue but about compliance and safety.

The company mix skews heavily toward mature, established enterprises. I count numerous Fortune 500 companies and publicly traded organizations like Progressive Insurance, General Motors, UnitedHealth Group, and Applied Materials. However, there's also a significant cohort of well-funded growth-stage companies, particularly Series B through Series E startups with substantial teams and real operational scale. The common thread isn't age but operational maturity: even the younger companies have moved beyond MVP stage into running production systems that serve thousands or millions of end users.

Source: Analysis of tech stacks from 5,729 companies that use Pagerduty

I noticed that PagerDuty users are predominantly mature, cloud-native technology companies with sophisticated DevOps practices and enterprise security requirements. The extreme correlation with Docker Hub tells me these are software companies running containerized infrastructure at scale, while the strong presence of enterprise identity management tools like Okta and OneLogin indicates they're handling complex security and compliance needs across distributed teams.

The pairing of PagerDuty with Docker Hub makes perfect sense because companies running microservices in containers need robust incident management to handle the complexity of distributed systems. When you have hundreds of services running across multiple environments, you need automated alerting and on-call workflows. The Okta correlation is equally telling. Companies investing in enterprise SSO are managing large engineering teams with role-based access controls, which aligns with the kind of organization that needs structured incident response. Golinks appearing so frequently suggests these companies value engineering productivity and have developed internal tooling cultures. These are teams that build custom workflows and internal platforms.

The full stack reveals these are mature, likely post-Series B companies with substantial engineering headcount. They're definitely product-led given the engineering-centric tooling, but the presence of Qualtrics and Adobe Audience Manager suggests they've evolved to have sophisticated go-to-market functions too. They're collecting customer feedback systematically and running targeted marketing campaigns, which indicates they've moved beyond pure PLG into enterprise sales motion. The combination points to companies in growth mode that have proven product-market fit and are now scaling both their product and their customer acquisition.