Okta Interview Questions
& Process

It started with a written email screening and then moved to two 30-minute behavioral interview rounds. The first was with regional sales team leaders and the second with a sales manager from a different location. You should prepare stories using the STAR Method about communication, teamwork, motivation, and leadership. The interviewers weren't from HR, so experiences might differ for other roles, but they were genuinely interested in me as a person, had great energy, and made it comfortable to answer questions. They set aside 10 minutes for my questions.

The interview process was a bit odd and frustrating. First, the recruiter initially shared a compensation range that differed from the public job description. Even when I pointed this out with the job description link, she didn't respond, which was weird since we had been emailing before. Then, the recruiter said I'd have a technical interview and stressed multiple times there would be no coding. I expected a high-level technical discussion. However, just 30 minutes before my 8 am meeting, the interviewer informed me we would be coding and I needed my environment ready. Since I only code on my work laptop and do interviews on my personal one, I had to rush to download a code editor and update Python and pip. It felt unreasonable to expect that on such short notice, and honestly, it felt like they were trying to set me up for failure. There also seemed to be some tension between Auth0 and Okta. The hiring manager was great, though, which was the only reason I considered continuing despite these red flags.

So, the interview for the Technical Support Engineer at Okta was pretty straightforward and had 4 parts. First, there was an online test with aptitude and some basic tech MCQs on networking, OS, and troubleshooting. After that, I had a group discussion focusing on communication and how you present your thoughts; the topic wasn't super technical, more about conversation flow. The next round was a deep technical interview covering Linux/Windows troubleshooting, DNS, DHCP, SSO (SAML, OAuth), and debugging strategies. They also threw in some practical scenarios, like troubleshooting Okta login issues, to see how I think. The last bit was an HR chat about my background, shift work, salary hopes, and career plans. It was a good experience, the people were nice, and the difficulty was moderate if you know your tech support and networking basics.

The scheduling was really bad, lots of people involved and interviews kept getting moved or canceled. They even did the screening and onsite together once because of miscommunication. It worked out for me because I had another offer, but it showed they weren't organized. The interviews themselves were good though, interviewers were professional and conversations were structured. After finishing all rounds, I didn't hear back even after following up. Almost three weeks later, I got an automated rejection email, like they just rejected my online application, no personalized feedback or acknowledgment of my time. I get not everyone gets picked, but the lack of communication and transparency was disappointing. Candidates put in a lot of time and effort, and a quick, personalized update would be respectful.