Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
SecurityProduct company

Okta

Builds identity and access management software that handles sign in, single sign on and user management for organisations.

Not known5 stage process documentedFounded 2009
Headquarters

San Francisco, California, United States

Headcount

1,000 to 5,000

1,000 to 4,999 people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply

No careers page on file yet. Try their LinkedIn or the job boards below.

Website

Ask for a referral to Okta

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

How they hire

Okta publishes its steps only for intern and early careers roles: CodeSignal pre-screen, recruiter screen, technical interview and hiring manager interview. Full time experienced loops are longer and are described here from candidate reports.

  1. 1

    CodeSignal pre-screen

    Official +1
    Online testRemote

    For technical early careers roles Okta starts with a CodeSignal test. Experienced candidates report a similar timed test of about four questions.

  2. 2

    Recruiter screen

    Official +1
    Recruiter screenRemote

    A conversational call about your background and interest.

  3. 3

    Technical interview

    Official +1
    Live codingRemote

    A video interview with an engineer on medium level coding problems, talking through your approach first.

  4. 4

    Virtual onsite (experienced roles)

    Reported
    Panel interviewRemote

    Three or four interviews covering algorithms, system design and behavioural questions. Some senior or frontend roles add a take home project with a presentation.

  5. 5

    Hiring manager interview

    Official
    Hiring manager

    A behavioural conversation with the hiring manager.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Identity and security concepts

    Reported

    Candidates report questions on single sign-on, OAuth and how it differs from SAML, and design problems with security built in.

  • Explaining trade-offs

    Reported

    Interviewers look for clear reasoning about why you chose an approach.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Roadmap
Coding Interview Playbook

A structured learning path through coding interview preparation that brings together data structures and algorithms fundamentals, recursion and the pattern-based approach to coding questions in one order. It totals 77 chapters and 1,054 lessons, with quizzes, flashcards and a certificate. Use it when you have plenty of material but no clear plan for what to study first.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 6 months
SubscriptionDetails
Roadmap
FAANG Coding Interview Roadmap

A bundle of five company-specific question courses covering the problems most often reported from Meta, Microsoft, Amazon, Google and Oracle coding rounds, each split into easy, medium and hard sets with worked solutions. It suits candidates who already know the core patterns and have a loop booked at one of these companies, and want to rehearse on the questions those interviewers are known to ask.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 4 months · Advanced
SubscriptionDetails
Course
Grokking Tech Salary Negotiations

A practical course on negotiating compensation in tech, from preparing and building a strategy to specific tactics, the full package beyond base salary, handling multiple offers and asking for a raise. It has tailored sections for fresh graduates and experienced engineers. It suits anyone with an offer coming, and anyone who has ever accepted the first number out of discomfort.

  • Career
  • Job search
Design Gurus · Career Growth · 1 week
SubscriptionDetails
Roadmap
System Design Interview Playbook

A learning path that bundles five courses into one sequence for system design preparation: System Design Fundamentals, Grokking the System Design Interview, Advanced System Design Interview Volume II, Grokking Microservices Design Patterns and Grokking Design Patterns for Engineers and Managers. Together they add up to 76 chapters and 666 lessons. It suits engineers who want a complete, ordered curriculum instead of assembling one from scattered posts.

  • System design
  • Job search
  • Career
Design Gurus · System Design · 2 to 4 months
SubscriptionDetails
Cheat sheet
Sefism University to Job-Ready Cheat Sheet

The quick-revision companion to the University to job-ready roadmap: OOP, Git and engineering practice, data structures, DBMS, operating systems and networks, then projects, choosing a direction, getting experience and the hiring process. It has editions for first or second year, third year, and final year. Revise a chapter a week alongside your courses and before assessments.

  • Career
  • Job search
  • CS fundamentals
  • DSA
Sefism · Career Growth · Reference · Beginner
FreeDetails
Video
Gaurav Sen: System Design

Gaurav Sen's YouTube channel, one of the first to make system design approachable, with whiteboard-style walkthroughs of scaling, sharding, consistent hashing, message queues, rate limiting and classic interview designs. He reasons through problems on camera, including discarded first ideas, rather than presenting a finished answer. The channel has about 758k subscribers. It is a good free starting point for system design before committing money to a course.

  • System design
  • Job search
Gaurav Sen · System Design · Ongoing · Intermediate
FreeDetails
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the Okta page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the Okta page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

Practise on CodeSignal before the pre-screen. Learn the basics of OAuth, OpenID Connect and SAML, since identity topics come up even in general engineering loops.

Sources

Whole profile last checked 2026-09-22.

Interviewed at Okta? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to Okta

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the Okta page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.

Book a free sessionSee all services

Follow along

New writing, resources and project ideas land here first.