Me postulé a través de un reclutador. El proceso tomó 2 semanas. Acudí a una entrevista en Omada Health (Oakland, CA) en abr 2016
Entrevista
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.
Preguntas de entrevista [2]
Pregunta 1
Modify an admin interface to use sever-side pagination rather than client-side.
Thank you for providing us with detailed feedback on your interview experience- glad to hear it was a positive one! At Omada, we’re big fans of pair programming as well. We strive to communicate well, and find that pair programming allows peers to learn from one another and stay up-to-date with the code. Thanks again for your comments; it’s great to have you on board!
Solicitud
Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en Omada Health en mar 2025
Entrevista
Applied online, contacted by recruiter, did a 1st round with engineer director, then nothing. Not even a rejection. Why is it so hard for companies to treat candidates like people?
Preguntas de entrevista [1]
Pregunta 1
Mostly a back-and-forth conversation about challenges with engineering culture.
Me postulé a través de otra fuente. El proceso tomó 3 semanas. Acudí a una entrevista en Omada Health (New York, NY) en abr 2022
Entrevista
Process took about 3 weeks. First was a call with the external recruiter, followed by a call with the internal recruiter, then an interview with the engineering manager for the team for which I was interviewing.
He asked a series of intermediate React and API -centric questions. And then ended the interview with some behavioral questions and some time for me to ask him questions.
After that I had the option to participate in either two one hour virtual coding interviews or do a 4-hour take home. I chose the take home due to my busy schedule during work hours. The take home was a React app with a Flask backend that I had to build upon in a series of increasingly challenging tasks.
After I passed the take home, there was one hour follow up with two senior engineers who interactively reviewed the code with me.
This was followed with a 30 minute checkin with the original Engineering Manager I had met where he asked me a few more in depth behavioral questions geared toward collaboration and conflict resolution.
The final meeting was with the original internal recruiter who asked for feedback about the process and then told me I would be receiving an offer.
Overall - it was a fantastic experience. Everyone was kind, communicative, and super helpful. What I appreciated most is that they never once left me hanging. They were extremely on top of their communications.
Preguntas de entrevista [1]
Pregunta 1
Tell me about a time you were involved with conflict between peers. How did you handle it?
Me postulé a través de un reclutador. El proceso tomó 3 semanas. Acudí a una entrevista en Omada Health en abr 2022
Entrevista
Process took about 3 weeks. First was a call with the external recruiter, followed by a call with the internal recruiter, then an interview with the engineering manager for the team for which I was interviewing. He asked a series of intermediate React and API -centric questions. And then ended the interview with some behavioral questions and some time for me to ask him questions. After that I had the option to participate in either two one hour virtual coding interviews or do a 4-hour take home. I chose the take home due to my busy schedule during work hours. The take home was a React app with a Flask backend that I had to build upon in a series of increasingly challenging tasks. After I passed the take home, there was one hour follow up with two senior engineers who interactively reviewed the code with me. This was followed with a 30 minute checkin with the original Engineering Manager I had met where he asked me a few more in depth behavioral questions geared toward collaboration and conflict resolution. The final meeting was with the original internal recruiter who asked for feedback about the process and then told me I would be receiving an offer. Overall - it was a fantastic experience. Everyone was kind, communicative, and super helpful. What I appreciated most is that they never once left me hanging. They were extremely on top of their communications.
Preguntas de entrevista [1]
Pregunta 1
Tell me about a time you had to resolve an internal conflict at work.
