Bloomberg Lp Software Engineer Interview Guide

Candidates who interviewed for Bloomberg's Software Engineer role describe a loop dominated by LeetCode-style coding. The follow-up questions that extend the original problem do much of the filtering. Reported problems include:

• tree and BFS questions, including binary tree vertical traversal and validating a binary search tree;
• an island question and meeting rooms;
• linked-list reversal and a sliding window problem;
• a reworded Two City Scheduling;
• finding the fastest-changing stock ticker.

Several candidates describe the difficulty as medium to hard, mainly because of time pressure and having to defend tradeoffs aloud. One interviewer pressed on the difference between ordered and unordered hash maps, so know how core data structures work, not just how to use them.

Expect resume and project discussion as well. Candidates were asked how they tested a full-stack project, about a conflict with a coworker, about a technical challenge they handled, and about their weakest skill. A "Why Bloomberg?" question also comes up, along with a comparison of working at a startup versus a big company.

The shape of the loop varies. Some candidates report a recruiter or HackerRank-style screen, then a superday of technical interviews, an HR conversation, and an engineering manager round. Another candidate had only two coding interviews before being rejected. A few candidates mention design-style prompts: a URL shortener, a single-user stock portfolio, a news alerting system, and data consistency during a canary deployment between new and legacy systems.

Practice writing correct code quickly, walking through it by hand, and explaining why you chose one approach over another. At least one interviewer checked the logic by reading the code rather than running it. Every account in this set ended without an offer, so treat the specifics as individual experiences rather than a fixed format.