Principal Software Engineer applicants have rated the interview process at Oracle with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 54% positive. To compare, the company-average is 64% positive. This is according to Glassdoor user ratings.
Candidates applying for Principal Software Engineer roles take an average of 32 days to get hired, when considering 43 user submitted interviews for this role. To compare, the hiring process at Oracle overall takes an average of 33 days.
Common stages of the interview process at Oracle as a Principal Software Engineer according to 43 Glassdoor interviews include:
Phone interview: 23%
One on one interview: 20%
Skills test: 14%
Presentation: 9%
Group panel interview: 9%
Background check: 9%
Personality test: 6%
IQ intelligence test: 5%
Drug test: 3%
Other: 2%
Here are the most commonly searched roles for interview reports -
Hiring Process is stringent.There would be many techinical rounds & atleast 2 managerial rounds.Recommend people applying for Oracle to have thorough knowledge in thier subject areas and prepare v well for the interviews.
Interview questions [1]
Question 1
Too Many technical questions by multi talented people at Oracle. There were some interesting aptitude questions as well. :)
I applied through a recruiter. I interviewed at Oracle (Seattle, WA)
Interview
Fairly easy tech screen. Loop was a bit of a mess. Coding portions required AI which was not mentioned ahead of time. One of the interviewers told me to find bugs in some code using AI, but accidentally pasted the solution instead of the buggy code which led to issues.
I applied through an employee referral. I interviewed at Oracle (Nashville, TN)
Interview
Standard coding screen followed by loop rounds.
Loop rounds -
1. System design - focused on the infra aspect more
2. Behavioral - turned into technical quickly and did some white boarding to explain how I cracked a problem.
3. Bartender - as they are all from platform team, most of their questions were targeted for infra position and that confused me.
Bias for action seemed very important for them than any other principle.
Coding - another leetcode medium and was easy to solve.
Interview questions [1]
Question 1
System design - Youtube using barebones infra instead of ootb services
The interviews were mostly medium level leetcode questions. Takes a lot longer than you would expect. About 3 months from beginning to end. The offer stage and background stage take the longest