Oracle interview notes, page 5 of 9

“The k == 0 case is what gets people.” The rest of the author's notes on Software Engineer interview at Oracle, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic problem, probably should've nailed it without hesitation but I spent a beat overthinking whether they wanted the sum formula or a sort-based approach.” The rest of the author's notes on Software Engineer interview at Oracle, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with the real-time hook layer because it felt like the most interesting part, kernel-level interception via fanotify or a minifilter driver feeding into a user-space daemon.” The rest of the author's notes on Software Engineer interview at Oracle, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one took me a while to even see the path forward.” The rest of the author's notes on Software Engineer interview at Oracle, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with a plain hash map and felt pretty confident until they asked about list operations.” The rest of the author's notes on Software Engineer interview at Oracle, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic topological sort but I kept second-guessing whether to go BFS (Kahn's) or DFS with coloring.” The rest of the author's notes on Software Engineer interview at Oracle, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This was the whole interview, not just one question.” The rest of the author's notes on Software Engineer interview at Oracle, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Blanked for a second trying to pick the right story.” The rest of the author's notes on Software Engineer interview at Oracle, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew it was a hashmap plus doubly linked list but fumbled explaining why the doubly linked list specifically.” The rest of the author's notes on Software Engineer interview at Oracle, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to just loop through and apply everything naively, which is obviously wrong for the optimization part.” The rest of the author's notes on Software Engineer interview at Oracle, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.