Taro Logo

Software Engineer Interview Experience - Seattle, Washington

October 1, 2019
Negative ExperienceNo Offer

Process

I reached out to the hiring manager. He gave me an initial call and informed me about the product and the overall interview process.

Then, I received a phone call interview invite. It was a 45-minute round where I programmed an easy-level LeetCode question on CoderPad.

After that, I received an onsite interview invite. It was my fourth onsite interview, and I had cleared all three previous interviews. However, this interview turned out to be the worst interview experience ever.

The onsite interview started with a LeetCode question, LRU Cache, which I solved quickly on the whiteboard. The interviewer was kind, and we had a good discussion about the team and their projects.

The second round was a system design interview. The interviewer was very rash. He started laughing as soon as he entered the room. He gave me a question and asked me to use the whiteboard to explain. As soon as I started, he said, "Sit down," and changed his mind to ask me about some random sorting algorithm. I explained that, and he started looking at my resume and laughing again. I really didn't understand his behavior.

The third round was a lunch interview with the hiring manager. He asked me some behavioral questions, and after lunch, we sat together to answer some Oracle values questions. He then asked me to solve a LeetCode question to determine if a number is a perfect square, which I solved quickly on the whiteboard. It was a good interview overall.

The last interview was again very disappointing. The interviewer was a senior software engineer. He gave me a simple array question. When iterating over the array, I incremented the index like this: 'index++'. As soon as I did that, he started arguing with me, saying this would increment the index first and then reach the next index. Initially, I thought he was trying to confuse me, but later it turned out that he didn't know. He didn't agree with what I said.

Anyway, he then asked me to change the array to a list because a list would give O(1) lookup, not arrays – this is what he said during the interview. I didn't know what to do there. I changed the array to a list, lol.

The final interview was behavioral with a member of another team. It was a good interview with many behavioral questions.

Overall, the interview process was very disappointing. If an interviewer lacks fundamentals, it is very difficult to clear the interview, as they will never listen to you.

I traveled to Seattle a month ago but still haven't received my reimbursement.

Questions

LRU Cache

Find if a number is a perfect square or not.

Array-based LC question (I don't remember exactly).

Was this helpful?

Interview Statistics

The following metrics were computed from 22 interview experiences for the Oracle Software Engineer role in Seattle, Washington.

Success Rate

0%
Pass Rate

Oracle's interview process for their Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive36%
Neutral23%
Negative41%

Candidates reported having mixed feelings for Oracle's Software Engineer interview process in Seattle, Washington.

Oracle Work Experiences