
PagerDuty Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 193 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 193 reportsCandidate interview experiences
First-hand accounts from people who interviewed at PagerDuty.
Sales Engineer
The whole thing took about a month, with four main parts: first, there was this online test, then I had to do a mock presentation of a demo. The recruiter I talked to in Chile was super nice, really clear and helpful. The hiring manager was also great, full of energy, polite, and seemed to really get where I was coming from. After that, I chatted with the Director of Solution Consulting, which was also a good, professional conversation. The last step was the demo presentation, where I had to showcase how the platform brings value. I felt pretty good about it after the hiring manager's feedback, almost like I had the job. But then, just three days later, I got an automated rejection email, and after that, radio silence. My main issue isn't with the people, it's with how the process was handled. It needs to be more consistent for candidates who get to the final stages. We put in a lot of effort, taking time off work, rearranging schedules, and spending hours preparing demos. This stuff is important, and making the process fairer would be a big improvement. Also, if a candidate really impressed you and you open the same role later, it'd be good to think about them again, but that doesn't always happen. In my case, I did well with PagerDuty, so when the role came up again months later, I applied. Getting rejected right at the start was confusing. Still, I appreciate the chance and the chats I had with the team. Big thanks to my recruiter in Chile, amazing job!
- Can you discuss your background?
- What are your sales skills like?
- What's your experience in customer-facing roles?
Software Engineer
The hiring process was very efficient. It kicked off with a recruiter call, followed by a 30-minute chat with the hiring manager. Then, there were two one-hour technical interviews: one involved a live coding challenge (not LeetCode style) and the other focused on system design. The final stage was a 30-minute discussion with the senior manager overseeing the team. The recruiter was prompt, getting back within a day after each interview to set up the next step. The entire experience, from start to finish, took about three weeks and was quite smooth and pleasant throughout.
- Could you write a small program that utilizes their API?
Customer Success Manager
The interview process at PagerDuty was honestly one of the smoothest and most respectful I’ve experienced. It was clear, well-organized, and moved at a good pace — no unnecessary delays or surprises. It started with an intro call with the recruiter, who was super friendly and explained everything clearly. Then I had a few video interviews with the hiring manager and some team members. Everyone I spoke with was warm, thoughtful, and genuinely interested — not just in my experience, but also in who I am as a person. What stood out was how natural the conversations felt. It didn’t feel like I was being grilled — it felt more like mutual exploration. Communication was clear and consistent the whole way through, and I never felt left in the dark. Overall, it was a really positive experience — fast, transparent, and human.
- Can you tell us more about yourself and your background?
- What makes you a good fit for this role?
- What interests you about PagerDuty?
Technical Support Engineer
Started with a recruiter call that was high-energy and made a good first impression. It was mostly an overview of the job rather than an assessment of mutual fit. Then, there was a take-home challenge using their API, which was pretty straightforward and well-organized. After that, I had an interview with the hiring manager, but unexpectedly, another manager joined with their camera off. This was awkward because nobody mentioned it beforehand. The interview had behavioral questions and then a technical part with Linux commands and SSH access to a test server. When I asked about scripting or SSH usage in the role, they said it's rarely, if ever, part of the daily tasks. It was strange they tested on skills not really used in the job. I guess they might want a more technical person, but the test didn't seem to match the actual job requirements. I was already unsure about the role, and this interview confirmed it wasn't for me. Overall, I felt like I dodged a bullet because the hiring managers weren't welcoming, and the process lacked transparency.
- Can you share an instance where you had to manage a dissatisfied customer?
- Recount a time you were mistaken and explain how you managed that scenario.
PagerDuty Interview Questions
Quoted word for word from PagerDuty interview reports.
“Can you determine if a given set of parentheses is correctly closed?”
Read reports →“Can you add the ability to search for a dish using specific ingredients or by how long it takes to cook?”
Read reports →“Can you find pairs in an array that add up to 100?”
Read reports →“Can you write a script to find all unique pairs of numbers in a given set that sum up to a specific target value?”
Read reports →“How would you design a search engine given a snapshot of the web?”
Read report →“Can you pair up elements in an array that add up to 100?”
Read report →“Also, could you add a way to see a list of all priorities and how many tasks have each priority?”
Read report →“Could you write a script that creates new users with the PagerDuty API?”
Read report →“Could you implement a command-line interface tool that works with the PagerDuty API?”
Read report →Formats, difficulty and experience
Across all 193 PagerDuty interview reports.