Okta reviews

- support leadership has quite a bit of work to do in terms of demonstrating solid leadership. I’ve never worked anywhere with the total lack of transparency and seeing people in roles that have no business leading a support org who helps with most of corporate America’s infrastructure. These are nice people but there’s a total lack of direction, empathy, and sense of knowing what they’re doing. Coming to Okta I thought I’d be working under world class leadership (the VP is stellar but everyone below him is far from him). - workload can change on a dime. You can have a nice week or a couple days but recent changes feel like 3x the workload we used to have leading to a lot of burnout as you’re getting 5+ cases a day (these cases can take 2weeks+ to finish) - there’s an over emphasis on customer first where you’re expected to bend over backwards for every customer. Customers are not always right and we need to educate them better so we can all benefit in the end. Okta’s product is complex and with the legacy monolith of code, it’s not easy and fast to resolve some high priority issues. We need to help customers understand that. It’s good to care about customers but education will always win over handing everything over on a silver plate.

- Benefits (especially vacation) are very basic, even when they didn't have to be - to the point of being annoying sometimes - HR and workplace management are all in HQ (San Francisco), so getting their attention on many of the pain points around benefits/office issues can be very challenging - Work/life balance can be tricky with a Pacific-Time based team - Complicated dev environment & monolithic architecture of the product sometimes complicate the simplest of tasks - Not the fastest brand of agile is followed in the dev process