Komodo Health logo

Komodo Health Software Engineer Interview Questions
& Process

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

Based on 17 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
52.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Komodo Health.

Showing 3 of 17
Komodo Health logo
Komodo Health

Software Engineer

Engineering · more than a year ago

Executive Average Negative experience No offer 1 round
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical

I interviewed with an executive who asked a bunch of high-level questions. When I tried to explain a project from my resume for a major telecom company, the executive responded with disbelief. At one point, the executive asked, "What did YOU work on?" I told them I worked on the project I just described and asked if they had any follow-up questions. The executive just repeated the same questions. It was a really weird interview; I'm not sure why, despite my detailed explanations, they kept asking the same things and implying I'd never built an API or set up a Kafka consumer. I wouldn't recommend interviewing here.

Confirmed questions2 questions
  • Can you tell me about your past experience?
  • What did YOU work on?
Komodo Health logo
Komodo Health

Software Engineer

Engineering

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Group Presentation Offer
Interview formats
System Design Coding Behavioral Technical

The recruiters reached out first, and the whole thing was super smooth from start to finish. They really focused on being open and communicative, so I never felt like I was guessing what was coming next. The rounds included a chat with the Hiring Manager, a whiteboard session for System Design, and then a Coding challenge where I had to work on a feature within an existing codebase. After that, there was a Product discussion with the Product Manager. All the technical tasks were practical and actually related to the job, not some tricky, out-there problems. Super practical and to the point. What stood out was how clearly the team explained what they were looking for, step-by-step, with clear ways they'd evaluate things. It all happened pretty fast; I got the offer in under two weeks from when they first contacted me.

Confirmed questions3 questions
  • Could you design a system?
  • Could you implement a feature for an existing codebase?
  • Let's discuss the product.
Komodo Health logo
Komodo Health

Software Engineer

Engineering

Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical System Design Coding Behavioral

It was a pretty standard interview process. First, I had a call with the recruiter. Then, I had a technical chat with an engineer. Finally, there was a round of interviews that covered design, coding, and behavioral aspects. It wasn't an overly difficult interview. It did take a while to get feedback though. Based on the feedback, it seemed like the TPM felt I wasn't a fit, maybe because my current employer has different processes or there was a communication issue. I wish they had followed up to clarify any concerns. The official reason given was that they wanted someone more backend focused, which is odd because they were upfront about wanting someone more front-end leaning. They never really tested my backend skills, despite my extensive experience in that area. It felt like an excuse. The whole experience left a bad taste in my mouth. The recruiters were great and I felt bad telling them this, but I felt like the company wasted my time by not being clear about their needs and expectations. Being honest would have been better, and Komodo Health really needs to work on being more transparent with candidates. I'll just consider it growing pains.

Confirmed questions1 question
  • The questions were all easy, including a coding question similar to a medium LeetCode problem.

Komodo Health Software Engineer Interview Questions

Quoted word for word from Komodo Health interview reports.

Given a structure represented by a list of heights, calculate the amount of water it can hold.

Read reports

Could you provide an SQL query to join two tables to get the desired data?

Read reports

Describe how you would design an application to schedule a programming task at a specific interval, like a cron job.

Read report

What are your thoughts on Algorithms and databases from a technical perspective?

Read report

Can you answer some technical questions about Algorithms and databases?

Read report

Formats, difficulty and experience

Across all 17 Komodo Health interview reports.

Interview formats

Behavioral 36.4%
Technical 29.5%
Coding 20.5%
System Design 13.6%

Interview difficulty

Easy 23.5%
Average 70.6%
Difficult 5.9%

Candidate experience

Positive 52.9%
Negative 41.2%
Neutral 5.9%