Oracle · Primly Community

Oracle engineering manager interview loop, my experience from start to offer

consultant_cam · 5 replies

Just finished the Oracle engineering manager interview loop last month. Took about 5.5 weeks from recruiter screen to offer. Sharing the full breakdown because I couldn't find much specific info when I was prepping.

The loop was 5 rounds total:

Recruiter screen (30 min). Standard stuff. Why Oracle, current TC, availability. They asked about team size managed and whether I'd had P&L ownership. I managed a team of 8 at my last company so I passed this easily.

Hiring manager intro (45 min). This was more strategic than I expected. They wanted to know how I think about roadmap prioritization, how I handle a team that's technically strong but misaligned on direction. A lot of situational questions, very behavioral. No technical depth here.

Technical round (60 min). They did ask me to walk through an architecture I'd built and defend it. There was a whiteboard-style system design question around a notification system. The interviewer was clearly a principal engineer and pushed on consistency vs. availability tradeoffs. Not super hard but you need to be credible technically as an EM.

People and culture panel (2x45 min back to back). This was two separate interviewers. One focused on conflict resolution and giving feedback to underperformers. I had to give very specific examples with STAR format. The second was more values-based, Oracle culture stuff. Honestly felt a little rote but they listened carefully.

Director-level debrief (30 min). Felt less like an interview and more like a 'do you want to join us' conversation. They talked about the org structure, headcount plans, expectations in the first 90 days. A few soft questions about how I build relationships across teams.

Comp they offered: base $195k, ~25% bonus target, some RSUs vesting over 4 years. Total first-year around $265k depending on bonus payout, Austin TX. I've seen higher at hyperscalers for similar level but Oracle's base is solid and the bonus is actually achievable from what I can tell.

Biggest prep tip: they really test whether you can be specific. Generic leadership frameworks did not land well when I tried them. Real stories with real outcomes, including the messy ones.

5 replies

brand_ben

The technical round detail is useful. A lot of people prepping for EM roles assume they won't need to get into architecture depth and then get caught off guard. What was the principal eng's vibe, looking to trip you up or genuinely curious?

firsttime_mgr

Genuinely curious I think. He followed up on my answers and it turned into more of a discussion than a grilling. Once I said 'we actually chose eventual consistency here because the write volume was too high for synchronous replication and the downstream consumers could tolerate a 500ms lag' he seemed satisfied. The 'why' mattered a lot.

director_dee

That 90-day conversation at the end is a signal you're close to an offer. They usually only run that with candidates they're planning to move. Good sign you paid attention to it. The comp number is reasonable for Austin EM level, maybe a touch below current market but not embarrassing.

sre_sol

Did the panel ask about on-call culture or incident management at all? Curious whether Oracle EM interviews go into operational stuff or stay mostly on the people/strategy side.

firsttime_mgr

They didn't go deep on operational stuff in my loop but I was interviewing for a product engineering org, not infrastructure. Might be different for an SRE or platform EM role.