Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Okta (San Jose, CA) en oct 2020
Entrevista
I reached out to recruiter in LinkedIn and then process started. Screening was with hiring manager followed by on-site. Screening was mix of machine learning, behavioral, choosing questions. On-site had bunch of rounds - 1. Big Data (highly unprofessional interviewer who was laughing in wrong answers). 2. Coding round (simple problem). 3. Cultural/leadership 4. Design and architecture.
In the end they offered compensation which was very low for Bay area standards and hence I rejected the offer.
Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Okta (Bengaluru) en mar 2026
Entrevista
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.
Solicité el puesto a través de un captador. Acudí a una entrevista en Okta
Entrevista
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.
Solicité el puesto a través de un captador. Acudí a una entrevista en Okta (Toronto, ON) en feb 2026
Entrevista
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.
