My Okta interview for a Staff Frontend Engineer role started like a short technical slot but dragged on to a full hour. It was scheduled as a 30-minute session and ran long, using a BrightHire recorder setup alongside a coding environment (CodeSignal). It felt very evaluation-heavy and ended with a rejection.
The technical part centered on a coding + discussion format, and the whole interaction had a tense, “talk-through-the-work” energy rather than a calm collaboration. What stood out most was how the conversation broadened in scope during the session, so it wasn’t just narrowly about frontend-level implementation details. Even though I tried to stay on track, the way the discussion evolved made it harder to predict exactly what they were prioritizing.
3 months ago
Easy Negative Bengaluru
I interviewed for a Staff Frontend Engineer role at Okta and the overall experience felt extremely negative. The session was scheduled for 30 minutes but stretched to a full hour, and the first sign of trouble was basic professionalism: the interviewer joined late, started immediately, and basically said they weren’t prepared to run the interview.
We began with what sounded like a straightforward array duplication problem. I gave an optimized solution with linear time and space. Instead of letting it stay a trade-off discussion, the interviewer pushed for a different approach and when I pointed out the memory overhead, the mood turned personal. Rather than a peer-level evaluation, the discussion quickly became defensive.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
