Madhive logo

Madhive 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.6 Rounds average
Average Typical difficulty
20% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Madhive.

Showing 3 of 5
Madhive logo
Madhive

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Coding Behavioral

Awesome experience! The interviewer was very attentive and to the point. Asked questions related to your level and stack. fyi look into the company before the intro call with the recruiter.

Confirmed questions1 question
  • Were there Leetcode style questions that were also conversational?
Madhive logo
Madhive

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Background check Offer
Interview formats
Technical Technical Technical

The interview process started with a recruiter call, followed by two architecture interviews and a coding interview. After that, they proceeded to check references. While I apparently aced all the interviews, with one interviewer even saying I was experienced enough to interview them, things got strange during the reference check. They initially asked for two references, which I provided. However, after speaking with them, they requested a reference from a previous manager. The process had been ongoing for months, and I knew they were leaning towards making an offer. Because I had other offers and needed a decision, I informed them about my timeline constraints. Madhive ultimately chose another candidate they felt had 'better experience.' This was a pretty poor experience overall, and I wouldn't work with a company that makes such demands on candidates, only to discard them when the candidate pushes back. Reading other reviews, I think I dodged a bullet.

Confirmed questions1 question
  • How would you architect an ETS pipeline using a messaging bus?
Madhive logo
Madhive

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Background check Technical screen Presentation
Interview formats
System Design Behavioral

So, I first talked to the recruiter, then the VP of Engineering. After that, I had a system design interview with two engineers. Then, they asked me to schedule a final chat with the CPO, which I did. It was a bit strange that there wasn't a coding interview. They had to reschedule the final interview because the CPO was traveling. About a week or two later, they let me know they went with someone they thought was a better fit.

Confirmed questions1 question
  • Could you design a stock market system to find the best deal given buy and sell orders?

Madhive Software Engineer Interview Questions

Quoted word for word from Madhive interview reports.

How would you architect an ETS pipeline using a messaging bus?

Read reports

Could you design a stock market system to find the best deal given buy and sell orders?

Read reports

Were there Leetcode style questions that were also conversational?

Read reports

Describe a problem you faced in the past and how you solved it.

Read reports

Formats, difficulty and experience

Across all 5 Madhive interview reports.

Interview formats

Behavioral 36.4%
Technical 27.3%
Coding 18.2%
System Design 18.2%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Neutral 20%
Positive 20%
Negative 60%