There's a phone screen, followed by a coding challenge and then an onsite. The coding challenge was too difficult and I was scheduled for an onsite. The onsite consisted of a pair programming session where me and an employee attempted to complete a task. I thought I did fairly well during the session, but after it was over they told me that my second session was cancelled due to scheduling conflicts, which I'm not sure I believe as I was ultimately rejected.
My biggest issue with my experience with Omada Health, is that I'm not sure how I could've done better during the pair programming.
Unfortunately, the pair programming you do is whatever your interviewer is working on at the moment.
So while you do get to work on their codebase (which is pretty cool) there are no set questions for the interview.
The following metrics were computed from 2 interview experiences for the Omada Health Software Engineer role in San Francisco, California.
Omada Health's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Omada Health's Software Engineer interview process in San Francisco, California.