Sources checked
Bloomberg
A genuine engineering loop, coding on HackerRank over Zoom plus a decision-bearing behavioral hour where a weak reason for Bloomberg turns down strong coders.
The Bloomberg process
3 of 5 stages you can practise here
- 01Online 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.
- 02
Warm, logistics-first conversation
motivationbackground fitcommunication - 03
Brief intros, maybe one warm-up question, then straight into 1-2 DS&A problems in a shared editor
problem solvingcommunicationcomplexity analysis - 04Virtual 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.
4 rounds you can practise
Same collaborative-but-persistent cadence as the phone screen, dialed up
problem solvingcomplexity analysisedge cases & testingA design-lite coding round, characteristic of Bloomberg: you model a small system in classes and then implement the core methods
class modelingdata structure choiceimplementationA spoken, whiteboard/diagram discussion, mainly for experienced hires and often finance-data-flavored
requirementsarchitecturedata modelingConversational, sometimes woven into other rounds or given a dedicated slot
motivationownershipcollaboration - 05Decision & 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.
Common questions
- How many coding rounds does Bloomberg's software engineer loop have?
- Typically a technical phone screen (one live-coding round, occasionally two) followed by a virtual onsite of 2-3 technical rounds. For new grads the onsite is coding-heavy and often includes a Bloomberg-style object-oriented design round; senior candidates are more likely to get a system design round. Many pipelines also start with a HackerRank online assessment.
- How hard are Bloomberg's coding questions?
- Predominantly LeetCode Easy-to-Medium, with occasional Medium-Hard. Bloomberg is known for breadth of standard problems (arrays, strings, hashmaps, linked lists, trees, graph BFS/DFS) rather than exotic Hard problems, and it weighs communication, edge-case handling, and explicit time/space complexity analysis heavily.
- What are Bloomberg's signature interview problems?
- Community reports consistently associate LRU Cache, Number of Islands, and Flatten a Multilevel Doubly Linked List with Bloomberg, along with merge-intervals, top-K frequent elements, and object-oriented design prompts such as designing a deck of cards or a parking lot. Treat these as characteristic, not guaranteed for any given loop.
- Does 'why Bloomberg' actually matter in the interview?
- Yes. Genuine motivation is one of the most repeatedly reported Bloomberg traits. Candidates who cannot articulate specific interest in Bloomberg, fintech, or the Terminal are commonly filtered, so expect 'why Bloomberg' and 'what do you know about what we do' in both the recruiter screen and the behavioral round.
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.