Omada Health Software Engineer Interview Questions
& Process

This was my second time interviewing for a SWE II role, this time for a different team. The entire process took about two months. It included a 30-minute hiring manager chat, a take-home assignment to be completed in 3 business days, a 90-minute session covering code review and system design, and a final 30-minute meeting with a hiring manager. I felt a bit caught off guard during the system design part because some questions were posed where the interviewers themselves admitted they didn't have answers, as their team is currently facing challenges with those exact issues. The final interview phase was quite disorganized. Between my system design interview and the subsequent hiring manager call, I was informed that the role had shifted, and I would now be interviewing with a new hiring manager for a different team. This new manager had only been with the company for a month and struggled to answer most of my questions, making the interaction feel awkward and unproductive. They also expressed uncertainty about whether the role would ultimately land on their team. Following this, I got rejected.

The interview process was pretty slick: there was a Recruiter Call, then a Chat with the Hiring Manager, followed by a Coding Challenge, a Design Discussion, and then a Behavioral / Coffee Chat. After that, there was a Director Interview, and finally a Follow Up with the Hiring Manager. These were all the discussions, not necessarily different interview times / slots. The process moved quickly, and didn't feel overly time-consuming or wasteful. I felt like every interview gave Omada insights into me as a developer and person. I was also able to ask questions and get a good feel for the culture and problems they were solving.

It was a pretty standard interview to start, with two phone screens. First, I talked to their recruiter, and then I had a chat with the engineering manager. When I got on-site, the main part of the day involved two pairing sessions. The first one was about adding a real feature to their frontend code. The afternoon session was more focused on the backend. It really gives you a good feel for how the team operates, with a big focus on pairing and TDD. You also get to see the codebase and their setup for pairing, which helps you understand the job better. In between the pairing sessions, I met some other team members during lunch, which was more relaxed. It was a good chance to ask about the team and the company. To wrap up the day, I had a debrief with the engineering manager and then the recruiter. All in all, the process felt quite clear and organized, and the recruiting team gave good info on what to expect. The pairing sessions can be tiring, but you get to know two potential colleagues and see how they work. It's a pretty unique experience, and it felt like I was interviewing them as much as they were interviewing me.