Great culture.
Flourishing stock.
Treats employees well.
No meeting Thursdays.
Friendly and skilled engineers.
Events and hackathons.
Compensation is great.
Managers are amazing; no micromanagement.
The monolithic codebase executed very poorly.
Very little attention was given to proper infrastructure choices.
Sales-driven "Band-Aid" solutions were encouraged.
There was very little room for self-improvement.
A huge chunk of time was wasted waiting for builds and dealing with merging code into production.
It was very risk-adverse. Moonshot projects were nonexistent on most teams, but were encouraged to be done in two-day hackathons.
Okta is growing big. Although Google has a monolith, what made Google so successful is their mindfulness to scaling properly. I feel as if Okta is lacking in this regard, which may be a bad sign.
Got an email from a recruiter after applying through the school career website. I completed a coding challenge, which was fairly easy, and was invited to an on-site interview. I met 3 engineers and 1 VP during the on-site. The interviews with the en
I applied through a referral. The process took over two weeks. First, the recruiter set up a call to walk me through the position and team. This was followed by a telephonic interview with one of their staff engineers. The interview was average, b
I was referred by an employee and liked what I saw and heard about the company. I had a 1-hour phone interview and a 2-hour coding challenge before an onsite interview that lasted 5 hours. Every step of the way, there was at least one question that m
Got an email from a recruiter after applying through the school career website. I completed a coding challenge, which was fairly easy, and was invited to an on-site interview. I met 3 engineers and 1 VP during the on-site. The interviews with the en
I applied through a referral. The process took over two weeks. First, the recruiter set up a call to walk me through the position and team. This was followed by a telephonic interview with one of their staff engineers. The interview was average, b
I was referred by an employee and liked what I saw and heard about the company. I had a 1-hour phone interview and a 2-hour coding challenge before an onsite interview that lasted 5 hours. Every step of the way, there was at least one question that m