RepostedBloomberg LP logo

Bloomberg LP · OA → Phone screen → Onsite

In process

Bloomberg New Grad SWE Offer Loops: 14 Experiences (Part 2 of 5)

Software engineer · New GradBachelor's degreeSep 2026
Shared by

Bloomberg new grad SWE interviews, Nov 2025 to early 2026: ten offers in 14 loops, Insert Delete GetRandom three times and Kafka in one manager round.

At a glance

  • Process: a screen, two or three technical rounds with about 45 minutes of coding each (often two problems), HR, then an engineering manager (09, 10, 12, 13, 15). Offers came two days to ten days after the manager round (13, 16, 20, 22).
  • Asked recently: graph or grid search in 7 of 14 reports, data-structure or class design in 5, string tasks in 5. Insert Delete GetRandom O(1) came up three times (10, 12, 16).
  • Difficulty: one round was usually harder than the rest (09, 17); hard rounds kept adding requirements until time ran out (17, 18).
  • Practise first: Insert Delete GetRandom O(1), Word Search, Flatten a Multilevel Doubly Linked List and Mutable Stock Price Top K.

Coverage: New grad SWE and SDE, mostly the 2026 cycle: 14 reports (09–22), November 2025 to early 2026, screen through offer. New York City and Frankfurt are named.

In this series

  • Part 1: the series overview and timelines 01–08, March to May 2026: stream design, Count Ships and linked lists.
  • Part 2 (current): timelines 09–22, November 2025 to early 2026: New York and Frankfurt offers, Kafka in a manager round, Word Search and Wordle.
  • Part 3: timelines 23–36, September to November 2025: Invalid Transactions, a fuel BFS follow-up and a top-news design round.
  • Part 4: short reports 01–16 (November 2025 to August 2026) and timelines 37–50 (October 2024 to 2025): a streaming palindrome, Candy Crush and London offers.
  • Part 5: short reports 17–48, October 2024 to November 2025: Number of Islands, multilevel-list flattening and Blackjack design.

What came up

Ten of these 14 candidates got offers. Loops mixed classic LeetCode problems with Bloomberg-flavored design: stock tracking, episode churn, a to-do class, Kafka.

Topic Reports Last seen
Resume or project deep dive 10 of 14 Feb 2026
Graphs, grids and DFS or BFS 7 of 14 Feb 2026
Data-structure or class design 5 of 14 Feb 2026
Strings and parsing 5 of 14 Feb 2026
Linked lists 3 of 14 Feb 2026
Trees 3 of 14 Feb 2026
System design 3 of 14 2026
Heaps, top-K and streams 2 of 14 2026

All dates are report months. A candidate can appear in more than one row.

Questions we found

Arrays, strings and stateful structures

Question Reports Last seen
Insert Delete GetRandom O(1) (LeetCode 380) 3 Feb 2026
Design an Ordered Stream 1 Feb 2026
String to Integer (atoi) 1 Feb 2026
Wordle checker 1 Feb 2026
Mutable Stock Price Top K 1 2026
First and Last Position, with insertions 1 Dec 2025
Maximum Nesting Depth of Parentheses 1 Dec 2025
Merge Intervals (variation) 1 Late 2025
Count Vowel Substrings 1 Nov 2025
Episode churn and a 70% retention threshold 1 Nov 2025
Equity prices: latest, max and average in O(1) 1 Nov 2025
Find Median from Data Stream (verbal) 1 Nov 2025
Horse-racing puzzle 1 Nov 2025

Graphs, grids, trees and linked lists

Question Reports Last seen
Flatten a Multilevel Doubly Linked List 1 Feb 2026
Word Search (LeetCode 79) 1 Feb 2026
Binary Tree Vertical Order Traversal 1 Feb 2026
Tower placement covering the most houses 1 Dec 2025
Shortest Path with Obstacles Elimination (LeetCode 1293) 1 Dec 2025
Social-graph partner task 1 Nov 2025
Odd Even Linked List 1 Nov 2025

System and class design

Question Reports Last seen
To-do list class with a completed-ID check 1 Feb 2026
Train-station design 1 Feb 2026
Modernize a legacy system 1 Jan 2026
Reconciliation system (Frankfurt) 1 2026
Kafka / distributed commit log 1 Nov 2025

Behavioral (BQ)

Question Reports Last seen
Tell me about a challenging project and what you would improve 2 Feb 2026
Why Bloomberg? 2 2026
How would you lead an unreasonable teammate and assign work? 1 Feb 2026
How do you take and give critical feedback? 1 2026
How did university differ from working at a company? 1 2026

14 detailed candidate timelines, loops, and screens

09: A New York offer, logged round by round

Report date: February 2026 · Role: New Grad SWE · Location: New York City · Result: Offer

  1. Timeline: applied late October, first-round request late November, round one mid-January, rounds two, three and HR a week later, manager early February, offer late February.
  2. Round 1: a tagged variation with a substantial follow-up.
  3. Round 2: tagged and untagged material, the hardest technical. Round 3: easier.
  4. HR was standard behavioral. The manager did a resume deep dive with no coding or system design.

10: Advancement announced at the end of each VO

Report date: February 2026 · Role: New Grad SWE · Result: Offer

  1. Phone screen: Flatten a Multilevel Doubly Linked List plus a simple DFS graph task.
  2. VO1: Design an Ordered Stream and a tree or trie-like task.
  3. VO2: Insert Delete GetRandom O(1) plus a string problem. Both VO interviewers announced advancement on the spot; HR followed up about 30 minutes later.
  4. HR asked ordinary behavioral questions. The engineering manager focused on the candidate's earlier product-management work, work style and resume, with no design exercise.
  5. Screen on January 13, written offer on February 17.

11: Wordle, Word Search and a to-do class

Report date: February 2026 · Role: New Grad SWE · Result: Offer

  1. Phone screen: String to Integer (atoi) and a Wordle-style checker.
  2. VO1: Word Search.
  3. VO2: Binary Tree Vertical Order Traversal, then a to-do list class with add, delete, single lookup, all-items lookup and a supplied completed-ID check. There was only time to explain the design, and the candidate still advanced.
  4. HR took about 15 minutes. The manager asked about a challenging project, what they would improve, how to lead an unreasonable teammate and how to assign work. A manager no-show forced one reschedule; the offer came within a week of the final round.

12: The same challenging project in every round

Report date: February 2026 · Role: New Grad SDE · Result: Offer

  1. Each technical round gave about 45 minutes to coding and 15 to conversation; every interviewer asked about the same challenging project.
  2. Round 1: two array or tagged questions. Round 2: two more problems, including a car-related task the candidate could not later recall.
  3. Round 3: object design: a RandomizedSet-style class, a train-station design, and a final DFS graph task.
  4. HR asked ordinary behavioral and background questions. The manager, ten minutes late, covered resume, motivation, prior work and Bloomberg's training and team placement. No system design. Offer.

13: Six problems, design follow-ups, then an offer

Report date: January 2026 · Role: New Grad SDE · Location: New York City · Result: Offer

  1. Round 1: two linked-list mediums, coded, run, complexity-checked and dry-run, plus introductions, behavioral and resume questions.
  2. Round 2: one untagged string problem and one tagged tree problem.
  3. Round 3: medium-to-hard graph and backtracking problems, then system-design questions.
  4. HR: motivation, other offers and logistics. Manager: resume decisions, tradeoffs, scalability, reliability, and how to modernize a legacy system. The offer came ten days later.

14: A valid line of Python, challenged in a superday round

Report date: January 2026 · Role: New Grad SWE · Stage: Third (superday) technical

  1. An engineering manager with 15+ years at Bloomberg doubted that Python's substring-membership expression worked, then criticized the candidate's language knowledge, though the expression is valid Python.
  2. The full problem was not shared. The candidate left feeling mocked and expected a rejection.

15: A Frankfurt offer with a reconciliation design round

Report date: 2026 (month not given) · Role: New Grad SWE · Location: Frankfurt · Result: Offer

  1. Technical 1: Why Bloomberg, lessons from prior work, how university differs from a company, then coding with edge cases and changing requirements.
  2. Technical 2: a resume review and a Mutable Stock Price Top K task.
  3. Round 3: the Frankfurt office, then a reconciliation-system design.
  4. HR: STAR-style behavioral answers. Manager: prior work, team structure, tools, critical feedback received, and how the candidate would give it.
  5. The offer call covered salary and relocation.

16: Three coding tasks in one VO

Report date: December 2025 · Role: New Grad SWE · Result: Offer

  1. Phone screen: First and Last Position in a Sorted Array, then append-only updates became arbitrary insertions.
  2. VO1: the constant-time add, remove and random structure and a nested-parentheses depth task.
  3. VO2: a grid-defense prompt (a tower spot covering the most houses within Manhattan distance k), then shortest path with up to k obstacle eliminations. Finishing early earned an extra contest-style adventure problem they did not solve. They still advanced.
  4. HR and the manager were behavioral and resume talks. The offer call came two days after the manager round.

17: Rejected after HR, before the manager

Report date: December 2025 · Role: 2026 New Grad SWE · Result: Rejected

  1. Round 2: resume questions, then an easy-to-medium task whose obvious answer could be simplified. After a nudge they coded the optimal path and two harder follow-ups, but missed one edge case and had a small Boolean-return bug.
  2. Round 3: a hard problem. The interviewer skipped coding after hearing the approach, added two follow-ups and pushed toward a niche optimal algorithm.
  3. HR came 30 minutes later (projects and logistics). The rejection followed; there was no manager round.

18: Frankfurt: a path problem that kept growing

Report date: Late 2025 · Role: 2026 New Grad SWE · Location: Frankfurt · Result: Rejected

  1. Round 1: introductions, Why Bloomberg and a proud project, then an easier Merge Intervals variation that had to compile and run.
  2. Round 2: two interviewers, the same behavioral opening, then a path-finding problem with requirements added step by step. The candidate used DFS and understood the optimization after hints, but had no time to code it. The rejection came within an hour.

19: One virtual and two campus technicals, then an offer

Report date: Late 2025 · Role: Early career / New Grad SWE · Location: New York City · Result: Offer

  1. One virtual technical and two on-campus technicals, each with two manageable LeetCode-style problems and no extra behavioral block in round one. No prompts were shared.
  2. The final stage was recruiter/HR plus an engineering manager. Another candidate replying said their manager asked about tech choices in a past internship and competing priorities.

20: Kafka in the manager round, and still an offer

Report date: November 2025 · Role: 2026 New Grad SDE · Result: Offer

  1. Phone screen: a social-graph partner task and Count Vowel Substrings.
  2. VO1: model TV-episode churn and a 70% retention threshold.
  3. VO2: an equity-price tracker with constant-time latest, maximum and average, then a verbal streaming-median extension.
  4. Manager: a Kafka / distributed commit log design: producers, consumers, topics, partitions, brokers, retries, replication, acknowledgements, durability and consistency. An ordering follow-up asked how to recover when the network routed messages to the wrong brokers. The candidate proposed a Raft-elected leader, felt the answer was weak, and got an offer two days later.

21: An easy round lost on the project explanation

Report date: November 2025 · Role: 2026 New Grad SWE · Location: New York City · Result: Rejected

  1. A referral and a conference contact led to VO1 with two interviewers. It opened with a summer-internship project; the nervous candidate explained it unclearly and had to restart.
  2. Coding: a horse-racing puzzle and an odd/even linked-list transformation, both easy to medium.
  3. In the feedback minutes, the interviewer said the project explanation had been confusing. The rejection came three days later.

22: One client project carried the whole manager round

Report date: November 2025 · Role: 2026 New Grad SWE · Result: Offer

  1. The manager picked a full-stack project built for a real client: React, an API and PostgreSQL replacing an Excel-and-messaging workflow.
  2. Topics: discovery, challenging user assumptions, limiting the MVP, a late request for automatic PDF and email, meeting summaries, prototypes to validate requirements, and docs for a successor. The manager praised the product thinking.
  3. Feedback and an offer arrived two days later.

Patterns across the reports

  1. Insert Delete GetRandom keeps returning. Three candidates got it or a RandomizedSet-style class in a live round (10, 12, 16), all of them ending with offers.
  2. Manager rounds were mostly about the resume. Six centered on projects, motivation or work style (09, 10, 11, 12, 16, 22); others went into legacy modernization (13), feedback (15) or Kafka (20).

Common questions

Does the Bloomberg new grad manager round include system design?

Usually not: six were resume or motivation talks (09, 10, 11, 12, 16, 22). One asked for Kafka design (20), one about modernizing a legacy system (13).

How many coding questions are in a Bloomberg new grad technical round?

Usually two in about 45 minutes (12, 13, 19); one VO had three (16).

How fast does Bloomberg give an offer after the final round?

Two days in 16, 20 and 22, within a week in 11, and ten days in 13.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.