The interview process is planned but the interviews themselves are unstructured. I began with an email connection from someone non-technical and ended up on the typical culture fit/what are you looking for call. I was then scheduled for three interviews about a day apart. The first two were with senior engineers and the last with the VP of engineering. Finally, I spoke with the lead architect.
The scheduling was a bit ad-hoc which was the only negative part of the experience. I found myself moving things around in my schedule to make time for the interviews as I didn't have the full schedule up front. I suppose some of this comes from them needing to decide to move forward with you as a candidate.
Otherwise, I enjoyed the unstructured style. It proved me an opportunity to dive deep on my expert subjects and have a back-and-forth talk about my weaker skills. It was very low pressure and certainly mixed technical with "would I grab a beer with this guy?" questions. One of the sessions involved a shared coding session.
How would you go about developing a system that renders a news feed with comments and the ability to comment on comments?
The following metrics were computed from 28 interview experiences for the Doximity Software Engineer role in United States.
Doximity's interview process for their Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Doximity's Software Engineer interview process in United States.