Bloomberg System Design Interview: Ticker Plant, 4 Prompts & Prep

Last updated: November 2026

Quick Answer

The Bloomberg system design interview is a one-hour onsite round, mostly for experienced engineers, where you design a practical system, often a market data or trading feed, in front of two engineers from the team. Bloomberg’s hiring page says in-house rounds run about an hour with two engineers and that its open-ended questions test design skills along with coding. Not every loop has one: interviewing.io notes some teams ask only coding. Rehearse a timed round with OphyAI System Design, our AI system design interview copilot, and read the Bloomberg interview guide for the full process.

Element	What we found
Length and panel	About 1 hour with two engineers (Bloomberg)
Who gets it	Experienced hires, team dependent (interviewing.io, candidates report)
Reported prompts	Multi-source trading data display, a stock exchange, standard designs such as ride-sharing
Twist	You may be asked to write code in the design round (interviewing.io)
Time squeeze	One senior candidate reports 25 minutes of resume talk before the design question

What Bloomberg Is Testing in This Round

Bloomberg’s own engineering story explains the bar. Its Ticker Plant publishes market data in real time to hundreds of thousands of Terminal subscribers, processing over 200 billion pieces of financial information a day. Feed handlers normalize each exchange’s data first, and Bloomberg stresses strict ordering and extreme accuracy. So interviewers listen for:

• Ordering and correctness. Prices must arrive in order and never silently drop. Say how you sequence updates and detect gaps.
• Fan-out. One update goes to many clients. Explain pub/sub by symbol and what you do with slow consumers.
• Numbers. 200 billion a day is about 2.3 million messages a second on average, before market-open peaks. Our back-of-the-envelope calculation guide shows how to do that math fast.
• The why. Bloomberg says it cares about your thought process as much as the solution, so give a reason for each choice.

What to Expect

Rounds are about an hour with two engineers. A senior candidate who interviewed in New York in November 2025 reports 25 minutes of resume and scaling questions before the design prompt, and advises moving straight to the core design and scaling issues. Plan a 30-minute version of each design.

Prepare for that squeeze with a short Mock round in OphyAI System Design: set 35 minutes on the built-in whiteboard and let the voice AI interviewer push you with follow-ups.

Example Questions and How to Answer Them

”Design a trading system that takes inputs from multiple sources and displays them to users.”

Approach: A senior candidate reports this from a 2022 New York onsite and says the interviewers wanted real system design, not object design. Put a feed handler per source that normalizes into one schema, add a sequence number per instrument, detect and refill gaps, and publish by symbol. Keep a last-value cache so a new screen shows prices at once, and merge updates for slow clients. Practice fan-out with the news feed prompt and the distributed cache prompt.

”Design a stock exchange.”

Approach: interviewing.io lists this as a Bloomberg-style prompt. Draw an order gateway with risk checks, a matching engine per symbol that processes orders one at a time so results are repeatable, an order book, and a market data publisher. Be ready to code the order book insert. Our list has no exchange prompt; the payment ledger and rate limiter drills cover the append-only log and the gateway.

”Design price alerts for Terminal users.”

Approach: This is a practice prompt that matches the domain, not a reported question. Users set rules such as “tell me if this stock drops 5%”. Evaluate rules on the price stream, shard by symbol, and avoid sending the same alert twice. Practice with metrics and alerting and the notification system.

”Design a ride-sharing service.”

Approach: A senior candidate reports this standard prompt in late 2025. Cover location updates, matching and trip state. Practice with ride-hailing dispatch.

How to Prepare in 3 Days

Day 1. Read Bloomberg’s Ticker Plant story. Learn the terms: sequence numbers, gap fill, conflation, pub/sub, last-value cache, p99 latency.

Day 2. Design the trading feed and the exchange out loud in 30 minutes each. Then write a short order book in your interview language.

Day 3. Run a timed Mock round (20 credits) and read the Scorecard: a 0 to 100 score, 7 skill scores, your time on each step against a target and 3 fixes. For the real call, Live Copilot (30 credits a session) listens to the interviewer, reads your board from a shared tab or window, and suggests what to say and draw next. System Design is on the Premium plan ($59 a month, 500 credits). On desktop its main window is left out of screen sharing; it is not hidden from a webcam or a person in the room. Start practicing →

Common Mistakes and Red Flags

Object design instead of system design. Classes and methods are not what this round wants unless asked.

Ignoring order. A feed that can show an old price after a new one is broken.

A long warm-up. With resume talk eating time, a 15-minute requirements phase leaves no room for deep dives.

Related Guides

• Bloomberg interview guide
• Rippling system design interview
• DoorDash system design interview
• System design interview guide

Frequently Asked Questions

Does Bloomberg ask system design questions?

Yes, for many experienced roles, but it depends on the team. Bloomberg says its questions test design skills along with coding. interviewing.io notes some loops are coding only, and a third-party review of 17 candidate reports found a design round in 4, none of them for new grads. Ask your recruiter which rounds you will get.

What system design questions does Bloomberg ask?

Bloomberg does not publish its questions. Candidates and prep sites report finance-flavored prompts such as a trading system that combines data from several sources and a stock exchange, plus standard designs like ride-sharing. Expect caches, queues and pub/sub applied to real-time market data, with ordering and accuracy as the hard parts.

Do you write code in the Bloomberg system design interview?

Sometimes. interviewing.io says that, unlike at many companies, you may be asked to write code during the design round. Bloomberg lets you choose paper, a whiteboard or a laptop and the language you know best, so practice writing a small core piece, such as an order book, after each design.

How should I prepare for the Bloomberg system design round?

Learn how real-time market data works, then practice short rounds, because resume questions can take the first 20-25 minutes. OphyAI System Design runs Mock rounds from 35 to 60 minutes with a voice AI interviewer and up to 3 hints, and ends with a Scorecard that shows which step ran long.

Sources and verification notes

Sources checked November 2026. Bloomberg publishes its interview format but no question bank, so prompts here are candidate-reported or from third-party prep sites, labelled as such.

• Bloomberg, Engineering experienced hire application process: first-party, phone interviews, one-hour in-house rounds with two engineers, design skills, paper, whiteboard or laptop.
• Bloomberg, How Bloomberg handles a massive wave of real-time market data: first-party, Ticker Plant scale, feed handlers, ordering and accuracy (March 2022).
• interviewing.io, Bloomberg interview process: third-party, team-dependent design rounds, stock exchange prompt, code in the design round.
• LeetCode Discuss, Bloomberg senior software engineer, November 2025: candidate-reported time split. Self-reported.
• LeetCode Discuss, Bloomberg onsite, February 2022: candidate-reported multi-source trading system prompt. Self-reported.
• LeetCode Discuss, Bloomberg senior software engineer, December 2025: candidate-reported ride-sharing prompt. Self-reported.
• PracHub, Bloomberg software engineer interview guide: third-party review of 17 candidate reports.