Divvy logo

Divvy Interview Questions
& Process

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

Based on 55 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
58.2% Positive experience

Which role are you interviewing for?

30 roles · 55 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Divvy.

Showing 4 of 55
Divvy logo
Divvy

Customer Success Manager

Sales · a year ago

Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Background check Offer
Interview formats
Behavioral Technical

I had a phone screen with the recruiter, which was pretty standard. Then, I interviewed with one of the CSM managers, and that interview was also pretty standard. After that, they ghosted me and never got back to me. I reached out to the recruiter multiple times for an update, and over a year later, they messaged me on LinkedIn to see if I was still interested in a CSM role.

Confirmed questions1 question
  • Can you describe a situation where a customer was very upset and explain how you managed it?
Divvy logo
Divvy

Cloud Systems Engineer

Engineering · more than a year ago

Entry Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Group Onsite Offer
Interview formats
Behavioral Technical Coding

The interview process was pretty simple and went through 5 stages: HR Screen, Department Head Interview, Group Team Interview, Director/VP Level Interview, and finally Negotiations. HR was great at keeping me updated, responding quickly and being available for calls. The interviews were 50% about culture/fit and 50% technical. The questions weren't tricky, and they encouraged asking for clarification if a question was unclear or had multiple answers. They stressed that honesty is important because the department is very knowledgeable, and you can't lie about your experience. Management has deep technical knowledge, not just business. They also emphasized culture fit, focusing on traits like reliability, being easy to talk to, respect, out-of-the-box thinking, appreciating small details, and understanding the importance of work-life balance for performance. I found it difficult mainly due to the technical questions, which required looking at the bigger picture and considering various approaches.

Confirmed questions8 questions
  • Given a specific scenario, how would you approach troubleshooting it?
  • Could you describe the high-level functionality of this Okta feature?
  • Could you detail the deep technical workings of this Okta feature?
Divvy logo
Divvy

Software Engineer

Engineering · more than a year ago

Senior Average Neutral experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen
Interview formats
Technical Coding System Design Technical

So I had an HR interview, then after that, 4 hour-long technical interviews. All the interviewers asked questions that seemed relevant and reasonable except for one. He showed up with a recursive gotcha question, the application of which I have never seen in any of the roles I have been in. It was also something for which there are abundant performant libraries out there. That particular interviewer looked bored the whole time. So everything seemed good and then it ended up a no-go. Weird experience overall.

Confirmed questions5 questions
  • Design an ETL system.
  • How would you perform certain operations on Python lists?
  • Solve a pancake-flipping or other basic LeetCode-style problem.
Divvy logo
Divvy

Software Engineer in Test

Engineering

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Take home Onsite Background check Offer
Interview formats
Behavioral Technical Presentation Other

I started with a recruiter call, then a phone screen to make sure I wasn't a total weirdo. A few days later, I had a zoom interview with the QA Manager where we talked about me and my experience and why I was interested in the job. Then I got some homework related to the job. The final interview had two parts: first, an interview with an engineering director and another Sr. SDET focusing on culture and experience questions. Second, an interview with the QA Manager, the Tech Lead for QA, and another Engineering manager where we reviewed my work, my process, how I solved problems, showcased my best work, and talked about areas for improvement. They also asked more culture and experience questions and gave me plenty of time to ask mine. After the final interview, the recruiter kept me updated every 3-5 days. Overall, I thought the process was great!

Confirmed questions1 question
  • How do you deal with conflict within a team?

Divvy Interview Questions

Quoted word for word from Divvy interview reports.

At what point is an invoice considered to be in collections?

Read reports

What are the pros and cons of buying versus selling a home?

Read reports

Could you describe the high-level functionality of this Okta feature?

Read report

What distinguishes an effective HR Business Partner from an ineffective one?

Read report

Can you find some coding assignment examples on GitHub?

Read report

Can you describe the qualities of a poor HR Business Partner?

Read report

Formats, difficulty and experience

Across all 55 Divvy interview reports.

Interview formats

Behavioral 48.5%
Technical 27.2%
Presentation 10.7%
Coding 5.8%
Other 4.9%

Interview difficulty

Easy 18.2%
Average 69.1%
Difficult 12.7%

Candidate experience

Positive 58.2%
Negative 32.7%
Neutral 9.1%

Reports by job function

Engineering 17
Sales 10
Operations 9
Marketing 8
Product 3
HR 3