Rewritten from public student write-ups for Oracle’s India campus roles (Application Engineer / ASE / Application Developer). The consistent surprise for candidates who prepare only LeetCode: Oracle’s campus rounds lean heavily on MCQ aptitude, tree variants, C-level memory questions, and DBMS internals rather than on contest-style algorithm problems.
Not a coding round. Sections covered numerical aptitude, reading comprehension, logical reasoning, data structures (heavy on trees, including AVL trees and code-snippet output questions), and software engineering concepts.
Round 2 - technical interview 1
Introduction, then puzzles: the three-ants-on-a-triangle problem, a pattern-formation exercise, and arranging digits to form the smallest number.
Followed by OS, DBMS, and data structures questions.
Round 3 - technical interview 2
ACID properties and database concepts.
OOP fundamentals.
Linked list implementation with raw pointers, then memory management: malloc/free, destructors, memory leaks, dangling pointers. C/C++ fluency was assumed.
Round 4 - technical + HR
Tree types, Red-Black trees with a code implementation, basics of machine learning, Oracle’s autonomous database, REST APIs, cloud concepts, threads, Linux commands, ER diagrams.
Behavioural close: background, motivation, and how Oracle compares with competing offers. Reports across write-ups agree this last part tests honesty more than polish - candidates who over-claimed on other offers were pushed on it.
The process shape is stable: an online test, two technical interviews, and a combined technical + HR round is the pattern repeated across Application Engineer and ASE write-ups from several years.
Trees are the recurring DSA theme - binary trees, BSTs, AVL and Red-Black trees show up far more often than graphs or DP.
SQL and DBMS are non-negotiable. Expect to write queries, explain joins, normalisation, and ACID, and to defend a schema.
Puzzles still appear, especially in the first technical round. Think aloud rather than going quiet.
After technical rounds, Oracle usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.