-45 minute phone screen with tech recruiter, pretty standard questions and overall a positive conversation -They ask for you to submit 3 references (one must be a prior manager) within 1 day of the initial phone screen -Take home assignment. Like others have mentioned, they said this would take 3-4 hours, however it took me more like 8-10 to really make it clear and concise with solid test coverage. I have 3 YOE with RoR and use it every day.
They give you a sample app and you have to add the following features to it, with specs and feature tests:
You won't have all the necessary libraries in your app, so a bit of work is needed to identify what is missing. The instructions were super clear, overall implementing these features was a good learning experience.
Now with added color:
The project README says you have 2 weeks to complete the assignment, however I was locked out of my project after 1 week, and had to reach out to the recruiter to get an "extension" (not an extension, the README says 2 weeks). I submitted my work, and did not hear anything for 2 weeks. I reached out again, and found that the team was unable to access my repo, but didn't bother to tell me. I went through the steps to share it again. I honestly think this specific interaction of the "extension" then the hiccup with submitting it is the reason I was rejected, not the 10 hours of coding or my 3 colleague references. A few days later I got a generic rejection with no specific feedback.
The exercise was worthwhile, however this entire process is a huge time investment, with ZERO effort on their end. The assignment took me 10 hours, and they didn't bother to tell me that they couldn't access it, let alone provide feedback. Asking 3 colleagues to submit detailed references for a company that hadn't even bothered to interview me (aside from the phone screen) was odd. This probably reads like a disgruntled candidate who got rejected, and that's definitely true, but as a candidate, I felt like I gave a lot, and they gave nothing. Every other company I've interviewed at has provided notes or feedback, so I'm not sure what their excuse is, but it left a sour taste in my mouth. I would discourage any friends or colleagues from applying here, there are plenty of other Rails shops that treat their candidates with more respect.
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.