Okta · Primly Community

Okta frontend engineer interview, went through the full loop in April 2026

quietquit_quincy · 6 replies

Wrapped up my Okta frontend engineer interview loop a few weeks ago. Wanted to write it up while it was still fresh because I spent a lot of time searching for this and found basically nothing specific.

For context, I was targeting a mid-level role (roughly IC3/IC4 range), React-focused, remote-eligible. I was referred in through a friend who'd been there about a year.

Recruiter screen (30 min): Standard stuff. Why Okta, what you're working on now, salary range. Recruiter was genuinely nice, moved fast, sent me prep materials the same day which I appreciated.

Technical phone screen (60 min): This was with an engineer on the Identity Engine team. First half was a live coding problem, JavaScript-focused. Think DOM manipulation, event handling, no framework magic. Something like: implement a multi-step wizard component with state managed yourself. Second half was a conversation about a past project, specifically asking about accessibility and performance decisions I made.

Onsite loop (virtual, 4 rounds in one day): Coding round 1: More vanilla JS, building a debounce/throttle from scratch, then a follow-up around async patterns. No React. They seemed to want to see that I understood the fundamentals underneath the library. Coding round 2: Actual React component. Build a table with sorting and filtering. They cared a lot about how I thought about state, not just whether it worked. System design: Frontend-specific. Design a single sign-on widget (you can imagine why Okta would ask this). How does the iframe/popup flow work, what's the security model, how do you handle token storage. This one caught me a bit off guard because I hadn't prepped frontend system design as hard as I prepped LC. Behavioral: Four STAR questions. Conflict with a stakeholder, a time you had to ship something you disagreed with, a time you mentored someone, biggest technical mistake. Pretty thorough.

Two things that stood out. First, they really care about security awareness because their product is literally identity, so "what's wrong with storing tokens in localStorage" type questions come up naturally. Second, the behavioral round felt weighted, not just a checkbox.

Total process took about 5 weeks from referral to offer. Still deciding. Their base was competitive, RSU refresh felt light compared to offers I have from other companies right now.

6 replies

mobile_mara

The vanilla JS emphasis is interesting. Did they ask you to use TypeScript at any point or was it all plain JS?

frontend_fran

All vanilla JS in the coding rounds, but my React round they were fine with me using TypeScript and I think preferred it. The system design was whiteboard-y so language-agnostic.

jp_newgrad

Did they say anything about expected LC difficulty? Like hard problems or more medium-level?

frontend_fran

Replying to jp_newgrad: I'd call it medium difficulty, but the tricky part is they're not standard LeetCode problems. More like applied JS knowledge. If you know how closures, promises, and event bubbling actually work you'll be fine. If you've only practiced LC in Python without thinking about the DOM you might struggle.

quietquit_quincy

The "ship something you disagreed with" behavioral is one I always prep but somehow never feel ready for in the room. Any tips on how you framed your answer?

frontend_fran

I talked about a time I lost a vote on which state management library to use, went with the team choice anyway, and then focused on what I learned from actually implementing the thing I argued against. They seemed to like that I owned the execution after disagreeing. The key is you can't be bitter about it in the telling, even a little.