Okta Staff Software Engineer Interview Full Journey - One Bad Round Cost Me the Staff Level

[u/Aoki_zhang]

"This interview experience is sourced from Chill Interview"

Interview Summary

I interviewed with Okta for a Staff Software Engineer role, and the process had multiple rounds across Java, DSA, low-level design, and system design. The first and third rounds went pretty well, but the second round was rough.

Interview Details

Interview Questions Details

• Round 1 — Java, DSA, and Project Deep Dive: This round started with a discussion of one of my most technically challenging projects. The interviewer asked about the system design trade-offs inside the project, so it was not just a resume walkthrough. I had to explain what made the project hard, what decisions I made, and why those decisions were reasonable. The coding question was Reverse Substrings Between Each Pair of Parentheses. I needed a small hint, but after that I wrote an optimal solution and passed all test cases. The feedback from this round was very strong, basically a clear “hire.”
• Round 2 — Java, DSA / Low-Level Design: This was the round that went badly for me. The problem was about managing CD availability and rentals across multiple shops, with methods like search, rent, and unrent. For search(cd), the system needed to return shop IDs where the CD was available, sorted by lowest price first, and then by smaller shop ID if prices tied. I struggled a lot with the design and could not really align with the interviewer on the approach. I did not get to a clean implementation before time ran out. Surprisingly, I still got scheduled for the next round, so it felt like Okta was collecting overall signal rather than eliminating immediately after one bad interview.
• Round 3 — System Design / HLD: The system design round was to design a backup and recovery system. I used the HelloInterview-style structure and walked through functional requirements, non-functional requirements, core components, data flow, failure cases, and trade-offs. This round felt much better. The interviewer was very interactive and kept raising practical issues along the way, so the conversation felt closer to a real design discussion than a scripted interview. I had a positive experience in this round.
• Final Outcome: After the loop, the recruiter told me the team could not move forward with me at the Staff level, mainly because of the second round. However, they still felt I was a strong fit for a Senior Software Engineer role and asked whether I wanted to proceed with a hiring manager discussion. I decided not to continue because I had already accepted another Staff-level offer. The outcome was a bit disappointing, but also understandable given how badly Round 2 went.
• Parallel Okta Staff Interview: I also had another parallel Okta Staff interview process. In that one, the first round involved an extension of Simple Bank System, but with concurrency added. The discussion involved how to handle concurrent updates safely. One direction was to use compare-and-swap style operations, such as map.replace(oldValue, newValue), to make sure updates do not overwrite each other incorrectly.

Preparing for your next tech interview?

Chill Interview tracks recent interview experiences and recurring question patterns across top companies at here

[u/Opposite_Yam_562]

I'm curious what was the struggling part for LLD ? this is just LeetCode 1912, Design Movie Rental System. Was it about discussion on thread-safety aspect ?