Doximity Software Engineer Interview Questions
& Process

So, first there was a coding challenge. Then, we had a 90-minute pair programming session, followed by a 60-minute backend interview and a 60-minute frontend interview. I really liked meeting the engineers, they seemed like great people to work with. A weird thing was that they asked for references pretty early on, even before the technical interviews. It felt awkward asking my colleagues for references at that point, and I almost didn't do it, but HR said it was just a quick questionnaire. When my former manager and colleagues got the reference requests, they told me how intense it was, like a mini performance review. One colleague even said the reference software was 'kind of creepy,' it went full-screen and warned them about mouse tracking when they tried to check dates on LinkedIn. The final straw was getting a super enthusiastic email from HR a week later about 'an update from the team!' I thought it was an offer, but it was actually a really bad way to deliver a rejection with no real feedback, just that I 'have potential,' which felt a little patronizing given my 20+ years of experience.

I started with a recruiter phone call about my background and interest. Then, I got a take-home coding test. They got back to me in a few days saying they hired someone. The recruiter did call to let me know, which was nice.

I started with a phone screen with their Minister of Culture, which was a casual chat about my background and what I'm looking for in a company, plus Doximity's vibe. It felt pretty relaxed and I left feeling good. Then, I got a take-home coding challenge that wasn't timed. The task was to enhance a basic Rails app by adding three user stories. These stories involved a mix of front-end work and an algorithmic challenge that required thinking about performance and caching, fitting for a full-stack Rails role. Although this take-home took over 10 hours, more than other similar tasks I did, it felt like the most relevant exercise. After submitting it, I had a 1-on-1 with the VP of Engineering, my potential boss. We discussed tech ideas and company culture, but unfortunately, we ran out of time before getting into deep technical stuff. Because of that, he set up two more technical interviews with senior developers. These final interviews were friendly but covered a good range of deep technical topics. I felt well-prepared for Rails, JavaScript, and general web development. There was one algorithm question framed as a casual 'how would you solve this?' that I didn't have the most efficient answer for, but we explored options and got close to what they were looking for. Overall, it was a great experience, challenging but gave me a solid understanding of the team and Doximity's culture.