Okta · Primly Community

Okta product manager interview questions: what they asked across 6 rounds

pm_priya · 4 replies

did the okta PM loop earlier this year for a senior PM role on their workforce identity products side. six rounds total, all virtual. took notes after each one, posting them now while they're still fresh.

recruiter screen (30 min) standard. why okta, background, comp range, timeline. nothing tricky.

hiring manager screen (45 min) this was the most important early conversation. they asked: what's your experience with B2B SaaS products and enterprise buyers how do you define 'good' for a product you can't A/B test easily (enterprise compliance products are hard to instrument) describe a product you shipped that didn't hit its goals and what you learned

product sense round (60 min) asked to redesign okta's admin dashboard. they gave me a persona (IT admin at a mid-market company) and a scenario (onboarding a new batch of employees). i was expected to go deep on user pain points before jumping to solutions. they pushed back on my first solution to see if i'd cave or defend it with data. defend it. with data.

execution/metrics round (45 min) how would you define success for okta verify (their MFA product)? walk me through how you'd prioritize features when the customer and the compliance team want different things. what does a quarterly roadmap conversation with eng look like for you?

cross-functional round (45 min) talked with a staff engineer. they asked how i handle disagreements with engineering leads and specifically wanted a story where the PM was wrong. have that story ready.

behavioral round (45 min) standard STAR. focus on customer-impact stories.

overall: okta PM interviews are heavy on enterprise SaaS judgment and stakeholder navigation. they're less 'design a consumer product' and more 'how do you move a slow enterprise machine forward'. if your background is B2C, you'll need to reframe your stories carefully.

4 replies

growth_gabe

the 'product you can't A/B test easily' question is a really good signal for enterprise PM maturity. how did you answer it? i freeze on those because my whole background is consumer growth where i run experiments constantly

pm_priya

i leaned on qualitative methods: customer advisory boards, cohort analysis of usage adoption over time, NPS segmented by role, and close monitoring of support ticket volume after launches. also mentioned designing launches with control groups where possible (some enterprise contracts let you phase rollouts by org unit). they seemed satisfied.

apm_aisha

was there a take-home case or was everything live? i've been seeing more companies go the take-home route and i can never tell which format to expect

jordan_pm

the 'PM was wrong' story is something i think every PM should have locked and loaded regardless of company. if you don't have one, you're either lying to yourself or lying to them. good prep note.