Doximity logo

Doximity Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 93 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
43% Positive experience

Which role are you interviewing for?

29 roles · 93 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Doximity.

Showing 4 of 93
Doximity logo
Doximity

Software Engineer

Engineering · half a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Background check Technical screen Technical screen Technical screen Offer
Interview formats
Coding Coding Technical Technical

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.

Confirmed questions1 question
  • Do you know GraphQL?
Doximity logo
Doximity

Software Engineer

Engineering · nearly a year ago

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Behavioral Coding

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.

Confirmed questions4 questions
  • Can you tell me about your experience?
  • What about this role sparked your interest?
  • Could you describe a difficult project you’ve undertaken?
Doximity logo
Doximity

Product Manager

Product · a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Take home Background check Offer
Interview formats
Case Behavioral

Had an initial screening call with HR. Then spoke with the hiring manager. After that, there were three more interviews with future teammates. They also had me do a case study and check my references. They ultimately said I didn't have the experience to lead an analytics team, which was weird because the job was for a product manager, not a lead or in analytics. Maybe they just picked someone they already knew. It felt disrespectful to go through all that, especially checking references, and then reject me for being unqualified. Big waste of my time.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Doximity logo
Doximity

Data Analyst

Analytics · more than a year ago

Entry Easy Negative experience Decline offer 5 rounds
Interview process
Recruiter call Take home Technical screen Technical screen Technical screen Technical screen
Interview formats
Coding Technical Technical Behavioral

It was very fast, completed in about 3 weeks. I had 5 interviews total. Started with a recruiter call, then a take-home assignment on Hackerrank (pro tip: look up the questions online; if you can't find them, don't waste time on it. They claim it's under 3 hours, but it took much longer. Your call though.). After that, it was 4 interviews back-to-back: the first was live coding with SQL and a review of the Hackerrank take-home, the second was a Python skills check (again, Google is your friend), the third was a product sense interview, and the final one was with the hiring manager, focusing mostly on behavioral questions and a lot of stats.

Confirmed questions4 questions
  • Can you tell me about a weakness you've worked to improve?
  • What's a weakness you've improved on?
  • Tell me about a weakness that you have improved on.

Doximity Interview Questions

Quoted word for word from Doximity interview reports.

What is the distinction between a class and a function in Python?

Read reports

What's the difference between a REST API and a GraphQL API?

Read reports

Could you highlight user mentions within the tweet body text? You'll need to get the ranges of those strings from the Twitter API and highlight them using an attributed string.

Read reports

For a given array of sorted integers, how would you identify if any two elements sum up to a specified target value?

Read reports

What is an asset pipeline in the context of web development?

Read report

Could you explain the distinction between a "lambda" and a "Proc" in Ruby?

Read report

Implement functionality to load data from a CSV file into your database using both a dedicated class and a seed file, ensuring distinct separation.

Read report

Can you explain what a generator and yield are in Python?

Read report

How would you fix the jittery scroll of tweets, given that images were being downloaded on the main thread?

Read report

Formats, difficulty and experience

Across all 93 Doximity interview reports.

Interview formats

Behavioral 34.5%
Technical 34%
Coding 21.4%
Presentation 4.9%
Other 2.4%

Interview difficulty

Easy 20.4%
Average 66.7%
Difficult 12.9%

Candidate experience

Positive 43%
Negative 40.9%
Neutral 16.1%

Reports by job function

Engineering 58
Sales 8
Analytics 6
Product 5
Marketing 5
Operations 4