Oracle Health Software Engineer interview: five-hour loop and existing Java codebase

Oracle Health·Software Engineer·Reported Jul 2026
Technical ScreenHard

A recruiter contacted me about two weeks after I applied. The recruiter call was basic, and a technical screener was scheduled for the following week. That first technical conversation was friendly and straightforward, almost a check on basics such as if-else control flow.

The final loop was much harder to arrange: five separate one-hour interviews spread across a week, and I took PTO to make it work. The systems interview was almost entirely one large design prompt about taking client information, sending it to servers, saving it in a database, and letting another customer retrieve it.

The other technical interviews felt more tied to context-specific knowledge than transferable engineering skills. One round was described as coding, but I had to write code inside a large existing Java codebase. I spent much of the time understanding the unfamiliar project structure, dependencies, and framework behavior rather than showing general coding and debugging ability.

The process felt long and high friction, and I did not get an offer. Looking back, I felt the outcome depended too much on readiness for a specific ecosystem rather than strong fundamentals.

Location: Boston, MA. Overall feedback: negative. Offer status: no offer.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Oracle Health
Role
Software Engineer
Rounds
Technical Screen
Difficulty
Hard
Date
Reported Jul 2026

Real Oracle Health interview experiences

First-hand reports from Oracle Health candidates — the rounds, the questions they were asked, and how it went.

All 9 Oracle Health interview experiences