Coding: this was an OO design problem I hadn't seen anywhere on the forum before, implementing two functions. One function is addTask(taskId, priority, timestamp) — the same task can be added multiple times at different timestamps. The other is executeTask(), which is the tricky part — you first sort by priority, and if a task has already been executed, you skip it.
System design: job scheduler. There are already write-ups for this design floating around out there, but based on the feedback I got afterward, what the interviewer actually wanted was for you to say something different from what's already out there. I prepared using Hello Interview, and the interviewer felt there was nothing that stood out. Everyone should prepare well and look at more resources.
BQ: the project I'm most proud of, handling conflict, the biggest difficulty I've run into, what advice I'd give my current team if I had to give one, why I want to switch jobs.
The reason I failed: I finished writing the coding part but didn't run the tests, and during the conversation the interviewer seemed unsatisfied with my approach several times. It felt like you're expected to come up with the optimal answer quickly and independently.
The system design part was pretty standard, nothing that stood out.
My personal feeling is that the current interview bar basically expects you to be "perfect".
Wishing everyone a perfect performance!
Discussion
Loading comments…