Taro Logo

Software Engineer Interview Experience - United States

April 12, 2019
Negative ExperienceNo Offer

Process

Talked with their recruiter on the phone for 45 minutes. Nice conversation, given a backstory on the company.

Next went on to the project which was a suggested 2-4 hour assignment allotted 2 weeks of time to complete. It's using an outdated and insecure version of the chosen computer language with a few other minor issues due to how old and stale the starting project is. I asked some questions regarding some of the ambiguity but it took almost a whole week for an engineer to say they don't really like to answer questions, preferring applicants to fill the blanks themselves.

A few days after submitting the assignment, I received a generic rejection email w/o any feedback specific to my application. While they have no obligation to inform you how you scored on their rubric, having an actual rubric, telling the applicant about the rubric, and then refusing to share that detailed information doesn't seem very productive. I believed I had paid close attention to the factors they had stated were important to the project but now I'll never know what to improve on or what I misunderstood.

Questions

What's your most recent project?

Was this helpful?

Interview Statistics

The following metrics were computed from 28 interview experiences for the Doximity Software Engineer role in United States.

Success Rate

32%
Pass Rate

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.

Experience Rating

Positive43%
Neutral14%
Negative43%

Candidates reported having mixed feelings for Doximity's Software Engineer interview process in United States.

Doximity Work Experiences