← Back to Directory

Oracle

Large Enterprises

Most of these Oracle write-ups come from Software Engineers (51), then Machine Learning Engineers (2). The most reported rounds are the technical phone screen (33), the system design round (8), the behavioral / leadership round (6) and the hiring manager screen (3).

53 interview notes · updated Jun 2026

Oracle·Software Engineer·Technical Phone Screen

Jun 2026
Oracle SWE interview with a greedy algorithm problem. The interviewer pushed pretty hard on complexity analysis which I wasn't fully expecting, so that part was a bit rough.
  • Given an integer n, find the largest number less than or equal to n whose digits are monotone increasing (each digit is less than or equal to the next).

“Figured out the greedy approach pretty quickly.”

View Post

Oracle·Software Engineer·Technical Phone Screen

Jun 2026
Oracle SWE interview with a graph/topological sort problem. The simplifying constraint they gave made it more approachable than a full DAG question, but you still had to know your cycle detection.
  • Given n courses labeled 0 to n-1 and a list of prerequisite pairs where b must be taken before a, return any valid ordering to complete all courses. Each course has at most one direct prerequisite.

“The one-prerequisite constraint is a gift if you notice it early.”

View Post

Oracle·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Oracle for a software engineer role. Just one question but it had a lot of layers to it.
  • Tell me about a time you or your team caused a failure that impacted customers. How did you handle the fallout, communicate with affected users, and make sure it didn't happen again?

“The part that tripped me up was the customer communication piece.”

View Post

Oracle·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Oracle had a coding round that threw me off because it wasn't your typical algorithm grind. They handed you a requirements doc and an existing codebase and basically said: figure out what's broken or missing, then build a CLI tool to handle it. More of a code review plus implementation exercise than anything else.
  • You're given a requirements document and an existing codebase. Walk through how you'd read and understand the code, identify missing or underperforming features, and then implement a CLI tool that fulfills the spec.
  • Where in the existing codebase would you refactor, and what's your reasoning?
  • How would you approach testing the CLI tool you just built?

“This took me longer than I expected just to orient myself.”

View Post

Oracle·Software Engineer·Technical Phone Screen

Jun 2026
Oracle SWE interview with a classic two-pointer problem. Nothing too wild but the O(n) constraint meant you had to know exactly what you were doing, no brute force handwaving.
  • Given an array of integers representing heights of vertical lines, find the two lines that form a container holding the maximum amount of water. Solve it in O(n) time.

“The O(n) requirement is what makes this non-trivial.”

View Post

Oracle·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Oracle for a software engineer role, focused entirely on building a job scheduler from scratch. Dense topic with a lot of ground to cover in a constrained window, and I definitely felt the time pressure.
  • Design a job scheduler system that supports cron and fixed-delay scheduling, dispatches jobs to workers, and handles retries and job dependencies.
  • How would you architect the core components of the scheduler, including the queue, worker pool, and status store?
  • Walk through the scheduling algorithm and how you'd scale it across multiple scheduler instances.
  • How do you handle failure scenarios, specifically at-least-once delivery and missed job runs?
  • What metrics and observability would you build into this system?
  • What are the trade-offs between a pull-based versus push-based dispatch model, and between a centralized scheduler versus partitioned schedulers?

“This is the kind of question where you think you know where to start and then realize there are like five different places to start.”

View Post

Oracle·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Two behavioral questions for a Software Engineer role at Oracle. Pretty standard stuff but the second one had more teeth than I expected.
  • Describe a time you changed the scope of a project. What drove that decision, how did you bring stakeholders along, and what happened in the end?
  • Walk me through a process you automated. What was the manual problem, what did you build, and how did you measure the impact?

“I had a decent story for this but rambled too much on the backstory and barely had time to explain the outcome.”

View Post

Oracle·Software Engineer·Hiring Manager Screen

Jun 2026
Behavioral round with the hiring manager at Oracle for a software engineer role. Pretty standard set of questions, nothing surprising, but you need real numbers and stories ready or it shows.
  • Tell me about yourself and walk me through your most impactful project.
  • Describe a time you had a conflict with a peer or your manager and how you resolved it.
  • Tell me about a difficult trade-off you had to make on a project.
  • Walk me through a project that failed and what you took away from it.
  • How do you decide what to work on when everything feels urgent at the same time?
  • Why do you want to work at this company and specifically on this team?

“I'd practiced this one so many times it almost came out too rehearsed.”

View Post

Oracle·Software Engineer·Technical Phone Screen

Jun 2026
Oracle SWE coding round, one problem the whole session. The question looked like a parsing exercise but the O(n) constraint meant you had to think carefully about how you scanned the string.
  • Given an encoded string, decode it into a 26-element integer array representing letter frequencies. Letters a-i map to digits '1'-'9'; letters j-z map to two-digit numbers followed by '#' (e.g. '10#' for j). Immediately after a letter's encoding, an optional parenthesized integer like '(7)' means that letter repeats that many times; no parenthesis means it appears once. Return int[26] where index i is the count of the (i+1)-th letter. Must run in O(n).

“My first instinct was to just iterate left to right and parse greedily, but the '#' suffix for two-digit codes means you don't know if a digit is standalone or part of a two-digit code until you look ahead.”

View Post

Oracle·Software Engineer·Technical Phone Screen

Jun 2026
Oracle SWE interview with a classic LRU cache design problem. Pretty standard for this kind of role but the implementation details tripped me up more than expected.
  • Design and implement an LRU cache with get and put operations that both run in O(1) average time. When capacity is hit, the least recently used item should be evicted. Walk through your data structure choices and any edge cases you considered.

“I knew the answer going in, hashmap plus doubly linked list, but explaining WHY the doubly linked list specifically took me a second longer than it should have.”

View Post

Oracle interview FAQ

What rounds are in the Oracle interview?

Candidates most often report a technical phone screen (33 write-ups), a system design round (8), a behavioral / leadership round (6) and a hiring manager screen (3).

What does the Oracle technical phone screen cover?

Across 33 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (34 questions), Technical Trade-offs (16) and System Design (10).