Bloomberg SWE Interview: Technical Phone Screen Guide

Estimated read time: 7-9 minutes

Summary: The Bloomberg SWE technical phone screen is the first major technical gate in many reported loops. The research is strongest for early-career and mid-level coding screens, usually around 45-60 minutes with an engineer. This guide explains the format, realistic question shapes, level differences, and the habits that keep a phone screen from turning into a silent coding exercise.

TL;DR + FAQ (read this first)

At-a-glance takeaways

• The technical phone screen is commonly reported as 45-60 minutes.
• The interviewer is usually an engineer and the format is phone or video with coding or problem solving.
• Bloomberg reports are especially strong for intern, new grad, junior, and mid-level coding-heavy paths.
• Senior candidates may still get coding, but deeper technical discussion can appear later.
• Exact questions vary, so prepare for topic families: arrays, strings, linked lists, trees, maps, and complexity.

Quick FAQ

Is this just an algorithm screen?
Mostly, but communication and edge-case handling are part of the signal.

Does every Bloomberg SWE candidate get this?
The research supports it as common, but paths can vary across SWE, financial software engineer, intern, new grad, and experienced roles.

Can senior candidates see design here?
Possibly, but the public evidence is weaker. Treat deeper design as possible rather than guaranteed.

---

1) How the screen runs

Expect a live coding or problem-solving conversation. You may work in a shared editor, talk through the approach, write code, test examples, and discuss time and space complexity.

The research notes that Bloomberg public reports mix several paths. That matters because an early-career phone screen may be pure coding, while an experienced candidate may receive more follow-up depth. Do not overfit to one report. Prepare to solve and explain clearly.

---

2) Candidate-facing question examples

Exact Bloomberg wording is not reliably public, so these examples translate the sourced topic families into interview-style tasks.

• Given a string of market symbols and counts, return the most frequent symbols in order. How would your approach change if the stream is too large to fit in memory?
• Given a linked list, remove the nth node from the end in one pass. Walk through the edge case where the head is removed.
• Given a binary tree, return the level-order traversal. Then return the rightmost value at each level.
• Given a list of intervals representing booked time windows, merge overlaps and return the next available gap of length k.
• Given a list of trades with user IDs, detect duplicate events within a time window.
• Given two sorted lists of updates, merge them while preserving timestamp order and removing duplicate IDs.
• Implement a small cache with get and put. Then add eviction when capacity is reached.

---

3) Evaluation signals

Strong candidates clarify the input, choose a direct approach, code steadily, and test the parts of the solution most likely to break. The interviewer should hear why a map, pointer pair, queue, heap, or traversal is appropriate.

For early-career candidates, fundamentals and coachability are central. For experienced candidates, the same screen can also reveal whether you communicate tradeoffs cleanly when the problem grows.

---

4) Common failure modes

Solving silently. The interviewer cannot score reasoning they never hear.

Forgetting edge cases. Empty input, duplicate events, single-node lists, skewed trees, and boundary timestamps matter.

Overcomplicating a screen question. Start with the simplest correct approach that meets the constraints.

Ignoring role variance. Bloomberg reports mix paths, so confirm your exact process with the recruiter.

---

5) How to prepare

• Practice arrays, strings, maps, linked lists, trees, queues, heaps, intervals, and simple caches.
• Run 45-minute sessions where you explain complexity and test edge cases out loud.
• Practice turning a topic family into a concrete problem instead of memorizing exact questions.
• For experienced loops, prepare to connect follow-ups to tradeoffs and maintainability.
• Ask your recruiter whether your screen is SWE, FSE, intern, new grad, or experienced-role specific.