Glassdoor users rated their interview experience at Oracle as 66.7% positive with a difficulty rating score of 3 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for HR Administrator and Territory Manager rated their interviews as the hardest, whereas interviews for HR Administrator and Sales Consultant roles were rated as the easiest.
The hiring process at Oracle takes an average of 49 days when considering 3 user submitted interviews across all job titles. Candidates applying for HR Administrator had the quickest hiring process (on average 21 days), whereas Sales Consultant roles had the slowest hiring process (on average 90 days).
straight to the point. if your resume is impressive, you are hired. there were 3 rounds. first one is test, the second round was interview with employees/team manager, third was hr round
Interview questions [1]
Question 1
describe your project. what is polymorphism. stack questions. practice dsa from striver, you are good to go.
Foram 3 fases, mas acho que poderiam ser duas. Gostei por não ter sabatina técnica e o pessoal foi sincero sobre o que estavam buscando. Foi uma conversa bem agradável, limpa e respeitosa.
Recently, I had the opportunity to interview for the Senior Java Microservices Developer role at Oracle, and it was both technically enriching and intellectually stimulating. Here’s a detailed account of the key questions, my thought process, and the learnings from the entire experience.
Interview questions [1]
Question 1
1. Project Discussion:
I was asked to explain the current architecture of my project. I spoke about our microservices-based payment platform using Spring Boot, Kafka, Redis, and PostgreSQL.
2. Deep Dive into Challenges:
They asked about the most challenging issue I faced. I shared how we handled message duplication and retries when Kafka consumers failed and how we used Redis for idempotency.
3. Core Spring Concepts:
Questions included: Scopes of Spring beans, Use of Prototype scope and related implementation, Common mistakes with Singleton beans, How to exclude packages from component scanning
4. Transaction Management:
They asked about @Transactional and how Spring manages transactions under the hood.
5. JPA & Hibernate:
Topics included: Features of JPA, Optimizing queries to prevent repetitive DB hits
6. Kafka Scenario-Based:
A practical scenario: what to do when a Kafka producer fails. I explained storing failed messages, retry strategies, DB optimizations, and caching using Redis.