I applied online. The process took 4 weeks. I interviewed at Okta (Toronto, ON) in Jul 2025
Interview
5 part interview process - Initial recruiter screening, Hiring Manager Screening, Take-home assignment, Tech Interview, Final panel interview.
Initial response times were great, went through 4 (out of 5 rounds) within 2-3 weeks. However, I got ghosted after the tech interview (round 4). 0 feedback provided, all follow-up emails ignored.
One of the interviewers actually boasted about the company being "known for responding" but in hindsight, I think they were being sarcastic.
Interview questions [1]
Question 1
1. CodeSignal assignment about Rate Limiting.
2. Pair-programming exercise for a express/node endpoint.
3. System Design (Cross-Domain SSO).
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
Interview
Recruiters reached out to me twice, and both times proceeded to ghost me. I don't think I'll waste my time dealing with this company again as clearly they don't know what they're doing.
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.