Oracle Software Engineer interviews reported by candidates mix easy-to-medium DSA with SQL, Java fundamentals and resume deep dives, across roughly three to five rounds that vary by team.
$137K
Avg. Base Comp
$210K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Oracle Software Engineer interview as a mix of coding and conversation, and the balance changes by team. Most reports center on easy-to-medium DSA problems. These include string and list manipulation, arrays, hash maps, backtracking such as a Word Search-style problem, and a HackerRank-style Closest Numbers problem. One candidate started with an online coding challenge along the lines of a sum-finder.
Several candidates also describe fundamentals checks. SQL joins and GROUP BY come up, as do Java memory management, Java OOP and Python-versus-Java differences. In one account, Spark concepts and functional operations such as map, flatMap, filter, fold and reduce also came up. One candidate had one round in Python and another that had to be in Java, so expect the languages on your resume to be tested.
Resume depth matters too. Candidates report rounds built around their own projects, including one where an architect pressed hard on design decisions, so be ready to defend every bullet. Behavioral questions and a hiring manager conversation typically close the process.
Outcomes are mixed, with both offers and rejections reported. Candidates stress explaining your reasoning aloud and communicating clearly in English. One candidate had only about 12 minutes left for a live coding problem after a long stretch of CV questions, so keep early answers concise. Another never heard back after the recruiter screen, while one offer arrived about a week after the final interview.
Synthesized from 178 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Oracle process.
The question I still think about wasn't on a whiteboard. In my second round, the software architect spent most of the time going through a project on my resume and asking me to defend the decisions I'd made. I had prepared mostly for coding, so being pushed hard on my own work caught me off guard, but it turned out to be the most useful part of the day.
The loop had three rounds. The first was with a senior engineer on the team, who asked about my past experience and then gave me an easy string problem from LeetCode. It wasn't tricky, but I still had to talk through my approach and cover edge cases. The second was the architect round I mentioned, a resume grill focused on projects and tradeoffs. The last was with the hiring manager, which was mostly a confirmation conversation plus a walkthrough of how my past work lined up with the team.
The coding questions were medium difficulty and centered on core DSA. Some of the technical questions weren't about algorithms at all. They covered Spark concepts and functional programming fundamentals like map, flatMap, filter, fold, and reduce, so I'd recommend being comfortable with those alongside the usual problem-solving practice.
I accepted the offer at the end of the process.
Prep tip from this candidate
Be ready to explain map, flatMap, filter, fold, and reduce precisely, along with the Spark concepts around them, since they came up alongside the DSA questions. Also prepare to defend every project on your resume in detail, because one round was essentially a full resume grill.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Oracle
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Closest SAT Scores | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| String Shift | |
| Upsell Transactions | |
| Largest Salary by Department | |
| Minimum Change | |
| Scrambled Tickets | |
| Rectangle Overlap | |
| Project Pairs | |
| Integer to Roman | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Size of Joins | |
| The Brackets Problem | |
| Nearest Common Ancestor | |
| Normalize Grades | |
| Basic Regex | |
| Resumable Fact Table Load | |
| Cyclic Detection | |
| Sort Strings | |
| Binary Tree Conversion | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Finding The Mode | |
| Production Model Monitoring | |
| Dijkstra implementation | |
| Target Indices |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call or online assessment that covers experience, skills and resume projects. Some accounts add work authorization, basic CS questions, or a behavioral prompt about solving a problem. One candidate was asked about experience with query optimization tools.
Candidates typically describe LeetCode- or HackerRank-style problems on strings, arrays, hash maps and backtracking, including a Word Search-style problem and Closest Numbers. Interviewers appear to watch how you explain your approach and handle edge cases, not only the final code.
Several candidates report fundamentals questions alongside coding: SQL joins and GROUP BY, Java OOP and memory management, and Python-versus-Java differences. One account also mentions Spark and functional operations such as map, flatMap and reduce. Which topics appear likely depends on the team and the languages on your resume.
Candidates report rounds focused on past projects and resume bullets, including an architect pushing hard on design decisions and tradeoffs. Expect to explain why you made each choice rather than recite a template.
Candidates commonly describe a closing hiring manager or HR round covering behavioral questions, project walkthroughs, and how past work fits the team. One candidate received an offer about a week after the last interview, while others report little feedback or no follow-up.
