Week 1 - Initial call with recruiter for availability, etc.
Week 1 - Second call with Eng. Manager to talk almost about life story, projects you worked on, your successes, challenges, etc.
Week 2 - do a take home coding challenge or do it on site - I chose take-home
Week 3 - on site interview with product manager, White boarding with engineer, code review with engineer, closing remarks with Recruiter
The product manager will talk about a hypothetical scenario to gauge how you will handle a product
The white boarding will ask you to design a system based on a requirement they will have
The code review portion will involve examining the take-home coding challenge - if you did not do take home you would likely write this on site. The review will ask why you did certain things, issues you encountered, and may ask you to make small changes.
Overall, the interview process is very well laid out and organized and not overly complicated in terms of what you are expected to know about algorithms or data structures but how you do the white boarding will play a critical role in how well you understand the importance of these things when it comes to system design.
Describe a situation where you felt you weren't right at something and how did you handle it.
How do you work with other team members, and how you helped junior developers.
The following metrics were computed from 2 interview experiences for the PagerDuty Senior Software Engineer role in Toronto, Canada.
PagerDuty's interview process for their Senior Software Engineer roles in Toronto, Canada is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for PagerDuty's Senior Software Engineer interview process in Toronto, Canada.