Oracle - MTS 2025 On Campus Internship
Summary
I recently received an on-campus internship offer from Oracle for the Member of Technical Staff (MTS) – Project Intern role. This post details my entire journey, from shortlisting and the online test to three rounds of personal interviews, offering preparation tips and personal takeaways for future aspirants.
Full Experience
Oracle MTS 2025 - Project Intern
Stipend - 1.25 L
B.Tech - NIT Trichy Circuital Department
Process Structure - OT followed by 3 rounds of PI.
I recently received an on-campus internship offer from Oracle for the Member of Technical Staff (MTS) – Project Intern role. In this article, I’ll share my entire journey — from shortlisting to interviews — along with some preparation tips and personal takeaways for future aspirants.
There was resume shortlisting or rather cg based shortlisting. Cg criteria was around 7.8 iirc. People above that were shortlisted for OT. It was open for circuital departments only
OT:
OT had 3 sections:
(i) DSA- There were 2 DSA questions, different for everyone. For me,
You are given a string with 0 and 1, and whenever you get 01, you need to make it 10. So in one iteration of string all 01 gets converted to 10, Every iteration counts to 1 second, we had to return the min no of seconds required so that there will be no more swaps.
Eg — 10101
So in sec 1- 11010
Sec 2- 11100
Ans- 2
2. Graph question was there, i dont remember it exactly, but you were given a start node and an end node, you were also given some nodes which had points, so you needed to start from the starting node and cover all the nodes with points and reach end node in minimum time.
I just brute forced it by taking a set for every possible path, it passed all the available test cases.
There were only 3 visible test cases.
(ii) CS Fundamentals + ML MCQs- These questions covered networking, OS, DBMS, ML as well. Questions were really good, so if you haven’t seen them before you won’t be able to attempt it.
(iii) General Maths, Reasoning, Comprehension MCQs- Basic maths, 3 comprehension paragraphs and a few reasoning questions were there.
Idk how many exact questions were there but ig around 30 MCQs were there.
I solved both the DSA problems, well brute forced it tbh. Then MCQs were mostly repeated so I had that figured out as well.
Tip — Try to finish OT asap, solving it quickly increases your chances of getting a PI call.
PIs:
I had 3 rounds. Pis were offline, pen and paper, so the paper that was used to solve questions is stapled along with the resume and goes to the next rounds for reference. PIs slot is important as people finishing their pis first were mostly the ones that got selected, so again a bit of luck involved. I will put some tips in between and some generic ones at the end.
PI 1:
I was a bit nervous, but as soon as I entered the room, the interviewer shook my hand, gave his intro and made me a bit comfortable. He started to take a look at my resume, he started with the CS minor that i had in my resume. (Tip — if you’re non CS, minor in cs are a big advantage is what i felt). He then started asking me what all courses I have done in CS minor. I said DSA and DBMS going on this sem, but I also mentioned I know OS and all as I did it on my own. So he asked me the difference between paging and segmentation, what is fragmentation, where does internal fragmentation happen. He then moved on to DSA, where he gave me a simple min heap problem saying to find top k most frequent elements. He aslo asked binary search in matrix question. He asked me the difference between dijkastra and bellman ford, TC of dijkastra, which algo is bellman ford based upon greedy or dp. He then moved to DBMS, asked me to write a simple SQL query, pretty basic. (Tip- Try to do SQL top 50 problems on Leetcode, it was a big help). I asked him a bit of a generic question like what do you expect of us interns at Oracle. Overall PI overall went for about 40–45 mins.
PI 2:
For PI2 again the interviewer started with his intro and asked me for my intro. Later on he looked at my resume. Also he looked at the paper on which i had my last PI, it had everything covered but my projects, so he started with my projects. Asked me to explain Lynx 2.0, and another of my React Native projects with node backend. Asked a bit about what I worked on in Lynx. For the next 15-20 mins he was just asking about REST Apis. To and fro. His questions were not direct, for example I remember he asked me what I would do before getting a response from the backend and showing it on my frontend. By this he wanted to know about status codes lmao. So yes all about rest apis, status codes, different http methods, difference between put post, idempotency of rest api, about rest architecture in general. (Tip — Know your projects, its techstack end to end, you don’t know what the interviewer might dive deep into). After this he asked me an oops question. About polymorphism, its types and some examples. And in the end I asked him about his oracle experience, he went on for about 5 mins. PI lasted about 30- 35 mins.
PI 3 (HR) :
I was told to have lunch after PI2 so just after returning, i got PI 3 call, this was very chill, an old guy just asking me questions like what is ICE? Why NITT? Why do something that is not your core? Why interested in CS?
And then some questions on Javascript, React Native and what was my experience in working in a team.
He asked me twice do i know ML? I replied no, I am planning to explore it as soon as I land an internship. So yeah pretty chill. I asked him one generic question in the end as well.
Some generic PI tips:
- Be confident. Even if you don’t know anything, use words like i haven’t explored it and show curiosity that you’re interested in learning it.
- DSA questions will mostly be easy and something that you might have already seen so explain properly, tc, approach everything.
- Always always ask some generic question at the end of PI, this makes some impact.
- Never say i dont know or be silent during pis. Lets say you have some tuff dsa problem, while solving think out loud dont just go in a shell and then say after you’ve figured out the problem, they are more interested in knowing how you approach a problem.
- Oracle sometimes asks puzzles as well, it didn’t happen to me but yeah please do gfg top 50 puzzles.
All the very best :)
#Oracle #InternshipExperience #NITTrichy #CampusPlacement #SoftwareEngineering #DSA #CareerJourney
Interview Questions (10)
You are given a string with 0 and 1, and whenever you get 01, you need to make it 10. So in one iteration of string all 01 gets converted to 10, Every iteration counts to 1 second, we had to return the min no of seconds required so that there will be no more swaps. Eg — 10101, So in sec 1- 11010, Sec 2- 11100, Ans- 2
Graph question was there, i dont remember it exactly, but you were given a start node and an end node, you were also given some nodes which had points, so you needed to start from the starting node and cover all the nodes with points and reach end node in minimum time.
difference between paging and segmentation, what is fragmentation, where does internal fragmentation happen.
simple min heap problem saying to find top k most frequent elements.
binary search in matrix question.
difference between dijkastra and bellman ford, TC of dijkastra, which algo is bellman ford based upon greedy or dp.
For the next 15-20 mins he was just asking about REST Apis. To and fro. His questions were not direct, for example I remember he asked me what I would do before getting a response from the backend and showing it on my frontend. By this he wanted to know about status codes lmao. So yes all about rest apis, status codes, different http methods, difference between put post, idempotency of rest api, about rest architecture in general.
oops question. About polymorphism, its types and some examples.
what is ICE? Why NITT? Why do something that is not your core? Why interested in CS?
what was my experience in working in a team.
Preparation Tips
I prepared by focusing on Data Structures and Algorithms, mentioning that many Online Test MCQs were repeated, and solving SQL top 50 problems on Leetcode. I also self-studied Operating System concepts. For interviews, I was advised to be confident, explain DSA approaches (including time complexity and approach), always ask generic questions at the end of a PI, and think out loud when solving tough problems. It was also critical to know my projects and their tech stack end-to-end. Finally, I was encouraged to do GFG top 50 puzzles as Oracle sometimes asks them.