Staff Software Engineer applicants have rated the interview process at Okta with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 43% positive. To compare, the company-average is 38.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Staff Software Engineer roles take an average of 44 days to get hired, when considering 7 user submitted interviews for this role. To compare, the hiring process at Okta overall takes an average of 25 days.
Common stages of the interview process at Okta as a Staff Software Engineer according to 7 Glassdoor interviews include:
Phone interview: 55%
Skills test: 27%
One on one interview: 18%
Here are the most commonly searched roles for interview reports -
1. Screening round- DSA based one problem (stack based)
2. DSA round- 2 probelms (one array and one graph based)
3. Debugging - Need to find bugs in a function and resolve it
4. HLD Design round
5. Hiring Manager ROund
Interview questions [1]
Question 1
1. parenthesis mathcing in screeing round.
2. Graph traversal in DSA
I applied through a recruiter. The process took 3 weeks. I interviewed at Okta (Bengaluru) in Mar 2026
Interview
The first was the online test
The second round was an 2 panel interview on JavaScript and system design round. Focused on how’s things work end to end.
The third was again a 2 panel interview on JavaScript and hands on coding.
Ghosted after completing 4 rounds. If not selected at least have the courtesy to inform.
I applied through a recruiter. I interviewed at Okta (Toronto, ON) in Feb 2026
Interview
Interviewed for Staff Software Engineer role at Okta.
The interview process consisted of 4 rounds:
Recruiter screening
Hiring Manager discussion
CodeSignal online assessment
Technical discussion with two engineers (focused on the assignment)
The overall process was smooth and well-organized. The online assessment was followed by a detailed technical discussion where I explained my approach and design decisions.
The final round was a discussion with two engineers about the assignment and general technical concepts. The discussion was interactive, though at times the interview felt a bit unstructured, and there were some areas of confusion during the conversation.
Overall, it was a good learning experience. The questions were practical and focused on real-world backend concepts like rate limiting, system design, and trade-offs.