The interview process consisted of an initial phone screen, two remote sessions for coding/troubleshooting, and an on-site interview that lasted all day (10 - 5).
The on-site interview was broken into multiple sessions with two breaks, one hour for lunch and 30 minutes for coffee/tea in the late afternoon. Some of the sessions were q&a and some were coding and hands-on tasks.
I was asked a lot of questions about how I would troubleshoot a given problem, improve a given design, approach a given situation, or implement a given thing. I was also given one assignment to complete a set of tasks on unix and two coding assignments. Each assignment was limited to one hour.
The goal of the first coding assignment was to build a 4-page web app that took input from the user and interacted with a data store. The goal of the second coding assignment was to analyze web server logs and find the most popular path.
The following metrics were computed from 1 interview experience for the PagerDuty Dev Tools Engineer role in San Francisco, California.
PagerDuty's interview process for their Dev Tools Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for PagerDuty's Dev Tools Engineer interview process in San Francisco, California.