Real, anonymous reports from people who interviewed for Software Engineer at Oracle Health, newest first and distilled into what to expect across the loop.
The process felt pretty well choreographed, and even when it got technically challenging, I never felt totally lost. After a recruiter conversation, I moved through a sequence of rounds that added up to four interviews in total. The conversations were professional and engaging, with a clear throughline from core coding to broader engineering thinking.
My loop started with a very detailed low-level design round where I had to design a trade reconciliation service. The interviewer was knowledgeable and helpful, but I could feel the bar for clarity and completeness was pretty strict. I left that first technical round realizing a few gaps in how I’d been preparing.
The interview process typically begins with a recruiter call, followed by a technical screen, and then a loop of four to five interviews covering coding, systems design, and behavioral topics. The timeline can vary, with some candidates experiencing quick feedback while others face delays of several weeks or months.
Candidates should prepare for a mix of coding challenges, system design discussions, and specific technical topics like distributed systems, cloud architecture, and data structures. The interviews often require candidates to demonstrate both problem-solving skills and a deep understanding of technical concepts.
Behavioral interviews are a key component, focusing on past experiences and alignment with company values. Candidates are often asked to describe situations using the STAR method, emphasizing teamwork, leadership, and problem-solving approaches.
The overall difficulty of the interviews is generally considered high, with many candidates reporting a fast-paced environment that tests their ability to think under pressure. Specific coding tasks can be challenging, and interviewers may push for clarity and depth in responses.
Candidates noted varying experiences with communication throughout the process, with some feeling well-informed and others experiencing long delays without updates. Feedback during interviews is often constructive, but the lack of follow-up after the final rounds can leave candidates feeling uncertain.
Candidates reflected on the importance of targeted preparation, especially in areas like low-level design and specific technologies relevant to the role. Many wished they had practiced more with the specific coding environments or frameworks used during the interviews.