2025–2026 Bloomberg New Grad Interviews: 98 Experiences (Part 2 :)

Continued from Part 1

Coverage: Timelines 09–22 of 50 detailed candidate reports. The 98-experience count applies to the complete series.

50 detailed candidate timelines, loops, and screens ~ continued

09: NYC 2026 offer after a five-round journal

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

Timeline

1. Applied in late October and received the first-round request in late November.
2. Completed round one in mid-January, then rounds two, three, and HR one week later.
3. Completed the manager round in early February and received the offer in late February.

Interview signal

The first round was a tagged variation with a substantial follow-up. Round two mixed tagged and untagged material and was the hardest technical. Round three was easier. HR was standard behavioral, and the manager round was a resume deep dive with no coding or system design. The candidate’s strongest advice was to separate thinking from typing: clarify, explain the approach, sketch pseudocode, and only then translate it into code.

10: 2026 New Grad offer with immediate superday advancement

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

Technical rounds

The phone screen asked Flatten a Multilevel Doubly Linked List plus a simple DFS graph task. VO1 used Ordered Stream and a tree/trie-like task. VO2 used Insert Delete GetRandom in O(1) plus a string problem. Interviewers announced advancement at the end of both VO rounds, and HR scheduled the next step roughly 30 minutes later.

Final rounds

HR asked ordinary behavioral questions. The engineering manager focused on the candidate’s earlier product-management experience, work style, and resume rather than a design exercise. The candidate’s timeline ran from a January 13 screen to a February 17 written offer.

11: Wordle, Word Search, to-do design, and a friendly manager round

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

Phone screen

The candidate implemented string-to-integer conversion and a Wordle-style checker.

Virtual onsite

The first technical was Word Search. The second used Binary Tree Vertical Order Traversal, then introduced 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 second design, yet the interviewer still advanced the candidate.

HR and manager

HR lasted only about 15 minutes. The manager asked about a challenging project, what the candidate would improve, how to lead an unreasonable teammate, and how to assign work. A manager no-show caused one reschedule; the offer still arrived within a week of the completed final round.

12: Three technical rounds, HR, manager, and an offer

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

Each technical round reserved about 45 minutes for coding and 15 minutes for conversation, and every interviewer asked about the same challenging project. Round one had two array/tagged questions. Round two had two more problems, including a car-related task the candidate could not later reconstruct. Round three shifted to object design: a RandomizedSet-style class, a train-station design, and a final DFS graph task.

HR asked ordinary behavioral and identity questions. The engineering manager arrived ten minutes late and used the rest of the hour for resume, career motivation, prior work, and Bloomberg’s training and team-placement process. No system design appeared. The candidate advanced after every stage and received the offer.

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

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

Round 1

Two linked-list mediums were coded, executed, complexity-checked, and dry-run. The round also included introductions, behavioral questions, a resume pass, and candidate questions.

Full loop

The next technical used one untagged string problem and one tagged tree problem. The third used graph and backtracking problems at medium-to-hard difficulty, followed by system-design questions. HR covered motivation, other offers, and logistics. The final manager round probed resume decisions, tradeoffs, scalability, reliability, and how to modernize a legacy system. The offer arrived ten days after the manager interview.

14: Correct Python syntax became the center of a hostile superday round

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

An engineering manager with more than 15 years at Bloomberg challenged whether Python’s substring-membership expression worked, then criticized the candidate’s language familiarity even though the expression itself was valid Python.

The source does not preserve the complete problem, so it cannot establish whether a missing requirement made the overall approach wrong. It does establish that interviewer behavior varied sharply: some candidates described supportive pair-programming, while this candidate left feeling mocked and expected rejection. The article treats that as an individual report, not a company-wide conclusion.

15: Frankfurt five-round offer with reconciliation design

Report date: 2026 (reply update; exact month not preserved) · Role: New Grad SWE · Location: Frankfurt · Result: Offer

The first technical mixed “Why Bloomberg?”, lessons from prior work, university-versus-company differences, edge cases, and requirement changes. The second combined a resume review with a Mutable Stock Price Top K task. Round three discussed the Frankfurt office and designed a reconciliation system. HR used STAR-style behavioral answers. The manager round went deeply into prior work, team structure, tools, critical feedback, and how the candidate would deliver feedback to someone else. The process ended in an offer call covering salary and relocation.

16: Full loop with three coding tasks in one VO

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

The phone screen used Find First and Last Position in a Sorted Array, then changed append-only updates into arbitrary insertion. VO1 combined the constant-time add/remove/random data structure with a nested-parentheses depth task.

VO2 began with a grid-defense prompt: choose a tower location that covers the most houses within Manhattan distance k. It then moved to shortest path with up to k obstacle eliminations and, because the candidate finished quickly, an extra AtCoder-style adventure problem they did not solve. The candidate still advanced. HR and the manager round were behavioral/resume conversations. The offer call arrived two days after the manager round.

17: Easy-to-medium round, hard round, HR, and a rejection before EM

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

Round two began with resume questions and an easy/medium task whose obvious solution could be simplified. The candidate found the optimal path after a nudge, coded it, then handled two increasingly complex follow-ups. They missed one edge case and made a small Boolean-return bug.

Round three introduced a hard problem. The interviewer skipped coding after hearing the approach, then added two follow-ups and pushed toward a niche optimal algorithm. HR happened 30 minutes later and covered projects and logistics. Despite community assumptions that reaching HR meant passage, the candidate received the rejection and never reached the final manager round.

18: Frankfurt rejection after a progressive path problem

Report date: Late 2025 (exact month not preserved) · Role: 2026 New Grad SWE · Location: Frankfurt · Result: Rejected

Round 1

The hour opened with introductions, “Why Bloomberg?”, and a proud project. The coding task was an easier Merge Intervals variation that had to compile and run.

Round 2

Two interviewers began with the same behavioral structure, then progressively added requirements until a path-finding problem became substantially harder. The candidate used DFS, understood the optimization after hints, but did not have time to implement it. The rejection arrived within an hour.

19: One virtual technical plus two campus technicals, then an offer

Report date: Late 2025 (exact month not preserved) · Role: Early Career/New Grad SWE · *Location: New York City · Result: Offer

The candidate completed one virtual technical and two technical interviews on campus. Each technical used two LeetCode-style problems; the candidate described them as manageable and reported no extra behavioral block in the first round.

The final stage consisted of recruiter/HR and an engineering-manager conversation. Another candidate described manager questions about technology choices in a past internship and handling competing priorities. The original candidate later confirmed receiving the offer. The exact coding problems were not shared.

20: Kafka in the manager round

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

Technical path

The phone screen included a social-graph partner task and Count Vowel Substrings. VO1 modeled television-episode churn and a 70% retention threshold. VO2 designed an equity-price tracker with constant-time latest, maximum, and average queries, followed by a verbal streaming-median extension.

Manager round

The manager asked for a Kafka / distributed commit log design covering producers, consumers, topics, partitions, brokers, retries, replication, acknowledgements, durability, and consistency. An ordering follow-up asked how to recover when producers intended to use different brokers but network behavior routed messages incorrectly. The candidate proposed a Raft-elected leader to establish order. They felt this answer was weak and still received an offer two days later.

21: New York VO rejection tied to communication, not question difficulty

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

The candidate entered the process through a conference contact after a referral. VO1 had two interviewers and began with a summer-internship project. The candidate was nervous, explained it unclearly, and had to start again.

Coding covered a horse-racing puzzle family and an odd/even linked-list transformation. Both felt easy-to-medium. During the final feedback period, the interviewer directly said the experience explanation had been confusing and that communication should improve before coding. The rejection followed three days later. This report is a useful reminder that a technically manageable round can still be lost before the first line of code.

22: A client project carried the entire manager interview

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

The manager selected a full-stack project the candidate had shipped for a real client. The project replaced an Excel-and-messaging workflow with a React frontend, API, and PostgreSQL database.

The discussion covered discovery, challenging user assumptions, limiting the MVP, handling a late request for automatic PDF generation and email, writing meeting summaries, validating requirements with prototypes, and documenting the system well enough for a replacement engineer. The candidate had owned discovery, scope, tradeoffs, delivery, and maintenance. The manager explicitly praised the product thinking. Feedback and an offer arrived two days later.

Continued in Part 3