Bloomberg Software Engineer mock interview

Finance-tech hybrid. 3-5 stages, 4-7 weeks. Code Review Round (Bloomberg-specific) reviews 200+ lines as if it were a PR. Coding 3.1/5 difficulty (closer to LC Medium than Hard). NYC SWE entry $213K TC.

  • ~22 days
    Avg hire timeline
  • 4-7 weeks
    Process duration
  • 3.1/5
    Coding difficulty
  • Free
    First mock

Why Bloomberg's loop is structurally different from FAANG

Per Glassdoor (n=503), Prepfully Bloomberg SWE guide, Akash Kumar's Medium 2024 candidate report, Bloomberg's Tech blog, and aggregated candidate accounts, Bloomberg's loop has a distinctive Code Review Round — review ~200+ lines of existing code as if it were a PR. This is unusual at FAANG-scale companies and reflects Bloomberg's pride in legacy infrastructure + craft culture.

Three signals matter most for SWE screening: (1) OOP design depth — Bloomberg emphasizes class hierarchies, encapsulation, composition more than typical FAANG; (2) 'Why Bloomberg' authenticity — most-cited rejection reason is generic motivation; reference specific Bloomberg products (Terminal subsystems, BLP API), engineering blog, OSS contributions; (3) trade-off articulation — solving the problem isn't enough, interviewers probe WHY. Information-dense responses score higher than concise-but-mute.

Compensation per Levels.fyi: NYC SWE entry ~$213K TC, Senior NYC ~$305K, US-wide median $275K. Materially below FAANG-NYC senior bands but with strong base + cash bonus structure (no public stock, different from FAANG RSU). Bloomberg's culture explicitly values pride in legacy systems and customer-empathy framing (Terminal users are traders/PMs, not engineers).

What the loop looks like

Round-by-round

  1. 01

    Recruiter screen

    Pre-onsite
    30-45 min

    Background, motivation, location preference. 'Why Bloomberg specifically?' is filtered explicitly here — most-cited rejection reason per Glassdoor candidate reports.

  2. 02

    HackerRank OA + Phone screen

    Pre-onsite
    45-60 min each

    HackerRank OA (typically 2 coding questions in 45 min, LC Easy + Medium for new grads) + 1-2 technical phone via HackerRank CodePair + Zoom.

  3. 03

    Superday — Coding × 1-2

    Onsite
    60 min each

    DSA: arrays/strings/hash tables, BFS/DFS on trees and graphs, DP. Frequently reported: binary tree vertical traversal, longest substring without repeating characters, LRU cache.

  4. 04

    Superday — Code Review Round

    Onsite
    60 min

    BLOOMBERG-SPECIFIC. Review ~200+ lines of existing code as if it were a PR — flag bugs, comment on maintainability, suggest improvements. Not common at FAANG.

  5. 05

    Superday — System Design (mid/senior)

    Onsite
    60 min

    Real-time, low-latency financial systems. URL shortener, market-data feeds, real-time messaging. Throughput, latency, consistency frequently probed.

  6. 06

    Engineering Manager + Final

    Onsite
    30-45 min each

    EM round on past technical decisions and engineering instincts (NOT finance trivia per recent reports). Final HR round on fit + comp.

Question bank

Real interview questions reported by candidates

  • Code review

    "Code Review Round (Bloomberg-specific): given ~200 lines of existing code, review as if it were a PR. Flag bugs, comment on maintainability, suggest improvements. Walk through reasoning out loud."

    Source · prepfully.com Bloomberg SWE guide, glassdoor Bloomberg SWE interviews
  • Coding

    "Coding: implement LRU cache. Discuss eviction policy, capacity, get/put complexity. Variant: LFU cache."

    Source · glassdoor Bloomberg SWE, akash-kumar916.medium.com Bloomberg new-grad 2024
  • Coding

    "Coding: binary tree vertical order traversal. Then variant with column-by-column ordering. Edge cases: skewed trees, empty trees."

    Source · glassdoor Bloomberg SWE interviews
  • OOP design

    "OOP design (Bloomberg emphasis): design a class hierarchy for [Bloomberg Terminal subsystem]. Discuss encapsulation, inheritance, composition trade-offs."

    Source · prepfully.com Bloomberg SWE, linkjob.ai Bloomberg new-grad 2026
  • System design

    "System design: real-time market-data feed. Cover throughput (millions of price updates/sec), low-latency delivery (sub-millisecond), client subscription management, fault tolerance."

    Source · prepfully.com Bloomberg SWE guide
  • Behavioral

    "Why Bloomberg specifically (vs FAANG, vs banks)? Reference specific Bloomberg products (Terminal, BNL data, Reference Data Services) — generic 'I want finance tech' fails."

    Source · glassdoor Bloomberg, prepfully.com Bloomberg guide (top-cited rejection)
  • Behavioral

    "Tell me about a time you maintained legacy code. Bloomberg culture values pride in existing systems — willingness to maintain matters."

    Source · bloomberg.com/company/values/tech-at-bloomberg
  • Behavioral

    "Behavioral: customer-empathy framing. Bloomberg Terminal users are traders/PMs, not engineers. How would you handle a user complaint about latency?"

    Source · bloomberg.com customer-centric design
Common signals to fix

What gets you rejected at this level

  • Weak 'Why Bloomberg' answer

    Per prepfully.com + Glassdoor + Blind: most-cited rejection reason. 'Didn't seem to research the firm' framing. Reference specific Bloomberg products (Terminal subsystems, BLP API), engineering blog posts, or open-source contributions (Bloomberg has active OSS in tech.bloomberg.com).

  • Arrogance — suggesting systems 'need rewriting'

    Bloomberg pride in legacy infrastructure is real. Candidates who suggest systems 'need to be rewritten' or critique existing architecture without understanding the trade-offs land badly. Show curiosity about why systems are built the way they are.

  • Cannot take hints / feedback mid-interview

    Bloomberg interviewers actively give hints when you're stuck. Candidates who push past hints or ignore feedback flag missing collaborative ability. Listen, integrate, articulate updated approach.

  • Poor articulation of trade-offs

    Solving the problem isn't enough — interviewers probe whether you understand WHY. 'I'd use a hash map' = insufficient. 'I'd use a hash map because of O(1) lookup at the cost of memory; trade-off vs sorted array depends on read/write ratio' = passes.

  • Low information density

    Interviewers report being unable to 'extract' enough signal from quiet candidates. Talk through approach, narrate decisions, reflect on alternatives. Information-dense responses score higher than concise-but-mute.

How Applr's AI mock interview tracks Bloomberg's rubric

Applr's Bloomberg mock simulates the Code Review Round format — present existing code with subtle bugs, score on bug-flagging accuracy + maintainability comments + improvement suggestions. OOP design rounds prompt class hierarchy specificity matching Bloomberg's interview emphasis.

Behavioral rounds prompt 'Why Bloomberg' specifically — generic motivation gets flagged with rewrites referencing concrete Bloomberg products and engineering blog content. Trade-off articulation is graded explicitly; concise-but-mute coding answers get rewrites that surface decision reasoning.

Adjacent loops

Related practice

FAQ

What's the Code Review Round really like?

Per prepfully.com + Akash Kumar's Medium 2024 candidate report: you're given ~200+ lines of existing code (sometimes intentionally buggy) and asked to review it as if it were a PR. Flag bugs, comment on maintainability, suggest improvements. Walk through your reasoning out loud. This is distinctive to Bloomberg — not common at FAANG. Practice code review on open-source PRs before the loop.

How does Bloomberg comp compare to FAANG?

Per Levels.fyi: NYC SWE entry total comp ~$213K (range $186K-$246K). Senior SWE NYC ~$305K (range $252K-$360K). US-wide SWE median $275K. Materially BELOW FAANG-NYC senior bands (Meta E5/Google L5 commonly $400K+). Bloomberg pays strong base + cash bonus, NO public stock — different structure than FAANG RSU. Trade-off: Bloomberg known for stability, work-life balance, low layoff history.

Is the EM round really about finance trivia?

NO per recent (2024-2026) candidate reports. The 'Engineering Manager round with finance-domain questions' reputation is partially overstated. Recent reports describe EM round as more about engineering judgment than finance trivia — past technical decisions, trade-offs you've made, how you'd debug complex issues. Light finance context (terminal user awareness, market hours) helps but deep finance knowledge isn't required.

Does Bloomberg have target schools?

Active campus recruiting at MIT, Stanford, CMU, UC Berkeley, Columbia, NYU, UPenn, Cornell, University of Michigan. School distribution is broader than pure-FAANG/HFT firms but core targets remain T20 CS programs. Bloomberg also runs Engineering Accelerator (Black/Latinx students), Bloomberg Launch, First Year Insights programs — accelerator graduates skip the phone screen, providing significant advantage.

Does Bloomberg sponsor visas?

Yes for SWE roles in NYC HQ + various global locations (London, San Francisco, Princeton, etc.). Strong sponsor with reputation for clean visa coordination. International students with US/UK work eligibility have a clear path. Bloomberg's NYC presence is the largest hub for SWE hiring.

How long should the loop take?

Per Glassdoor aggregate (n=503): average 22 days from first contact to decision. Onsite-to-decision often longer. Total 4-7 weeks typical, longer for senior roles. The Code Review Round and OOP-emphasis distinguish Bloomberg from typical FAANG loops — practice these specifically.

Ready to practice for Bloomberg?

Start free →