real interview stories, told over a cup of tea ♡
Bloomberg Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
13 results
- Two Passed Screens, Filled Openings, and a Virtual OnsiteBloomberg · Software Engineer · Onsite · Aug 2026Rejected
At Bloomberg, you can move forward with at most two teams at the same time, and each team's phone screen is independent. Basically, one job posting corresponds to one opening, and those openings fill pretty quickly. I passed both phone screens, but both openings had been filled. The recruiter helped forward my resume to a sister team of one of those teams that was hiring, so I didn't need another…
- Detecting Fraudulent Transactions Within 60 MinutesBloomberg · Software Engineer · Technical Screen · May 2026
Coding Interview | Fraud Transactions I recently interviewed with a coding problem about fraudulent transactions, so I am recording it here. The problem roughly gave me a transaction list: I had to find the fraudulent transactions under two rules: A single transaction with an amount greater than $2,000 is immediately considered fraudulent. Transactions from the same account within 60 minutes are…
- Top K Frequent Elements Phone ScreenBloomberg · Software Engineer · Technical Screen · Mar 2026
The first round was a standard phone technical screen — coding only, no behavioral questions. The difficulty is generally on the higher end of LeetCode medium, and the focus is on whether your data structure choice is reasonable and whether your code is clean. The question I got was to design a data structure that supports insert, delete, and returning the current Top K most frequent elements. Th…
- Simplified Grep, Friend-Request Math, and a BQ RoundBloomberg · Software Engineer · HR Screen · Dec 2025
Round 1: implement a simplified version of grep — find lines in a file containing a specific string, and also account for extensibility to flags. I just honestly clarified requirements first, then wrote the parsing plus the string matching. The focus of this problem isn't really the algorithm, it's whether you can write clean, extensible code. Round 2: given an array of ages, compute the total nu…
- Final Round Focused Entirely on My Solo Full-Stack ProjectBloomberg · Software Engineer · Onsite · Nov 2025Offer
Hey, sharing my interview experience from Bloomberg's final round today. We did about 2 minutes of small talk to open, then the HM went straight in: "I'm particularly interested in this full stack project you did for a real client. Let's focus mostly on that, I'd like to understand how you work." As soon as I heard that I knew this round wasn't about how strong my technical skills were, it was ab…
- A GHC Resume Pickup Ends in a Failed First Virtual OnsiteBloomberg · Software Engineer · New Grad · Onsite · Oct 2025Rejected
Application timeline: 9/26/2025: Found a referral and applied for the 2026 Software Engineer - New York role. The position isn't open to the public — you can only apply through a referral. 11/2025: Went to GHC'25, talked to a Bloomberg engineer, dropped off a paper resume, and saw them mark it up. 11/13/2025: Unexpectedly got the schedule-VO (virtual onsite) email — must have been picked up throu…
- Phone Screen, Super Day, and EM Round to OfferBloomberg · Software Engineer · Onsite · Oct 2025Offer
I've been reading everyone's interview reports here on the forum, so now that I've got an offer, I wanted to give back with my own. 11.12 — Phone Screen It was a question from a coding-practice site — I don't remember the specifics. Follow-up: if you keep inserting numbers that are bigger than the last one at the end, how do you update it? And what if you insert random numbers regardless of size,…
- Rejected After a Van Eck Sequence QuestionBloomberg · Software Engineer · New Grad · Onsite · Oct 2025Rejected
Painful memory from an interview I did last year, around September-October. I was in a funk for a month after it. Bloomberg's bar is basically two medium-to-hard questions, and you're expected to get the optimal solution. It was a virtual interview, and the interviewer showed up 10 minutes late. I sat in the meeting watching her keep logging in and out, and when she finally turned her camera on,…
- SQL String Ops and a 20-Minute OOD ScreenBloomberg · Data Engineer · Senior+ · Technical Screen · Sep 2025
The role was Senior Software Engineer - Data Engineering. I couldn't really find much interview experience for this role online, so let me contribute one here. The interviewer was a woman, not very enthusiastic. 40 minutes, 2 questions — the first was SQL, the second felt more like OOD. The first SQL question wasn't too hard logically, the hard part was that it tested string operations. I roughly…
- Three Onsite Rounds in One DayBloomberg · Software Engineer · Onsite · Sep 2025In progress
This week's onsite report — all three rounds happened on the same day, and I probably failed. In the third round, the manager didn't ask me anything at all, he just told me straight up to ask him any questions I had. I stayed calm and asked a few things, it took about half an hour, then he said I could ask one last question and that was it. Round 1: coding Round 2: SD, with the team lead Round 3:…
- Two Rough Phone Screens and a Cryptic Tree PuzzleBloomberg · Software Engineer · Technical Screen · Sep 2025No response
The interview experience itself was actually pretty good in one sense — just spray and pray, blindly mass-applying with your eyes closed, and there's a decent chance you'll land some phone screens. I landed four HR calls total: one slot already got filled, another is still waiting to be scheduled, so right now I've actually done two phone screens. But honestly, the experience itself was not great…
- Efficient Process, Rejected the Next DayBloomberg · Product Manager · Technical Screen · Jul 2025Rejected
Fresh rejection from Bloomberg. A recruiter reached out on LinkedIn. They quickly scheduled the first round, an HR sync, about 30 minutes. They asked about my general work experience, whether I owned the roadmap, whether I had experience launching products globally, how I worked with cross-functional teams, and what the product I owned was like. They walked me through the overall interview proces…
- Recruiter Promised Easy-Medium, Got String-Heavy SQL and Rushed OOD CodingBloomberg · Senior Software Engineer - Data Engineering · Senior+ · Technical Screen · Jul 2025
I couldn't find much interview experience for this specific role online, so I'm contributing mine here. The role was Senior Software Engineer - Data Engineering. The interviewer wasn't very enthusiastic. 40 minutes, two questions — the first was SQL, the second felt more like an OOD (object-oriented design) question. The logic in the first SQL question wasn't actually that hard — what was hard wa…
