Honey logo

Honey Software Engineer Interview Questions
& Process

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

Based on 24 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
75% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Honey.

Showing 3 of 24
Honey logo
Honey

Software Engineer

Engineering

Mid Easy Positive experience No offer 6 rounds
Interview process
Phone screen Technical screen Onsite
Interview formats
Technical Behavioral Coding

The interview journey kicked off with a phone screen conducted by the Director of Engineering, which included both technical and behavioral elements. Following that, there was a full day comprising five rounds of interviews, focusing on technical and behavioral aspects. Overall, the process felt quite positive, from the initial contact with the recruiter to the engineers and managers I interacted with. I ended up not getting the offer because of a headcount reduction, and also because my recent experience as a manager meant I hadn't been coding actively for a couple of years, which I felt was a reasonable explanation.

Confirmed questions4 questions
  • Could you explain why you're interested in Honey?
  • Write a function to detect a cycle in a linked list.
  • Implement a min stack data structure.
Honey logo
Honey

Software Engineer

Engineering

Intern Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Technical System Design Behavioral

So, it was a pretty standard interview process. First, a recruiter called me to chat about my background, skills, and why I was interested in Honey. Then, I got a link to a Codility test to check my basic coding and algorithms/data structures knowledge. After I passed that, I had an onsite interview. It was two back-to-back interviews, each about an hour long in the afternoon. The first one was a typical algorithm whiteboarding problem, so definitely brush up on Leetcode and Cracking the Coding Interview and get comfy writing code on a whiteboard. The second interview was more about systems design – they asked me what personal project I'd build in a weekend and how I'd implement it. Both interviews also touched on cultural fit and gave me time to ask questions at the end. The whole thing was super smooth, and the recruiters were always on top of things.

Confirmed questions1 question
  • What would you build if you had a weekend to create something?
Honey logo
Honey

Senior Software Developer

Engineering

Senior Difficult Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

Had a 30-minute call with the recruiter, and then I had to follow up with my portfolio. It felt very serious and formal. Had a 30-minute call with the recruiter, and then I had to follow up with my portfolio. It felt very serious and formal.

Confirmed questions2 questions
  • Tell me about your process.
  • Describe your management style.

Honey Software Engineer Interview Questions

Quoted word for word from Honey interview reports.

Implement the string to integer (atoi) function, covering edge cases like -2147000000 and 2147000000.

Read reports

For a given number, can you determine if the sum of the squares of its digits eventually results in 1?

Read reports

Can you find two numbers in an array that add up to a specific value?

Read report

Could you detail the various HTTP status code categories?

Read report

Formats, difficulty and experience

Across all 24 Honey interview reports.

Interview formats

Coding 29.6%
Behavioral 29.6%
Technical 29.6%
System Design 11.1%

Interview difficulty

Easy 33.3%
Average 58.3%
Difficult 8.3%

Candidate experience

Neutral 8.3%
Negative 16.7%
Positive 75%