Real, anonymous reports from people who interviewed for Software Engineer at Oracle, newest first and distilled into what to expect across the loop.
My process leaned heavily on a multi-round loop with very concrete technical coverage. I had a manager-style round where we talked high-level about my devops projects, and then I went into a hands-on technical interview that focused on medium tasks around Docker, Kubernetes, Ansible, and Git. After that, I met with a director who kept the conversation at the level of the projects I’d worked on and how I’d contribute.
I went through a fairly standard recruiter-to-loop flow that still felt a bit unpredictable in timing. After the initial recruiter interaction, the process stretched out and I ended up waiting through delays before the final technical part. Even with the extra downtime, the recruiter was responsive and kept me updated.
The interview process typically follows a structured flow starting with an HR screen, followed by multiple technical rounds focused on coding, system design, and behavioral assessments, often taking several weeks to months to complete.
Candidates can expect a strong emphasis on data structures and algorithms (DSA), with coding questions ranging from easy to medium difficulty, often derived from LeetCode-style problems, along with system design and SQL topics.
Behavioral interviews often occur after technical assessments, focusing on communication, fit, and past project experiences, with interviewers using structured methods like STAR to evaluate responses.
Candidates may face hands-on coding exercises during interviews, requiring them to demonstrate problem-solving skills in real-time, often under pressure, which can significantly impact performance.
The interview environment can vary, with some candidates experiencing unresponsive interviewers or disorganized sessions, which can affect their comfort and performance during technical assessments.
Candidates often reflect on their performance post-interview, noting the importance of deep preparation on specific problem types and the need for confidence in technical discussions to improve outcomes.