Passed Rounds 2, 3, and HR Bloomberg New Grad NYC
Interview Experience
As the title suggests, the CS gods were on my side today. Since I posted after passing R1, I figured I’d do the same now. I haven’t fully finished the process yet (EM scheduled for next week), but I w
Full Details
As the title suggests, the CS gods were on my side today. Since I posted after passing R1, I figured I’d do the same now. I haven’t fully finished the process yet (EM scheduled for next week), but I wanted to share my experience in case it helps anyone who’s still interviewing or has their R1. I remember reading a ton of posts that really eased my nerves, so hopefully this helps someone else too. Feel free to DM me for more specific details. Round 2 (on zoom) Both interviewers were absolute legends. Super helpful and communicative throughout the entire interview. They were on the older side and gave off major “chill uncle” energy. We talked through both LC questions together, and they never really let me drown if I got stuck. This was the harder round between 2 & 3 tbh. Got asked time complexity for 1 of them. A little tricky since it was recursion but answer seemed to satisfy. The behavioral section turned into some great conversations, and they asked a lot of open-ended, conversation-inviting questions at the end. Lots of smiles and genuinely insightful discussions. I was asked to come back in 15 minutes.
Round 3 (on zoom) I didn’t think it could get better, but it did. Both interviewers were younger, high-energy, super chill, and very supportive. I only had one LC question this round and we shared a few laughs while working through it. I initially missed a small optimization but caught it quickly. Once again got asked time and space, answer was relatively straightforward. We spent the rest of the time talking about general coding best practices and asking questions. Once again, great vibes and great conversations. I was asked to come back in \~30 minutes (which turned into an hour) for HR.
Round 4 / HR (on zoom) I wasn’t too worried about this round. Mostly knew if I made it this far, I just had to be solid on my resume and behaviorals. No coding. It went smoothly and felt more like a conversation than an interview. I was asked the usual behavioral questions along with some housekeeping stuff (salary expectations, sponsorship, availability, etc.). I’m now scheduled for the EM round next week and was told to expect a resume deep dive and/or system design.
Question: I’ve read the full spectrum of EM experiences, from super chill resume discussions to brutal system design rounds. I plan to know my resume inside and out and grind system design. Any other advice? Is it common to fail the EM round? I can see the finish line, but job’s not finished (insert Kobe meme). Any advice would be appreciated, and feel free to reach out. I’d love to help however I can. Update: Got the offer!
About This Question
This is a candidate experience report from a bloomberg interview for a eng manager role (new grad level) during the phone screen round reported in 2026.
It covers the following topics: Recursion, System Design, Oop, Networking .
Difficulty rating: Easy
Topics
More Bloomberg Interview Questions
About Bloomberg Interview Reports
This question was reported by a candidate who interviewed at Bloomberg. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Bloomberg are the higher-signal extractions to take from this report.
For broader preparation context, the Bloomberg interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Bloomberg reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Bloomberg Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Bloomberg reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.