Operations | Monitoring | ITSM | DevOps | Cloud

In 2022, we wrote about our engineering interview process to make it more transparent and accessible to candidates. A lot has changed since then: we've grown to 80 people across London, San Francisco, and New York, and naturally, our interview process has evolved too. We thought it was time for an update!

Incidents happen. Whether it’s a service outage, degraded performance, or an unexpected spike in errors, things will go wrong. The question isn’t if incidents will occur—it’s how quickly and effectively you can respond when they do. For years, incident response has been a mostly manual process: someone gets paged, scrambles to investigate, loops in the right people, and after some firefighting, hopefully resolves the issue before too many customers notice.

Since its launch in 2009, PagerDuty has been the go-to tool for organizations looking for a reliable paging and on-call management system. It’s been the operational backbone for anyone running an ‘always-on’ service, and it’s done the job well. Ask anyone about the product, and you’re all-but-guaranteed to hear the phrase “it’s incredibly reliable.” I agree. But reliability isn’t everything.

It's no secret that building a data-driven culture in a company is hard, but what is it exactly that makes this such a tricky endeavor? Contrary to popular belief, technology isn't the main hurdle. A recent survey reveals that only a quarter of respondents cite technological limitations as the primary obstacle to becoming data-driven.