Fairly standard interview for the beginning of the process which included two phone screens. One with their in-house recruiter, the other with the engineering manager.
Once on-site, two pairing sessions composed most of the day. One pairing session was to implement a real feature in their frontend codebase. The afternoon session was more backend centric.
Overall you get a good sense of how the team likes to work, a huge emphasis on pairing and TDD. You also get exposure to the codebase and their tooling/station for pairing which gives a good idea of what the job would be.
Between the two pairing sessions, you get to meet other members on the team over lunch and have a more casual environment. This is a good opportunity for questions about the team and the company.
At the end of the day, debrief with the engineering manager and then their recruiter.
Overall the process is pretty transparent and well structured, the recruiting team gives plenty of information on what to expect during the day.
The pairing session can be exhausting but you get to know two of your potential co-workers and get a sense of their experience or how they work. This is a pretty unique experience and you're almost interviewing them as much as they interview you.
Frontend development with React/Redux and backend development with Ruby on Rails.
The following metrics were computed from 1 interview experience for the Omada Health Senior Software Developer role in San Francisco, California.
Omada Health's interview process for their Senior Software Developer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Omada Health's Senior Software Developer interview process in San Francisco, California.