Real, anonymous reports from people who interviewed for Software Engineer at Oracle, newest first and distilled into what to expect across the loop.
Recruiter reached out and scheduled my interview, and over the next couple of weeks I went through a fairly standard multi-round loop that felt technical-first with clear progression. The first round started with a DSA problem—things like finding the longest continuous subarray under an absolute-difference constraint, or a more scenario-based question framed around infection spreading across houses. I also had to work through a variation-heavy prompt where the interviewer expected me to explain the approach and then reason about the complexity.
I interviewed for a backend + data role and started with a screening round focused on a very data-heavy question. The setting was all about URL access logs at a large scale, and I was asked to compute the top K URLs overall as well as the top K URLs accessed within the last 24 hours. I had to think through how to handle a huge volume of data, not just solve a small toy problem.
The interview process typically starts with a recruiter screen followed by a multi-round technical loop, often consisting of 4-6 rounds with a mix of coding, system design, and behavioral questions. Candidates noted that the timeline can vary significantly, with some experiencing delays of several months before receiving feedback.
Candidates faced a variety of coding challenges, primarily focused on data structures and algorithms (DSA), with questions ranging from medium to difficult levels. Common topics included implementing algorithms, reasoning about time and space complexity, and solving practical problems like LRU cache and course prerequisites.
System design rounds were a significant part of the interview process, where candidates were asked to design solutions for real-world problems, such as handling large file uploads or microservices architecture. The focus was on structuring the design and discussing trade-offs rather than just technical details.
Behavioral interviews were present but not always the primary focus; they often revolved around discussing past experiences, projects, and team fit. Candidates were encouraged to articulate their thought processes and how they approach problem-solving in a team context.
Overall, candidates found the interviews to be challenging but fair, with a consistent emphasis on clear reasoning and communication. Some reported feeling pressure due to the pacing of the interviews, while others noted inconsistencies in interviewer engagement and feedback.
Candidates wished they had focused more on specific areas such as system design and SQL queries, as well as practicing under timed conditions to simulate the interview environment. Understanding the expectations for each round and maintaining consistency across rounds were highlighted as key to success.