My interview experience at PagerDuty was excellent. I was first contacted by a recruiting manager, who set up an initial phone interview with an engineering manager. That interview was a typical get-to-know-you phone chat, followed by a screen-shared coding challenge. The challenge was moderate in difficulty; she was more trying to gauge how well I communicate my thought process.
A few days later, I was invited to an onsite. This was scheduled for about 1.5 to 2 weeks out. The onsite lasted about 4 hours, with 4 separate interviews. The interviews ranged from conversational to different types of coding challenges. The great thing was that they let me use my own laptop and setup I was comfortable with, and I was allowed to use any online resources I needed. They don't want to know that you've memorized all of the methods, but rather that you are able to find what you need and communicate your process.
Two days after the interview, I was contacted with an offer.
I can't give any specifics; just make sure you are familiar with anything from API/Rails level to front-end.
The following metrics were computed from 6 interview experiences for the PagerDuty Software Engineer role in San Francisco, California.
PagerDuty's interview process for their Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for PagerDuty's Software Engineer interview process in San Francisco, California.