Four onsite rounds. In the first round I was given some workers and some jobs, and I had to implement a task tracker that assigns jobs based on each worker's capacity. It wasn't hard, and I personally think the main focus is the data model. The second round was coding: given an array and some elements along with the minimum number of times each one must appear, find the shortest contiguous window that guarantees all of those elements appear at least that many times. I used a sliding window. The third round, system design, caught me off guard. I thought it would be a design-YouTube or design-Uber type of interview, but it was actually low level design. I was asked to design a traffic control system where pedestrians can push a button and the lights change. The context is similar to a problem on LC, but it isn't testing concurrency. I never realized what the interviewer wanted until the end, when they said they expected me to design a state machine. I probably failed this round. The fourth round was a project deep dive, which was basically digging through my resume, past projects, trade-offs, and so on.
Oracle Software Engineer Interview Experience — Four Onsite Rounds, a Low-Level Design Round That Caught Me Off Guard
Onsitemedium
Published
Curated and edited by PracHub
Discussion
Loading comments…