Five distinct rounds and three references: an initial screen with the recruiter, a discussion of my background with the department director, and three interviews with members of the team, most of which focused on familiarity with basic terminology and best practices. Full process took about a month.
Less of the interview than I'd like was spent on understanding how I think and approach problems, and more was spent on ensuring I know what ACID transactions and load balancing are. I still got a very positive impression of the team and work environment.
I was verbally offered a role by the recruiter after my interviews and reference checks, but was called the following day to inform me that the requisition for the role had been put on hold and they would not be moving forward.
Hiring freezes happen, and I don't begrudge the rank-and-file people I spoke to, but it's a very negative and somewhat unprofessional experience to bring someone through an entire hiring pipeline only to rescind a verbal offer due to a freeze rather than allow those already in the pipeline to continue through. I felt that my time had been wasted.
What is DNS? What differentiates a REST API from a GraphQL API? How would you debug a sudden slowdown of an endpoint in a service?
The following metrics were computed from 1 interview experience for the Doximity Senior Site Reliability Engineer role in United States.
Doximity's interview process for their Senior Site Reliability Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Doximity's Senior Site Reliability Engineer interview process in United States.