I applied to Okta for a Staff Software Engineer role and the process landed on a design problem that set the tone quickly. The main prompt was to design a movie rental system. I remember spending time reasoning about the core flows and how the components would interact, keeping the design grounded in how the system would actually be used.
The rest of what I remember is mostly the structure around that kind of staff-level design evaluation—enough to feel like the bar wasn’t just about getting to a working answer, but about thinking through trade-offs and presenting a coherent approach. Overall, it was a focused interview that leaned heavily on the same movie-rental design theme, and by the end I felt like I had shown my thinking clearly, even if the final decision didn’t go my way.
2 months ago
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.
2 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 …
10 months ago
Average Positive Bengaluru
After an initial HR call to go over the role and what I’d be working on, I moved into a technical screen. That screen was LeetCode-style DSA practice …
11 months ago
Average Negative Toronto, ON
I came into this one feeling unusually hopeful because the recruiter was responsive and had clearly prepared me for what the onsite would look like. T…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial HR Screening
The interview process typically begins with an HR screening that assesses fit and outlines the role. This initial conversation is crucial as it sets the stage for subsequent technical interviews and can heavily influence the overall progression of the process.
HR screeningfit assessmentrole overview
Technical Coding Rounds
Candidates can expect multiple technical coding interviews focused on data structures and algorithms (DSA), often involving medium-level problems that assess problem-solving skills under time constraints. The coding interviews are generally structured and can include a mix of LeetCode-style questions and real-world scenarios.
coding interviewsDSAproblem-solving
System Design and Architecture Discussions
Some interviews may shift towards system design or architecture discussions, where candidates are expected to demonstrate their understanding of complex systems and trade-offs involved in design decisions. This aspect can vary in tone, with some candidates reporting a lack of collaboration during these discussions.
system designarchitecturetrade-offs
Behavioral and Managerial Rounds
Behavioral interviews are included to assess communication, teamwork, and past project experiences, often conducted by hiring managers. These rounds aim to evaluate cultural fit and how candidates collaborate with others, contrasting with the technical focus of earlier rounds.
behavioral interviewscultural fitteamwork
Interview Tone and Professionalism
Candidates have reported mixed experiences regarding the professionalism and tone of interviews, with some feeling that certain interviewers were unprepared or dismissive. This inconsistency can impact the overall candidate experience and perception of the company culture.
Many candidates expressed frustration over the lack of timely communication and transparency after interviews, often receiving automated rejection emails without personalized feedback. This aspect has left a negative impression on candidates regarding the respect for their time and effort.