Bloomberg · Software engineer · All levels
Behavioral / Motivation ('Why Bloomberg')
Conversational, sometimes woven into other rounds or given a dedicated slot
What they actually ask
The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.
- “Why Bloomberg specifically, and why fintech?”
- “Walk me through the project you are most proud of.”
- “Tell me about a difficult technical problem you solved and how you approached it.”
- “Describe a time you disagreed with a teammate and how you resolved it.”
- “Tell me about a time you had to learn something new quickly.”
What this round is judged on
- Motivation · genuine, specific interest in Bloomberg
- Ownership · drove past projects and decisions
- Collaboration · handles conflict and works well with others
- Learning orientation · picks up new things quickly
- Communication · clear, structured storytelling
Where this round sits
Bloomberg’s published process. Lime marks the stage this round runs.
- 01Online Assessment (HackerRank)
- 02Recruiter / HR Screen
- 03Technical Phone Screen
- 04Virtual Onsite (Final Loop)this round
- 05Decision & Team Matching
What happens in each stage›
- Online Assessment (HackerRank)
- Timed DS&A coding, typically 1-3 problems in roughly 60-90 minutes. Standard for new-grad and intern pipelines; sometimes waived for experienced or referred candidates. Whether a given candidate gets an OA vs. going straight to a phone screen varies.
- Recruiter / HR Screen
- Logistics, background, level fit, and motivation. Bloomberg recruiters probe 'why Bloomberg' early and seriously.
- Technical Phone Screen
- Usually one round (occasionally two), ~45-60 min live coding in a shared editor (HackerRank CodePair / CoderPad-style). Pure DS&A, Easy-Medium, with escalating follow-ups on complexity, edge cases, and testing.
- Virtual Onsite (Final Loop)
- Typically 2-3 technical rounds plus a behavioral/motivation component, ~45-60 min each. Composition varies by level: new grads see coding-heavy loops with a Bloomberg-style object-oriented design round and little/no system design; senior candidates are more likely to get a finance-flavored system design round.
- Decision & Team Matching
- Bloomberg has historically interviewed candidates generally and team-matched afterward (a hiring-pool model) rather than for one specific team, though some teams run direct loops. Persistence of this model into 2026 is unverified.
Sources
Built from what Bloomberg publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.
Confirms Bloomberg's two public SWE levels (Software Engineer, Senior Software Engineer) and compensation. No interview-process detail on the page.
Confirms Blind 75 / Grind 75 as the canonical DS&A prep lists that map cleanly onto Bloomberg's coding topic set (arrays, strings, hashmaps, linked lists, trees, graphs).
Official source for the company blurb and any published engineering values/how-we-hire content. Bot-blocked to automated fetches (403, or 301 to a marketing page that 403s); a human can read it.
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.
Other Bloomberg rounds
- Recruiter / HR Screen
Warm, logistics-first conversation
- Technical Phone Screen (Live Coding)
Brief intros, maybe one warm-up question, then straight into 1-2 DS&A problems in a shared editor
- Onsite Coding Round
Same collaborative-but-persistent cadence as the phone screen, dialed up
- Object-Oriented / Low-Level Design Round
A design-lite coding round, characteristic of Bloomberg: you model a small system in classes and then implement the core methods
- System Design Round (Senior)
A spoken, whiteboard/diagram discussion, mainly for experienced hires and often finance-data-flavored