HR pinged me on Linkedin and scheduled a meet for which she never turned up. Then she came back with another meeting date for which she again did not turn up, thus wasting my time and my sleep TWICE (as the meetings were at PST friendly time 5AM IST). I cannot believe such unprofessional behavior from an Okta HR. She did not bother to reply or apologise for this either.
4
Outras avaliações de entrevista de vagas de Staff Software Engineer da empresa Okta
Candidatei-me por meio de recrutador(a). O processo levou 3 semanas. Fui entrevistado pela Okta (Bengaluru) em mar. de 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.
Candidatei-me por meio de recrutador(a). Fiz uma entrevista na empresa 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.
Candidatei-me por meio de recrutador(a). Fui entrevistado pela Okta (Toronto, ON) em fev. de 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.
