Bloomberg interview notes, page 6 of 14

“My first instinct was to just store everything in one big map and figure it out later, which was the wrong move.” The rest of the author's notes on Software Engineer interview at Bloomberg, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I had an answer ready but rambled a bit trying to make it sound impressive.” The rest of the author's notes on Software Engineer interview at Bloomberg, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Started with the greedy approach since it's the obvious move: just keep picking the highest-probability next token until you hit an end-of-sentence marker.” The rest of the author's notes on Software Engineer interview at Bloomberg, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The base version isn't bad once you realize the root is just the node that never appears as anyone's child.” The rest of the author's notes on Software Engineer interview at Bloomberg, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew round-robin scheduling as a concept but generating ALL valid schedules via backtracking is a different beast.” The rest of the author's notes on Software Engineer interview at Bloomberg, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The base case is pretty textbook, two pointers moving inward until you find a mismatch, then you try skipping one side or the other and see if the remainder is a palindrome.” The rest of the author's notes on Software Engineer interview at Bloomberg, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The O(n) constraint is what makes it interesting.” The rest of the author's notes on Software Engineer interview at Bloomberg, 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, you've probably seen it a hundred times.” The rest of the author's notes on Software Engineer interview at Bloomberg, 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 pure backtracking and it worked on small inputs, but I could see where it was going with overlapping subproblems.” The rest of the author's notes on Software Engineer interview at Bloomberg, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is the core prompt and it sprawls in every direction fast.” The rest of the author's notes on Software Engineer interview at Bloomberg, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.