← Interview experiences
Got the offer

Project Intern(Internship) at Oracle

Difficulty
Process took
2-3 Weeks
Rounds
4
Format
Hybrid
Applied via
Other

How it went

  • Stay calm under ambiguous questions, scenario-based questions are not about right answers, but about thought process, communication, and logic.

What they would tell you

  • Stay calm under ambiguous questions, scenario-based questions are not about right answers, but about thought process, communication, and logic.

How to prepare

  • Prepare DevOps fundamentals only if your resume hints at it. In my case, since I had touched DevOps in an internship, the first round went deep into it.

Round by round

  1. 1

    Online Assessment90 min

    The first round was an online assessment with two DSA-based questions, both of medium difficulty.The focus was on testing our core problem-solving and coding skills.

  2. 2

    Technical Interview 1 (Resume + DevOps + Coding)60 min

    The interview began with a quick introduction and a few resume-based questions. Since one of my internships had DevOps exposure, the interviewer, who was from Oracle’s DevOps team, steered the discussion heavily in that direction. We talked about CI/CD pipelines, containerization basics, and tools like Jenkins and Docker. Then we moved to the coding section. The round ended with an informal chat about the future of DevOps, cloud-native development, and automation trends. It was a balanced round and went well overall.

  3. 3

    Technical Interview 2 (Projects + Theoretical Concepts)60 min

    The interviewer started by going through my resume and asked me to explain my AWS-based projects in detail. We discussed the services I used like EC2, S3, and Lambda, along with the overall architecture and the decisions I made during the project. After that, the interviewer moved to some theory questions, like:

    • What is multithreading and how would you use it in a web server?
    • What’s the difference between threads and processes?
    • What is thread safety and how can you avoid race conditions?
  4. 4

    Director Round (Tech Strategy + Culture Fit)60 min

    This round started with a summary of my performance in previous rounds. The Director had already reviewed the feedback and wanted to dive deeper into my architectural thinking. Topics discussed:

    • Monolith vs. Microservices
    • A few scenario-based questions, like:
    • “If you were given an application with scaling issues, how would you debug and redesign it?”
    • Final 5–10 mins were spent on general behavioral questions: Why Oracle? What kind of work excites you? How do you work in teams and handle disagreements?

What came up

MediumHybrid0 1 years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources