Had a phone screen with the hiring manager, which was less technically focused and more about getting a good feel for what Omada Health is all about and what they're looking for in this role, and giving them a good feel for what I'm looking for in my next position.
On-site consisted of two pairing sessions, team lunch, and another chat with the hiring manager. Each pairing session was 90-120 minutes long, which was enough time to understand the story, discuss its stakeholders and what would best satisfy their needs, and delve into the codebase to tackle the problem. In both cases, I did more of the risk than a normal pairing session would entail, but that's understandable.
Overall, I'm a big fan of pair programming. It's a great way to spread knowledge around, avoid silly coding mistakes, and socialize standards and practices. Plus, it provides a great forum for asking questions and, in the case of an interview, building rapport and gaining insight into the way a team functions in the real world-class as opposed to a series of whiteboarding sessions. This also means the opportunities for professional growth are plentiful.
At the end of the day, you need to be willing to engage in pair programming more than half the time, otherwise Omada Health is not the right place for you.
Modify an admin interface to use sever-side pagination rather than client-side.
Update a data import utility to comply with a newly-modified interface specification.
The following metrics were computed from 1 interview experience for the Omada Health Senior Software Engineer role in Oakland, California.
Omada Health's interview process for their Senior Software Engineer roles in Oakland, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Omada Health's Senior Software Engineer interview process in Oakland, California.