Omada has a very health-oriented company culture. Unlike a lot of tech companies, they don't attempt to fill you with sugar and treats to make your job more bearable. There is a deep sense of pride shared by the company that pertains to making a positive, life-changing impact on people's lives. The mission feels holistically helpful to humans. There haven't really been any interpersonal issues that have arisen since I've been there; everyone gels pretty well.
While on the financial and business side, the company seems on track to continue growing; for the individuals in the company, it seems like growing within the company is not much of an option.
The company takes pride in a mostly-flat management structure, which encourages this feeling of lack of career mobility.
Also, the company is run very top-down, which can work with a less flat management structure, but in a wide company structure, it leads to very few decision makers controlling the workflow of many.
This is especially apparent within the product and design realms of the company as one or two key stakeholders structure workflow of the entire design team.
This issue trickles down further to the development team who constantly work with these disempowered and highly-controlled designers to create someone else's vision of the product.
This leads to much 'waiting on approval' and 'let me check with' conversations that lead to a lot of wasted time and effort throughout the company.
Empower and trust your employees and they will do wonders.
As you're scaling out, remember that reconsidering your position and role in the company is part of the scaling and that sometimes the bottleneck to improving company-wide lies in improving yourself.
Phone conversation with HR (30 minutes), phone conversation with manager (60 minutes), home assignment (one week to finish). Last one didn’t go well, on my personal laptop I don’t have an environment to implement part of the assignment, therefore I
The interview process was fairly standard: 1) Phone screening 2) Take home coding challenge: It's not that difficult, and you're given a week to complete. 3) Onsite: 2 pair programming sessions with 2 different engineers: Note that they have a re
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
Phone conversation with HR (30 minutes), phone conversation with manager (60 minutes), home assignment (one week to finish). Last one didn’t go well, on my personal laptop I don’t have an environment to implement part of the assignment, therefore I
The interview process was fairly standard: 1) Phone screening 2) Take home coding challenge: It's not that difficult, and you're given a week to complete. 3) Onsite: 2 pair programming sessions with 2 different engineers: Note that they have a re
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