Taro Logo

Principal Software Engineer Interview Experience

May 1, 2022
Positive ExperienceNo Offer

Process

Submitted an application online.

This was followed by an initial 30-minute phone interview to discuss the position, the interview process, and identify next steps.

First interview: A one-hour session with the team lead that included a beginner-level coding challenge.

Second interview: A 45-minute session with the hiring manager that included dialogue using the STAR format and ended with time to ask interviewer questions.

Third interview: A one-hour session with an architect that included a medium-level coding challenge.

Fourth interview: A 45-minute session with an architect that included a system design challenge.

Fifth interview: A one-hour session with an architect that included a medium-level coding challenge.

I was informed via an automated message that I was no longer a candidate for the position.

Questions

Convert a list of Java objects to another list of Java objects

Design a data synchronization solution similar to Dropbox

Code a method to merge sorted arrays

Code a solution to identify a winner in a game using constant time

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the Okta Principal Software Engineer role in United States.

Success Rate

25%
Pass Rate

Okta's interview process for their Principal Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive75%
Neutral0%
Negative25%

Candidates reported having very good feelings for Okta's Principal Software Engineer interview process in United States.

Okta Work Experiences