divvyDOSE logo

divvyDOSE Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
0% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at divvyDOSE.

Showing 3 of 5
divvyDOSE logo
divvyDOSE

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience Decline offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding Presentation Behavioral

The interview process began with an initial screen with an engineering manager, followed by an open-ended take-home assignment. After that, there was an engineering interview that had little to do with the take-home. The final stage was a 3-hour block of several back-to-back interviews. Feedback between rounds was minimal, requiring self-assessment to guide preparation. The take-home involved creating a Flask app to integrate GitHub and Bitbucket APIs for combined profile data. Due to ambiguous instructions, I limited my time, expecting to discuss limitations and future steps for a real service. However, the take-home and its potential expansion were barely touched upon in the interviews. I later learned that my take-home submission led to a decision to down-level the position without informing me, which I would have used to withdraw had I known about the discrepancy. A friend also mentioned DEI issues at the company, given the extensive unpaid work expected during the interview process.

Confirmed questions1 question
  • How would you approach scaling an application?
divvyDOSE logo
divvyDOSE

Software Engineer

Engineering · more than a year ago

Entry Easy Negative experience No offer 3 rounds
Interview process
Phone screen Technical screen Onsite
Interview formats
Technical Coding

The interview process started with an initial phone screen, followed by an API implementation task, and concluded with a final 3-hour in-person round. Honestly, it felt like a complete waste of time because the interviewers seemed unsure of what they were looking for, ultimately wasting both their time and mine. The reason given for not proceeding was the typical 'not ready to pull the trigger.'

Confirmed questions1 question
  • API related questions
divvyDOSE logo
divvyDOSE

Software Engineer

Engineering

Senior Average Neutral experience No offer 5 rounds
Interview process
Phone screen Technical screen Take home Onsite Background check Offer
Interview formats
Technical Coding Behavioral

The hiring process started with a phone screen. If successful, the CTO would call, followed by a coding challenge. Positive results from the coding challenge led to an in-person interview, which lasted about 4 hours. The in-person part was quite intense, involving an hour of rapid-fire questions from three managers. Then, there were meetings for 'culture compatibility' and a detailed technical discussion about the coding challenge. I felt prepared because I have 7 years of industry experience. The CTO mentioned feedback would be provided, even if not selected. I got an email the next day stating they were moving forward with other candidates. Despite assurances of feedback, I haven't received any after requesting it twice, and it feels like I've been ghosted. I'm unsure about what this company is looking for.

Confirmed questions1 question
  • What has been your experience with AWS?

divvyDOSE Software Engineer Interview Questions

Quoted word for word from divvyDOSE interview reports.

Could you create and deploy a responsive webpage that uses the Google Maps API to show pharmacies within a certain radius?

Read reports

Formats, difficulty and experience

Across all 5 divvyDOSE interview reports.

Interview formats

Technical 38.5%
Coding 38.5%
Behavioral 15.4%
Presentation 7.7%

Interview difficulty

Easy 40%
Average 60%
Difficult 0%

Candidate experience

Negative 80%
Neutral 20%