I applied online and received a reply from the recruiter the next day. I scheduled a phone screening with a manager. During the phone screening, I was asked common questions and then asked to write a small program.
Within the next couple of days, I scheduled another phone screening with a technical lead from another team. I passed that as well, answering coding questions and finding errors in code snippets.
I was invited for an on-site interview. That's where a pretty awful experience started.
The interview was rescheduled a couple of times. However, when I arrived, I had to wait about half an hour for the first interviewer to arrive.
I spent about 6 hours on-site, interviewed by 6 different people. Some were knowledgeable, others were not. Every single one asked me to fix problems in the code or write some code snippets. Really? Don't you trust each other?
The strangest task was handwritten on the board, fully covering almost all of it. The solution of replacing all that code with just 4 lines did not satisfy the interviewer.
Another interviewer, when I was talking about my previous work, was visibly rolling their eyes at decisions that were PM responsibility, as if it was the worst thing they had ever heard.
None of the interviewers seemed brave enough to call it off and not waste anyone's time, even though most of them looked very unsatisfied.
Fix the code for locking/unlocking critical sections.
The following metrics were computed from 2 interview experiences for the Okta Principal Software Engineer role in San Francisco, California.
Okta's interview process for their Principal Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Okta's Principal Software Engineer interview process in San Francisco, California.