Interview Experience - 181 - Oracle | Application Developer - 1 | IC-1
Summary
Job Role: Software Development (Application Developer - 1)
Number of Rounds: 4 (2 Technical + 1 Managerial + 1 Director)
Offer Status: Rejected
Location: Hyderabad
Candidate Name: Not disclosing due to privacy reasons
Candidate Experience: 1.9 years of experience
Interview Process
The interview process at Oracle for the role of Application Developer - 1 consisted of four rounds. Two were technical, followed by one managerial and one director round. All the rounds were conducted on the same day, which made the process quite intensive and slightly tiring as well.
The panel was professional and structured. Each round had a mix of problem-solving, coding, and concept-based questions, with some rounds extending into project discussion and behavioral aspects.
Preparation Guide
For this interview, the candidate primarily relied on prior work experience and conceptual understanding. No specific preparation sources were mentioned, but the nature of questions indicated that strong knowledge of data structures, algorithms, OOP concepts, and some system design aspects were essential.
Additionally, reviewing Java fundamentals and brushing up on JavaScript concepts would have been beneficial given the flow of questions. Puzzles and backtracking problems were also a part of the process, so practicing standard problem patterns is advisable.
Interview Rounds
Round 1: Technical Round 1
Duration: ~45 minutes
Difficulty Level: Medium
Experience:
The interviewer created a friendly and authentic environment, which helped set a positive tone. The round focused on coding and problem-solving skills.
Questions asked:
Search for a target value
xin a matrix where the rows and columns are sorted in ascending order.Given a binary tree, print the left view of the tree.
Additional questions on OOP concepts and Java fundamentals.
The candidate successfully solved both coding problems and was able to answer the OOP and Java-related questions. Since some time was left, the interviewer utilized it to test conceptual knowledge, which is a common practice in such rounds. Feedback from the interviewer was positive, indicating satisfaction with both coding ability and conceptual understanding.
Key Learnings:
Always be prepared for additional questions in case you finish early. Interviewers often test breadth in concepts when time permits.
Round 2: Technical Round 2
Duration: ~50 minutes
Difficulty Level: Medium
Experience:
This round began with a focus on JavaScript, as the candidate had listed it as an expertise area on the resume.
Questions asked:
What is a closure in JavaScript?
What are promises in JavaScript?
Given a matrix of
m x n, print the matrix in spiral order.
The candidate was able to confidently answer the JavaScript-related questions since they had prior understanding of those concepts. For the coding problem, the candidate directly proposed the optimal approach, which impressed the interviewer. They then implemented and tested the code with sample test cases, and the solution worked well. The interviewer gave positive feedback in this round as well.
Key Learnings:
Be careful while adding skills or expertise in your resume. If a technology is listed, expect detailed questions on it. It is important to be comfortable with every tool or language you mention.
Round 3: Managerial Round
Duration: ~60 minutes
Difficulty Level: Difficult
Experience:
This round had a mix of technical depth, design discussions, puzzle-solving, and behavioral questions.
The interviewer began with an introduction and discussion about past projects. The candidate was asked to explain:
High-level design (HLD) of one of the projects.
The data model used.
Trade-offs made and considerations for concurrency handling.
Following that, the interviewer presented a puzzle:
Find the angle between the hour and minute hand of a clock.
The candidate gave the correct formula and approach but made a mistake while applying it to the example provided.
Next, the interviewer shifted to a coding problem:
Given an 8x8 chess board, arrange 8 queens such that no two queens attack each other.
The candidate proposed a backtracking approach, coded the solution, and explained it well. The interviewer seemed satisfied with the coding part.
Finally, the round ended with a few behavioral questions focused on teamwork, problem ownership, and handling challenges.
Key Learnings:
This round highlighted the importance of being versatile—comfortable with puzzles, design discussions, and behavioral aspects in addition to coding. Practicing puzzles beforehand and being prepared to talk in depth about past projects and design decisions is very important for managerial rounds.
Final Thoughts
The overall process was rigorous and well-structured. The technical rounds evaluated coding skills, core computer science concepts, and language fundamentals, while the managerial round focused on broader aspects like design, problem-solving ability, and behavioral fit.
Even though the final outcome was a rejection, the interview provided a good learning experience. Some important takeaways for future candidates include:
Be very careful with what you mention in your resume; you will be asked to prove expertise in those areas.
Strong fundamentals in data structures and algorithms are essential.
Managerial rounds often include puzzles, system design discussions, and behavioral questions. Be ready for a holistic evaluation, not just coding.
Time management and clear explanation of approaches matter as much as solving the problem.
Overall, this experience reflects the balanced approach Oracle takes in evaluating both technical competence and overall fit for the role.