Moxe Health logo

Moxe Health Interview Questions
& Process

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

Based on 23 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
30.4% Positive experience

Which role are you interviewing for?

8 roles · 23 reports

Candidate interview experiences

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

Showing 4 of 23
Moxe Health logo
Moxe Health

Test Engineer

Engineering · a year ago

Mid Average Neutral experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Panel Onsite
Interview formats
Coding Behavioral

It was a pretty easy process overall. There were 4 rounds: a phone call, a technical coding challenge, a panel interview, and finally an interview with the CEO. While it might sound like a lot, they were really just trying to see if I was a good fit for the role. The coding part involved a couple of straightforward Python pytest problems, and the panel interview was mostly about going over my resume and talking about my past experiences.

Confirmed questions3 questions
  • Tell me about some simple coding exercises you've done related to test automation.
  • Can you talk about your experience as listed on your resume?
  • What other experiences can you share that are relevant to this role?
Moxe Health logo
Moxe Health

UI & UX Designer

Design · more than a year ago

Mid Average Neutral experience No offer 6 rounds
Interview process
Recruiter call Phone screen Presentation Technical screen Group Panel Offer Background check
Interview formats
Behavioral Presentation Technical Case Group

I applied in mid February and my interviewing process ended in mid June. I had my first interview in mid May. The first round was a 30 minute call with the Director of Product Management & was mostly informal. My second interview was another short call with the Lead Designer. My third call was a panel interview with a cross-functional team. My fourth interview was with the Chief Product Officer. My fifth interview was with the CEO. My sixth interview was with the Chief People Officer. They did not inform me until the 4th interview that the role required 3 days in the office which was not going to work for me. The people were nice enough during the interview, but when I expressed my hesitancy to come into the office, they completely ghosted me. I thought we could perhaps figure out a scenario where I could come in less often since the lead designer isn't even in the same office, but apparently we could not. I found the interview process to be entirely too long and I think them ghosting me was really unprofessional after I had committed several hours and 4 months of my life to talking with them.

Confirmed questions2 questions
  • Nothing out of the ordinary.
  • The interviews were not very challenging outside of a case study presentation to the cross functional team.
Moxe Health logo
Moxe Health

Software Engineer

Engineering · more than a year ago

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

The whole process took nearly two months. I passed two technical rounds, and then there were two rounds with C-suite. They suddenly asked for two reference letters, which they hadn't mentioned before. After I provided the references and completed the final two rounds, I was rejected a week later. Scheduling each round took about a week. The final round itself was delayed by two weeks because the interviewer didn't show up the first time, requiring rescheduling. It's puzzling why C-suite rounds were necessary, given their apparent busy schedules (often running late or not showing up at all). This suggests poor management, especially considering the time wasted. Asking for a former manager's reference adds to this. I'd avoid this company.

Confirmed questions3 questions
  • Could you answer some technical questions?
  • Tell me about a system design you've worked on.
  • Can you share some behavioral examples?
Moxe Health logo
Moxe Health

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience No offer 4 rounds
Interview process
Take home Technical screen Technical screen Onsite
Interview formats
Coding Technical Coding Technical

So the interview process was kinda all over the place and felt like a lot. It started with a take-home test that had some really particular C# questions. After that, I had a chat with a manager, then a pair programming session where we could use Java or C#. The last part was a typical whiteboarding interview. I didn't finish it all though, because having so many specific technical tests seemed like too much. Plus, they weren't great at communicating, like emailing me about interviews I'd already done or taking ages to reply. All that just felt like big red flags, so I decided not to continue with them.

Confirmed questions1 question
  • A coding assessment that initially included 3 problems: one involved a complex SQL query, another was specifically in C#, and the third was an algorithms problem that could be solved in any programming language.

Moxe Health Interview Questions

Quoted word for word from Moxe Health interview reports.

Can you design a function to check password strength in any programming language?

Read reports

Could you write a program to check the strength of a password?

Read reports

Could you write some small code to take a value from a text box and display the results?

Read reports

Can you tell me about a commercial product you admire?

Read report

Formats, difficulty and experience

Across all 23 Moxe Health interview reports.

Interview formats

Behavioral 37.7%
Technical 22.6%
Coding 15.1%
Presentation 7.5%
System Design 7.5%

Interview difficulty

Easy 17.4%
Average 78.3%
Difficult 4.3%

Candidate experience

Positive 30.4%
Negative 47.8%
Neutral 21.7%

Reports by job function

Sales 9
Engineering 9
Product 2
Marketing 1
Design 1
Consulting 1