InterviewLegend

Your Prep Plan

Alex Chen12 min readUpdated 970 real interview reports
In this lesson
  • Find out first whether your org is OCI or a legacy database and apps team
  • Lead with the coding core and LRU Cache, then the SQL and Java fundamentals
  • Prepare a metrics-backed failure story for the bartender round

Oracle grades its own way, and five things set the shape. The first is a question you answer before you open an editor: which org are you interviewing with? OCI and the legacy database and apps orgs run genuinely different loops. Then come the pieces you drill. There's an easy-to-medium coding core and a real SQL and DBMS layer that a LeetCode-only plan skips. Seniors get a design surface that tests low-level and distributed design together. Most loops end on a cross-team behavioral round they call the bartender. Get those sized right and the rest is bookkeeping.

The Oracle angle
Nail which org you are interviewing with before you touch a single data structure. The org fragmentation here is severe. OCI runs a modern, standardized loop (HackerRank, a system design round, the bartender) that pays at the top of the band and promotes faster. The legacy database, Fusion and apps, NetSuite, and Oracle Health orgs lean toward product knowledge and SQL (with PL/SQL for database roles). They run lighter DSA on slower, lower-comp timelines for the same level. A plan built for a generic "Oracle loop" is built for a company that does not exist. Email your recruiter, ask which team owns the req, and tailor everything below to the answer.

One layer decides more Oracle loops than people expect. Because it is a database company, a real SQL and DBMS layer rides right alongside the coding. It lives in the campus online assessment and resurfaces as trade-offs inside coding and design rounds, and a candidate who trained only on LeetCode gets blindsided by it. Settle one more habit early too. You code on a plain online editor that has to compile and pass test cases, and built-in library functions are sometimes banned outright. Practice cold, from scratch, on a bare editor. That is the room.

How to spend your prep time

Each phase below has one focus, a rough share of your time, and a checkpoint you clear before moving on. The shares assume a full senior loop with two design rounds in it. That design surface is senior-weighted. Targeting new grad or IC2? Shrink Phase 4 to almost nothing and pour those hours back into the coding core and the fundamentals layer. Confirm your org and level on the first call, because the answer moves real hours between the phases.

1
Phase 1 · start here

Orient, then identify your org and level

  • Read The Interview Process and How Hiring Decisions Are Made so the shape is clear. It starts with a recruiter phone screen, then a HackerRank online assessment (heavy for campus, often skipped for experienced hires). Sometimes there's one technical phone screen. Then a live loop of four to five rounds, then recruiter and offer. End to end it runs slow and high-variance, with multi-week silences common.
  • Make the first Oracle-specific move: ask your recruiter which org and team the req sits in. OCI (Oracle Cloud Infrastructure) runs the modern, standardized loop of HackerRank plus system design plus the bartender, pays at the top of the range, and is the prestige destination. Legacy database, Fusion and apps, NetSuite, and Oracle Health orgs run lighter-DSA, more SQL and product-focused loops that are slower and lower-comp. Which org you interview with changes almost everything.
  • Name your target level on Oracle's real ladder, IC1 through IC5 (Software Developer 1 up to Consulting MTS). Watch the naming variant: the same rung posts as "Software Developer 1/2/3/4" in India and apps instead of the MTS/SMTS family. Senior MTS (IC3) is where the loop adds the design rounds, so your level sets how much of the system design phase applies to you.
Ready to move on: You can describe your loop in order, you know which org and team you are interviewing with (or you have emailed the recruiter to find out), and you have named your target IC level.
2
Phase 2 · the coding core · ≈35%

The easy-to-medium coding core

  • Work the six coding lessons: Arrays & Hashing (the dominant cluster, so lead here), then Strings & Parsing, Trees & BSTs, Design & LRU Cache, Stacks & Intervals, and Graphs, Grids & DP. The band is easy to medium. Medium is the mode, and the hard problems are a minority that tend to be "hard-looking but standard" (First Missing Positive, Trapping Rain Water, Integer to English Words). A candidate fluent at LeetCode-medium clears most Oracle loops.
  • Own LRU Cache cold. It recurs in Oracle loops more than any other problem by a wide margin, roughly three times as often as the next one, and it comes back thread-safe at senior. Build it until it is recall, not reconstruction. Four Premium questions, and House Robber are the next tier to make automatic.
  • Do not skip dynamic programming. The line that "Oracle never asks DP" is a myth: House Robber and max-non-adjacent-sum, a Premium question, and Word Break all recur in a moderate DP tier. You want breadth across the patterns here, not exotic depth.
Ready to move on: A fresh medium goes to correct, compiling code in about twenty-five minutes on a plain online editor. LRU Cache is muscle memory. You can pick the right pattern for arrays, strings, trees, stacks, intervals, graphs, and moderate DP without stalling.
3
Phase 3 · Oracle fundamentals · ≈20%

The Oracle fundamentals a LeetCode-only plan skips

  • Work Oracle Fundamentals, the layer a pure algorithm grind walks in blind to. For campus and new-grad candidates the HackerRank OA runs about 100 minutes with roughly 36 questions. Expect aptitude MCQ and CS-fundamentals MCQ (DBMS normalization, ACID, keys, indexing, plus OS and OOP output-prediction). Then one to three coding problems. A common split is one DSA, one SQL, and one API or REST task.
  • Get real reps on SQL and DBMS: joins, group-by, subqueries, and taking a plain-English feature to a normalized schema and ER diagram. Also practice the SQL-versus-NoSQL, indexing, and caching trade-offs that surface inside coding and design rounds. Some rounds even let you choose "DB queries or algorithms." Java-internals probes recur too (collections and HashMap internals, JDBC, thread-pool sizing, volatile versus atomic).
  • If you are targeting senior, add the concurrency slice in this lesson: Producer-Consumer, a thread-safe LRU, and a Singleton that is safe under threads. This is where the coding bar and the low-level design bar meet.
Ready to move on: You can write the common joins and a group-by from memory, normalize a plain-English feature to a schema, explain ACID and one indexing trade-off out loud, and (if senior) make LRU thread-safe.
4
Phase 4 · system design · ≈20%

System design, senior-only: LLD and HLD

  • Start with What Oracle Tests, which sets the honest expectation. New grads and junior IC1/IC2 face little or no distributed design, and at most one object-oriented-design-in-code prompt. If that's you, shrink this phase to near zero and move the hours into the coding core and fundamentals. At Senior MTS and up the design surface is heaviest, often two rounds (one low-level and one distributed HLD) plus the hiring manager's "explain your own architecture" deep-dive.
  • Build the four worked designs. LLD: Thread-Safe Cache teaches the object-oriented-design method (nouns to classes, interfaces, Strategy for pluggable eviction, SOLID, concurrency-safety) that is an Oracle signature. Then the HLD set: Distributed Job Scheduler (the number-one recurring Oracle HLD), Concurrent Booking System (seat locking and double-booking prevention, BookMyShow-style), and DB-Backed Sharded Service (schema, partitioning, indexing, with the OCI service overlay).
  • Aim for a practical, production-over-textbook bar at small-to-medium scale, not a billion-user drill. And skip the storage-engine myth: Oracle does not ask SWE candidates to design a query optimizer or an MVCC engine. The real DB angle is a DB-backed service plus fundamentals.
Ready to move on: You can carry LRU from code to a thread-safe class. You can sketch the job scheduler with a queue, worker pool, durable state, and retries. You can hold a real conversation on the booking system and the DB-backed service, schema included.
5
Phase 5 · behavioral · ≈15%

The bartender round and the values framing

  • Read Behavioral & Values. Oracle is not a leadership-principles company the way Amazon is, so there is no public, numbered rubric you get scored against. Corporate-wide, the only official value list is the six from Oracle's Code of Ethics (Integrity, Mutual Respect, Teamwork, Communication, Customer Satisfaction, Quality), and that is a compliance document, not an interview scorecard. Do not recite it as one.
  • OCI candidates consistently report a behavioral organized around an internal set they call the "OCI values." Think putting customers first, acting now then iterating, owning without ego, and nailing the basics. Treat that as a guide to what OCI cares about, not a verbatim rubric to recite, since the exact wording and count vary between accounts. Prepare against the themes.
  • Expect the final round to be the "bartender": a senior engineer or manager from outside the hiring team runs a mostly-behavioral STAR interview, Oracle's softer analog to a Bar Raiser. Prepare a metrics-backed failure story. A weak one with no metric and no lesson is the number-one reported rejection cause. Be ready for "Why Oracle?" in real depth, anchored to OCI, databases, and distributed systems. Behavioral Questions by Theme has the worked strong-versus-weak example.
Ready to move on: You have a metrics-backed failure story and a genuine "Why Oracle" answer. You have one story each for conflict, customer impact under a tight deadline, and (if senior) mentoring. You can name the theme a given prompt is testing.
6
Phase 6 · the offer · ≈10%

The offer, then mock cold and taper

  • Run one or two full mocks against a timer on a plain online editor that compiles and passes test cases. That's the constraint in the room. Built-in helpers are sometimes banned too (for example, a longest perfect-square chain without Math.sqrt). Force one mock to include the SQL and DBMS layer, and if you are senior, one low-level-plus-distributed design pairing.
  • Skim Negotiating Your Offer so the shape is not a surprise. Oracle pays modest cash with no meaningful annual bonus, so comp is essentially base plus RSU, below FAANG through the mid-levels, then it roughly doubles at IC5. The RSUs vest annually, once per year at each anniversary (leave mid-year and you get nothing for that partial year), often on a front-loaded 40/30/20/10 shape at OCI. Grant size is negotiable, cadence is not.
  • Negotiate total comp, not one lever. Push the number and let them allocate, because pushing RSU alone just moves money out of base. Ask for a sign-on (it is winnable, and $35K is very good at junior and mid), and fix a high base up front since base is sticky after hire. Then fix your two weakest surfaces, stop adding new material, and sleep.
Ready to move on: A stranger running your mock would pass you. You can code cold on a compile-and-pass editor with no AI help. You value Oracle RSUs at the live ORCL price on an annual vesting schedule, and you negotiate on total comp.
The Oracle angle
The two things a LeetCode-only candidate walks in blind to are the fundamentals layer and how much LRU matters. It is a database company, and it tests like one. SQL and DBMS live right in the OA, and indexing questions and Java internals resurface as trade-offs inside coding and design rounds. Meanwhile LRU Cache recurs more than any other Oracle problem, and at senior it comes back thread-safe. Train only arrays and trees and you are ready for half the loop. The Oracle Fundamentals lesson and owning LRU cold are what close the gap.

In the room

The habits below are where prepared candidates drop points at Oracle specifically. Each clears a bar this loop sets that a pure pattern grind never trains. None are optional here.

The Oracle angle
The last round is usually a "bartender." Don't treat it as a formality. A senior engineer from outside the hiring team runs a mostly-behavioral round, Oracle's softer analog to a Bar Raiser. The number-one reported rejection cause here is a weak failure story with no metric and no lesson. Bring a real one. Expect "Why Oracle?" in depth, and anchor it to OCI, databases, and distributed systems rather than legacy ERP. Down-leveling is common and set by the panel at the debrief, so give them nothing to trim.
  • Compile and pass the test cases. Oracle codes on a plain online editor that must compile and pass. Partial passes are recoverable, so land a correct brute-force version before you optimize, and keep it running. A working plain answer beats an elegant broken one.
  • Code without the library crutch. Built-in functions are sometimes banned by name (a longest perfect-square chain without Math.sqrt, an in-place O(1)-space array trick). Practice the from-scratch version so a banned helper does not derail you mid-round.
  • Bring the SQL and DBMS layer. A DBMS multiple-choice question, a SQL query, or an indexing trade-off can surface in any round, campus or lateral. Be ready to write a join and a group-by, normalize a schema, and reason about SQL versus NoSQL out loud.
  • Own LRU cold, thread-safe if senior. It is the flagship Oracle problem and the bridge into the low-level design round. Build it from memory, then be ready to make it safe under concurrent access.
  • Ask which org and team you are in. OCI and the legacy orgs run different loops, so the single most useful question you can ask your recruiter is which one owns the req. The answer moves real hours between the phases above.
  • Value the offer at the live ORCL price. Comp is base plus RSU with no meaningful annual bonus, and the RSUs vest once a year, not quarterly. Negotiate total comp on the current share price, ask for the sign-on, and fix a high base up front.

Identify your org first. Then drill the easy-to-medium coding core, the Oracle fundamentals a LeetCode-only plan skips, senior-only design, and the bartender. Oracle is a database company with an easy-to-medium bar and a genuine SQL and DBMS layer with Java internals. Seniors face a low-level-plus-distributed design surface. Most loops also include a cross-team behavioral round, and the org split changes the whole loop. Size your prep to your org and level. Own LRU cold. Everything else in this guide sits on that spine.

Key Takeaways

  • ✓Identify your org and level before anything else. OCI runs the modern, top-of-band loop, while legacy database, apps, and Health orgs run lighter-DSA, SQL-heavy variants, so which team owns your req changes almost everything. Ask the recruiter.
  • ✓Spend the bulk of your time on the easy-to-medium coding core (about a third). Medium is the mode, and LRU Cache is the flagship problem to own cold. Next come the Oracle fundamentals a LeetCode-only plan skips: the HackerRank OA, SQL and DBMS, Java internals, and senior concurrency.
  • ✓Treat system design as senior-only. New grads face at most one object-oriented-design-in-code prompt and should move those hours into coding and fundamentals, while Senior MTS and up get a low-level round and a distributed round, so build both.
  • ✓Prepare a metrics-backed failure story and a real "Why Oracle" for the bartender round. Value the offer at the live ORCL price: base plus RSU, no meaningful bonus, annual vesting. Negotiate total comp across every lever.
Next up:The Coding Interview
Had your Oracle interview?Tell us what they asked. Reviewed before it goes in, never with your name.
Oracle interview guide

Know what Oracle asks before you walk in.

19 coding · 4 system design · 18 behavioral questions

Get Premium$49 a year · Cancel anytime
Or start freeNo card.

Get their questions first.

InterviewLegend is independent and not affiliated with or endorsed by any company it covers.