Getting an Interview
Getting an Interview
Interviews for Top Jobs at Oracle
- Software Engineer (124)
- Applications Engineer (69)
- Business Development Consultant (60)
- Member of Technical Staff (58)
- Senior Software Engineer (55)
- Associate Consultant (52)
- Applications Developer (48)
- Inside Sales Representative (45)
- Sales Representative (43)
- Senior Member of Technical Staff (34)
- Software Developer (27)
- Sales Consultant (22)
- Consultant (22)
- Business Analyst (21)
- Senior Applications Engineer (20)
- Account Manager (20)
- Applications Sales Representative (19)
- Senior Consultant (19)
- Principal Consultant (19)
- Engineering (16)
- Intern (16)
- Associate Sales Representative (14)
- Hardware Engineer (14)
- Director (14)
- Senior Sales Consultant (14)
- Staff Consultant (13)
- Software Developer II (13)
- Account Executive (13)
- QA Engineer (12)
- Product Manager (11)
Software Engineer IV Interview
I applied through a recruiter. The process took 1+ week. I interviewed at Oracle (Santa Clara, CA) in July 2013.
Phone interview was technical. Coding questions on binary trees, find the error in some code. Also on mutex, locks, memory management. Onsite interview was also some coding on bitmaps, binary trees, mutexes. Not too difficult. People were nice.
- A puzzle Answer Question
Reasons for Declining
Salary was lower than market.
Other Interview Reviews for Oracle
Software Engineer IV InterviewAccepted OfferPositive ExperienceAverage Interview
I applied online. The process took 4+ weeks. I interviewed at Oracle (Burlington, MA) in March 2013.
- Applied via Oracle.com website. - Recruiter called for phone screen - Hiring manager called for short interview - Onsite interview with hiring manager and some team members - 4 hours. Some technical challenge whiteboard questions which were basic and reasonable. - Onsite interview with group manager - Phone interview with remote team member - Request for references - Request for background check to verify statements on resume - Background check for criminal history
- One technical interview, go to the whiteboard, write some code which does XXXX. 1 Answer
Appears to be a big company with a lot of "process" in hiring. It appears to be better to negotiate salary, etc. before the offer is made because going back to change an offer appears to require a lot of justification, signatures, delays.
Software Engineer IV InterviewAccepted OfferNeutral ExperienceEasy Interview
I applied through an employee referral. The process took 3 days. I interviewed at Oracle (Santa Clara, CA) in August 2011.
One phone interview, then an afternoon of 1:1 interviews on site. After that, another day of 4 1:1 interviews, and finally a phone negotiation with HR. First technical interviews were very standard and focused on my background and included a group interview and impromptu presentation. Questions focused on Java programming and some general algorithm analysis, as well as one or two 'brain teaser'/problem solving questions. Second set were more geared towards fit and focused on goals, interests, and chances for me to ask questions.
- Two people are each stuck on their own island, connected by a ferryman with a lockable box. Each person has their own lock and key, but can't send the key along with the box. One person wants to send the other a diamond, but it must be placed into the box and locked or it will be stolen by the ferryman. How do you send the diamond without the ferryman stealing it? 5 Answers
I didn't need to negotiate much as I wasn't looking for a salary bump. I was more interested in the change of responsibility. It helps to hone in on your desired salary and position up front, because there's not much else that can be negotiated. You will want to agree to everything because once it hits Larry Ellison's office and gets his approval there's not much else that can be changed.