The process started with a standard phone screen from the recruiter. About a week later I had a phone interview with the hiring manager with standard behavioral questions, e.g. regarding working in a team and software developer successes and failures.
The on-site interview was three segments plus lunch. A 1:1 session with the hiring manager drilling in on more technical discussions regarding SW architecture and process. There was a live coding challenge where you can use any environment you want. There was also a database modeling session given a product idea to implement. The latter two sessions included remote team members dialing in. The interview ended with a brief overview of the company and benefits with the recruiter.
Overall I thought the process was straightforward and fair, though I had wished there was more time to dive into what the engineering teams were actually working on. I also generally got the vibe that interviewers other than the hiring manager were not super invested in the interview; I never heard a couple of the folks speak during the sessions.
What design considerations should you incorporate for a scalable, HA service?
Describe a project that you worked on and that didn't go well.
When would you use functional vs. object oriented programming?
The following metrics were computed from 1 interview experience for the PagerDuty Senior Software Engineer role in Atlanta, Georgia.
PagerDuty's interview process for their Senior Software Engineer roles in Atlanta, Georgia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for PagerDuty's Senior Software Engineer interview process in Atlanta, Georgia.