Oracle-OCI interview experience | IC3 | USA
Summary
I recently interviewed for an IC3 role at Oracle-OCI in the USA. The interview process consisted of several rounds, including object-oriented design, behavioral discussions, and two LeetCode medium problems. I have not yet received an offer.
Full Experience
I applied for a position on the Oracle portal, and a recruiter reached out to me. The scheduling process was smooth, but I didn't receive much information about what to expect in the interviews.
My first round was focused on Object-Oriented Programming (OOP). I was asked to write code to design a game and its player characters. The interviewer was primarily interested in my approach to designing classes, subclasses, and methods, rather than the specific game logic itself.
Following that, I had a series of onsite virtual loops:
- Round 1 (IC4 from another team): This was a 1-hour technical round. I spent about 50 minutes on a LeetCode medium problem, which was related to arrays and stacks. The remaining 10 minutes were for Q&A.
- Round 2 (Sr. PM from another team): This 1-hour round was entirely behavioral, focusing on my working style and past experiences.
- Round 3 (Hiring Manager): A shorter 35-minute session with the Hiring Manager. We discussed team fit for about 20 minutes, followed by 15 minutes for my questions.
- Round 4 (IC5): Another 1-hour technical round. I spent about 40 minutes on a LeetCode medium problem involving a tree structure. The first 10 minutes were for intro and behavioral questions, and the last 10 minutes for Q&A.
- Round 5 (IC4): This was a 1 hour and 10 minutes round. After a 5-minute introduction, I spent 55 minutes on a specific LeetCode medium problem, Minimum Area Rectangle. The remaining 10 minutes were for Q&A.
I noticed that the LeetCode questions I encountered were not from the commonly tagged Oracle list on LeetCode.
Interview Questions (2)
I was asked to write code to design a game and its player characters. The interviewer's focus was on assessing my ability to design classes, subclasses, and methods using object-oriented principles, rather than the specific game logic.