
Mochi Health Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mochi Health.
Software Engineer
I applied directly. The first round was with the recruiter, a quick chat about my experience, the role, and salary expectations. She was a bit late but generally seemed nice and was quick to schedule the next steps. The second round was a 30-minute coding session with a junior frontend engineer using CoderPad, where I had to build a small React dropdown component. She was great and easy to talk to. The third round was another 30-minute session with a more senior frontend engineer, also via CoderPad, where the task was to call an API and display the data. I had some trouble with syntax, but the interviewer was pleasant and helped me find my bug. I didn't hear back after the third round. Given some reviews mentioning a toxic workplace and micromanaging CEO, it seems like I might have avoided a bad situation. Overall, it was a decent experience and good practice, so I won't hold the lack of follow-up against them.
- Could you build a dropdown component for selecting a medication?
- Please fetch data from the provided API and display it on the screen.
Software Engineer
The interview process wasn't too bad. I can't complain about the initial phone screening, although it could have been a bit clearer. Ultimately, it seems like a good place to work, and that's what I liked most about it.
- What salary do you expect?
Software Engineer
Started with a recruiter call, touched on a basic probability problem. Then, a quick 15min video chat with the CEO, who talked about the intense work hours (60-70 hrs/week), the company's tech setup, and asked some typical questions. Next, a tech interview with someone acting as the tech lead because the original interviewer couldn't make it. This 60min session wasn't what was expected – supposed to be leetcode, systems design, and work history, but it ran over and didn't get to the design part. Communication was pretty smooth and quick at first, but then things went quiet for a few business days. No replies to two follow-up requests, and then they sent a rejection without any feedback.
- A recruiter asked a basic probability question.
- An interviewer asked a standard, easy algorithm question.
Mochi Health Software Engineer Interview Questions
Quoted word for word from Mochi Health interview reports.
“Given a matrix where 1 represents a road and 0 represents a wall, how would you find a path from the top-left to the bottom-right corner?”
Read reports →“Can you build a component based on a Figma link?”
Read reports →“design a calculator”
Read reports →“Could you solve the LeetCode Easy problem 'Word Pattern'?”
Read reports →“Could you design an LRU Cache?”
Read report →“Can you explain how to pass props in React and how rendering works?”
Read report →“Could you build a dropdown component for selecting a medication?”
Read report →“What salary do you expect?”
Read report →“Can you elaborate on your seniority?”
Read report →Formats, difficulty and experience
Across all 13 Mochi Health interview reports.