The interview process started with a 4-hour, single-problem code challenge. It was an interesting, real-life style algorithm problem that I felt was well thought out and would accurately capture problem-solving skills.
The second round was a 1:1 video interview code challenge focusing on data structures and time efficiency. The interviewer was extremely stiff and difficult to understand.
The final stage consisted of a panel of four back-to-back interviews, ranging from 30-60 minutes each. All were a combination of behavioral and technical.
Two interviewers were great: they were candid about their experience, easy to talk to, and encouraging as I went through the challenges.
Another was hard to read but pleasant. The last interviewer was extremely rude, literally saying things like, "I can't grade you based on your inner monologue," and simply saying, "No," instead of providing guidance.
Based on the variety of interviewers, I'm unsure if the company culture is great, as two people seemed awful to work with and two seemed great.
There was a heavy emphasis on OOP and time complexity analysis throughout the process.
I was told at the end that they interviewed roughly 1,600+ candidates for 4-6 openings.
Describe the most interesting or challenging project you've worked on. How did you preemptively ensure it would scale well?
Describe in detail how the HTTP network protocol works when a user interacts with a web app.
Using OOP principles, how would you design a website where users can book a flight?
The following metrics were computed from 4 interview experiences for the Okta Software Engineer New Grad role in United States.
Okta's interview process for their Software Engineer New Grad roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Okta's Software Engineer New Grad interview process in United States.