My Oracle ASE On-Campus Interview Experience
Anonymous User
139

Getting placed at Oracle as an Associate Software Engineer (ASE) has been one of the most exciting and defining milestones of my college journey. The process tested not only my coding skills but also my ability to stay calm under pressure, explain my thought process clearly, and demonstrate strong fundamentals.

Below is a structured walkthrough of my interview experience:

⸻

Round 0 – Online Assessment (OA)

The Online Assessment was designed to filter candidates based on problem-solving and CS fundamentals. It had two parts:
1. MCQs covering:
• Operating Systems (CPU scheduling, deadlocks, paging vs segmentation)
• DBMS (normalization, indexing, transactions, isolation levels)
• Networking (TCP vs UDP, OSI layers, IP addressing)
• OOPs & general CS fundamentals
• Aptitude and logical reasoning
2. Coding Section (2 questions):
• Dynamic Programming problem
• Bit Manipulation problem

The OA was intense and time-constrained, requiring not just problem-solving but efficiency. Cracking it gave me confidence for the interviews ahead.

⸻

Round 1 – Technical (DSA + CS Fundamentals)

The round began with a casual introduction about my background, family, hobbies, and college life, which helped ease into the technical part.
• Projects Discussion: I explained my academic and personal projects, highlighting design choices, scalability, and problem-solving approach.
• DSA Questions:
1. Detect cycle in a Linked List → Explained Floyd’s Cycle Detection Algorithm (Tortoise & Hare).
2. Dijkstra’s Algorithm → Discussed logic, applications (like Google Maps shortest paths).
3. Linked List Implementation → Step-by-step node creation, insertion, traversal.
• CS Fundamentals: OOPs (inheritance, polymorphism), DBMS (indexing), OS (process vs thread).

This round focused on concept clarity and connecting algorithms to practical use cases.

⸻

Round 2 – Technical (MERN + Problem Solving + System Concepts)

This round explored my development skills and applied problem-solving abilities.
• Web Development / MERN Stack:
• Why React over plain JS?
• Use of Context API
• SQL vs NoSQL (MongoDB differences)
• Scalability of MERN applications
• Coding Challenges:
1. Delete the middle node of a Linked List (handling both even/odd cases).
2. Find triplets with sum = 0 → Efficient hashing approach expected.
• CS Fundamentals:
• TCP vs UDP (applications like video calls vs file transfer)
• OS: paging vs segmentation, CPU scheduling policies
• DBMS scaling approaches
• Resume Projects: Discussed motivations, tech stack choices, challenges faced.

The interviewer also asked “Why Oracle?” → I emphasized Oracle’s global impact, culture of learning, and opportunities to solve large-scale problems.

⸻

Round 3 – Managerial + Technical (Deep Dive)

This was the most challenging and insightful round. It combined technical design, behavioral skills, and culture fit.
• Design Task:
• Create a Low-Level Design (LLD) for a Kisan Help App
• Draft UML diagrams & database schema
• Explain implementation of features: farmer registration, crop suggestion, weather alerts
• Behavioral Questions:
• How do you handle team conflicts?
• What if you miss a deadline?
• Share a time when you made a tough decision under pressure.
• Culture Fit Discussion:
The interviewer shared about Oracle’s work culture, mentorship, and collaboration. I highlighted my values of teamwork, structured thinking, and continuous learning.

This round tested my ability to design, reason, and communicate effectively.

⸻

Round 4 – HR Round (Closure)

The final round was relaxed and focused on:
• Role expectations and growth opportunities at Oracle
• Relocation and work environment flexibility
• My long-term goals and how Oracle fits in

The HR left me with a very positive impression, making it a warm closure to an intense process.

Comments (1)