Bloomberg interview notes, page 5 of 14

“This one took me a minute to even parse.” 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 went straight for a hashmap keyed by id, which was the right call for O(1) lookups on get and delete.” 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.

“Pretty standard stuff if you've done any interval problems before.” 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 got the basic structure down pretty quickly, nodes with a map of character to child node, a flag for end-of-word.” 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 interface looked clean so I jumped straight to a flat vector of subscriptions and immediately realized that's a disaster at 10^5 subs with tens of thousands of trades per second.” 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.

“I started with clarifying questions about user segments and SLA commitments, which felt right, but then I kind of rambled when it came to the actual decision criteria for new OS support.” The rest of the author's notes on Product Manager interview at Bloomberg, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The naive approach feels obvious until you start thinking about what happens when multiple characters collide on the same count.” 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 plain BFS and I coded like half of it before realizing revisiting cells is actually valid here because your fuel level changes after hitting a gas station.” 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 started with the brute force and talked through it fine: iterate every cell, count houses within distance k, track the max.” The rest of the author's notes on Software Engineer interview at Bloomberg, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was brute force O(n^2) and I coded it up fine, but then they asked about scale.” 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.