Initial call with Engineering Manager to verify certain skills/job history First tech programming round, moderate difficulty LeetCode type problem Virtual on-site interviews: - Another coding round, much easier than the first one for some reason. They asked questions I might ask of an intern (I have 10+ years professional experience). - Behavioral interview. This one was pretty strange but they asked questions to (I guess) understand how you deal with ambiguity. - System design: this was a pretty basic design question on consuming a data stream and exposing it in streaming/batch formats. However, the system was pretty broad in scope so I asked a lot of clarifying questions.
The interviewer didn't seem very experienced at this question so he didn't have responses for most of my questions. As a result, I spent a lot of time trying to get info out of him so I could make judicial design choices and we ran out of time while doing the diagramming. A couple days later, I had feedback that there were "observations" during the design interview, so they wanted me to have a follow-up interview. The recruiter didn't have much info about what these "observations" were but it seems they weren't satisfied that I had asked so many requirements questions. The follow-up interview was much harder and ran the gamut of different topics. The interviewer rapid-fired questions on lots of different topics.
The topics include LeetCode style questions, CS 101 questions, system design, databases, APIs, and security. It seems to vary quite a lot depending on who interviews you.
The following metrics were computed from 10 interview experiences for the Paxos Senior Software Engineer role in United States.
Paxos's interview process for their Senior Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Paxos's Senior Software Engineer interview process in United States.