OM1 logo

OM1 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

7.6 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at OM1.

Showing 3 of 5
OM1 logo
OM1

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Technical Coding System Design

I had a few interviews, a couple of them technical, that went very well. I met several members of the team over Zoom and everyone seemed nice. I was even promised an offer by the recruiter who seemed very helpful. But then, inexplicably, I did not hear back from the company again. The term 'ghosted' that other reviewers have used is entirely appropriate. I got a bounced email message from the recruiter, and the hiring manager did not respond to my follow-up message. Truly bizarre, and disappointing.

Confirmed questions3 questions
  • Questions about database design
  • Questions about system design
  • A programming quiz
OM1 logo
OM1

Software Engineer

Engineering

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Presentation Onsite
Interview formats
Technical Coding System Design Presentation Behavioral

It started with a recruiter call, then I spoke with the hiring manager about the job and my interest. After that, I had 5 interviews, each about 30 minutes. One was a live coding test with two parts: SQL and programming. The SQL part was about basic joins and aggregate functions with group bys, not too hard if you've used SQL a lot. The programming part was also straightforward if you know how to code. Another interview focused on database design, like how to create tables and schemas that connect well and are efficient. This could be tough without much SQL experience. Then there was a system design interview where they asked me to design a real-world system. Another part was a project presentation, where I talked about a past work project. They said not to stress too much about preparing it, but I'd recommend putting in effort if you want the job. I reused some material from an old presentation but tailored it. The final interview was about role-specific questions. Each interview had at least 2-3 people. Overall, it felt like a fair and well-planned process.

Confirmed questions5 questions
  • Can you explain basic SQL concepts like joins and aggregate functions with group bys?
  • How would you design a database schema, focusing on efficient and sensible table connections?
  • Describe how you would design a real-world system.
OM1 logo
OM1

Software Engineer

Engineering

Mid Average Negative experience No offer 20 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Technical Coding Behavioral System Design

This was a really weird interview process, and honestly, it felt like a big waste of my time. I went through interviews at OM1 for a few months, talking to at least twenty different people. Seriously, I had around twenty separate virtual meetings. By the end, after meeting what felt like half the company, HR and the rest of the team just ghosted me. About 95% of the interviews involved the same questions, showing a lack of coordination between team members at different stages. The whole process seemed unorganized and poorly planned, with little consideration for the candidate. There was also a technical part where they insisted I use Python, even though my primary language is Javascript. This was the only place I've interviewed where I couldn't use my preferred language for a technical, algorithm-style question.

Confirmed questions2 questions
  • Determine a user's health score using a Python function (LeetCode style, easy-medium).
  • Whiteboard a database schema for a given scenario, showing one-to-many and many-to-one relationships, and join tables.

OM1 Software Engineer Interview Questions

Quoted word for word from OM1 interview reports.

Can you determine a patient's OM1 score using provided visit codes and a predefined list of condition types?

Read reports

How would you make sure all daily data files over 5 years load properly?

Read reports

How would you ensure that every one of the 5-years worth of daily data files loaded correctly?

Read reports

Can you explain basic SQL concepts like joins and aggregate functions with group bys?

Read reports

What steps would you take to confirm the data loaded is as expected?

Read report

How would you ensure all the data loaded was what you expected?

Read report

How would you design a database schema, focusing on efficient and sensible table connections?

Read report

Formats, difficulty and experience

Across all 5 OM1 interview reports.

Interview formats

Technical 26.3%
Coding 26.3%
System Design 21.1%
Behavioral 15.8%
Presentation 10.5%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Positive 40%
Negative 60%