Oracle || OMCS || On-campus || /

I interviewed for a Technical Analyst / Programmer Analyst position at Oracle in /. I am a graduate from a Tier-1 college. The interview process consisted of an online coding assessment and a single onsite round.

The online coding assessment included a dynamic programming question, a difficult SQL problem, an API implementation problem, and 6 multiple-choice questions. I was able to solve the dynamic programming and SQL problems completely, and I believe I answered all the multiple-choice questions correctly. I was then invited for the onsite interview.

The onsite interview was conducted by 4 panelists and lasted for approximately 1 hour and 20 minutes. The interview covered a range of topics, including my resume, previous work experiences, projects, and technical skills.

The panelists asked me to explain my projects and to rate my proficiency in various skills mentioned on my resume, such as React, CSS, JavaScript, data structures and algorithms, competitive programming, and MongoDB. I indicated that I was most proficient in data structures and algorithms. I was then asked to explain a data structures and algorithms problem that I had recently solved, which I was able to do.

One of the panelists then asked me about my proficiency in React, JavaScript, and MongoDB. I explained that I was not an expert but had a good understanding of these technologies. I was then asked to write code for React Router DOM, which I was able to do with a few minor errors that I corrected. I was also asked about React hooks, Redux, props, and lifecycle methods in React. I was able to explain the theory but struggled with writing code. I mentioned that I had previously relied on copying code from React's documentation during an internship, which elicited laughter from the panelists.

The interview also included general HR questions, such as why I was interested in Oracle, my favorite subjects in college, why my resume was software-oriented despite my non-CS background, my hobbies, and my ability to work under pressure. I answered these questions using the STAR technique.

One of the panelists then asked me questions about MongoDB, MySQL, and object-oriented programming. I explained the difference between MySQL and MongoDB and why I chose MongoDB for my project. I was also asked to write code for inserting data into MongoDB and to explain how to fetch data from a database. I was able to answer these questions. I was then asked about exceptions in MySQL, which I was not familiar with. I attempted to answer by discussing normalization.

Overall, the interview was challenging but rewarding. I was selected for the position. My advice to future candidates is to be prepared to answer questions about all the skills mentioned on your resume and to be comfortable discussing your projects in detail. Be prepared to answer general HR questions and to think on your feet. It is also helpful to have a water bottle with you during the interview.