RoundHound
Menu

What to expect in a Bloomberg interview

Bloomberg interview research for Software Engineer and Data Scientist, with 12 practice rounds across 2 role plans, example questions, and preparation advice.

Practice a Bloomberg round
Updated 4 min read

How Bloomberg interviews

Start with the reported process for your role, then use our practice rounds to rehearse the skills it tests. Follow your recruiter’s instructions for your team and location.

Software Engineer
Mid-level · 6 practice rounds · 4 h of practice
Data Scientist
Mid-level · 6 practice rounds · 4 h of practice

What Bloomberg says about its interviews

Bloomberg states that its experienced engineering interview process is customized to the role. Bloomberg says that no two interview processes will be exactly alike. Engineering: Experienced Hire Application Process

Bloomberg lists application, screening, assessment, interviews, and offer as general hiring stages. Bloomberg says the process can differ by job function and experience level. How We Hire | Bloomberg LP

Bloomberg typically schedules two phone interviews for Data Science candidates before an in-house visit. Data Science: Application Process

Bloomberg Software Engineer interview

Bloomberg’s process includes one or two phone interviews, including a 45- to 60-minute technical call on a computer, followed by in-house interviews. Software Engineer candidates in 2025 describe four virtual rounds of about 35 minutes, including coding and distributed-system design.

Our 6 practice rounds

40 min practice

Interest and Role Screen

Assess motivation for Bloomberg, role fit, relevant skills, and clear discussion of prior work.

Practice focus: Motivation for Bloomberg and this role. Strengths, weaknesses, and relevant experience. Situation-action-outcome stories about collaboration or challenges.

Illustrative practice follow-ups: “Probe strengths, weaknesses, and relevant skills.” “Ask for decisions and outcomes in one past example.”

Practice this round
60 min practice

Technical Phone Coding

Assess coding fluency, problem-solving structure, and communication during a live technical screen.

Practice focus: Medium array or hash-map problem. Stack or string processing variation. Resume context before a coding task.

Illustrative practice follow-ups: “Change input size or ordering constraints.” “Ask for an optimization and its cost.” “Probe empty, duplicate, and boundary inputs.”

Practice this round
35 min practice

Onsite Coding: Stream Aggregation

Test data-structure selection, incremental processing, and ability to extend a correct solution under time pressure.

Practice focus: Streaming top-K aggregation. Batch totals versus real-time results. Heap or ordered-map update strategy.

Illustrative practice follow-ups: “Add real-time results without rescanning all products.” “Probe ties, late events, and changing K.”

Practice this round
35 min practice

Onsite Coding: Cascading Arrays

Assess stack or array reasoning, repeated transformations, and correctness on cascading edge cases.

Practice focus: Adjacent-run removal. Generalized run threshold. Cascades after neighboring groups merge.

Illustrative practice follow-ups: “Change the minimum run length.” “Add several adjacent cascades.”

Practice this round
35 min practice

Onsite System Design

Assess production-oriented design reasoning for a high-volume, filtered market-data distribution service.

Practice focus: Market-data fanout to many subscribers. Symbol and event-type filters. Distributed delivery, backpressure, and failure recovery.

Illustrative practice follow-ups: “Increase subscriber count and event rate.” “Probe slow consumers and disconnected clients.”

Practice this round
35 min practice

Onsite Behavioral and Project

Assess ownership, collaboration, impact, judgment, and reflection through specific engineering examples.

Practice focus: Significant project deep dive. Collaboration or conflict example. Failure, learning, and changed behavior. Motivation and job priorities.

Illustrative practice follow-ups: “Ask why a key decision was made.” “Probe disagreement and personal influence.”

Practice this round

Bloomberg Software Engineer interview questions

  • Explain why you want to work at Bloomberg and why you want this role. Candidate report
  • Describe your strengths, weaknesses, relevant skills, and experience that fit the role. Candidate report
  • Explain a past project in detail and discuss prior experience. Candidate report
  • Solve LeetCode-style medium coding problems and explain the solution clearly. Candidate report
  • Solve a cache design or implementation problem. Candidate report
  • Solve a variation of Valid Parentheses. Candidate report
  • Design an application version system that can tag versions for different user groups. Candidate report
  • Implement a class design for complex financial logic after a discussion of financial concepts. Candidate report
  • Maintain product-volume totals from a trade-event stream and return the top K products both at day end and in real time. Candidate report
  • Design a market-data fanout service for tens of thousands of subscribers with different symbol and event filters. Candidate report

What candidates and sources report

  • Bloomberg states that the typical experienced engineering process starts with one or two phone interviews and then continues with in-house interviews. Bloomberg
  • Bloomberg states that the first experienced engineering phone call is with Human Resources or an engineer and focuses on the candidate's interests. Bloomberg
  • Bloomberg states that a later technical phone call is with an engineer, lasts 45 to 60 minutes, and requires computer access in a quiet place. Bloomberg
  • Bloomberg describes its technical interviews as interactive and collaborative. It assesses coding fluency and problem-solving. Bloomberg
  • Bloomberg asks experienced candidates to explain their motivation for Bloomberg and the role, their strengths and weaknesses, and their relevant experience and skills. Bloomberg

How to prepare

  • Design market-data fanout: Practice requirements, interfaces, filtering, backpressure, recovery, and scale trade-offs for many subscribers.
  • Prepare evidence stories: Build concise situation-action-outcome stories for motivation, collaboration, leadership, challenge, failure, impact, and learning.

Mistakes to avoid

  • Do not give generic reasons for wanting Bloomberg.
  • Do not describe team results without explaining your own actions.
  • Do not code before confirming input and output assumptions.
  • Do not rely on running code; inspect it and dry-run it manually.
  • Do not hide ranking costs inside vague helper functions.

Questions to ask your interviewers

  • Is the current mid-level loop still four virtual rounds of about 35 minutes?
  • Does this team require system design for the Software Engineer role?
  • How does the technical phone screen differ from the in-house coding rounds?
Open the Software Engineer practice plan

Bloomberg Data Scientist interview

Bloomberg’s process includes a Talent Acquisition screen, two Data Science phone interviews, and three technical rounds during a later in-house visit. Phone topics include algorithms, problem solving, machine learning, natural language processing, and your experience.

Our 6 practice rounds

40 min practice

Talent Acquisition Screen

Confirm clear communication, relevant experience, and readiness for the Data Science process.

Practice focus: Concise experience and role-interest overview. Collaboration or challenge example. Process readiness and logistics discussion.

Illustrative practice follow-ups: “Ask what changed because of your actions.” “Probe one collaboration difficulty and its resolution.”

Practice this round
40 min practice

Phone: Algorithms and Foundations

Assess problem solving across data structures, algorithms, and foundational technical reasoning.

Practice focus: Data-structure selection for a constrained task. Algorithm design with complexity analysis. Foundational machine learning or NLP concept.

Illustrative practice follow-ups: “Change one constraint and explain how the approach changes.” “Compare your approach with one simpler alternative.”

Practice this round
40 min practice

Phone: Applied ML and Experience

Assess depth of research or project experience and the quality of applied machine learning decisions.

Practice focus: Research or project walkthrough. Model choice and evaluation tradeoff. Open-ended applied machine learning discussion.

Illustrative practice follow-ups: “Probe how you measured success.” “Ask what you would change with more time or data.”

Practice this round
40 min practice

In-House: Technical Foundations

Use one technical round to test depth across algorithmic, machine learning, and problem-solving foundations.

Practice focus: Algorithm or data-structure transfer. Foundational NLP or ML comparison. Failure mode and edge-case analysis.

Illustrative practice follow-ups: “Introduce a new data constraint and retest the approach.” “Ask for a counterexample to the initial claim.”

Practice this round
40 min practice

In-House: Applied ML Case

Assess how the candidate frames an applied machine learning or data diagnostic problem before selecting a solution.

Practice focus: User-journey drop-off diagnosis. Messy event data and metric design. Model proposal with operational constraints.

Illustrative practice follow-ups: “Change the success metric and revisit the design.” “Ask how you would diagnose a disappointing result.”

Practice this round
40 min practice

In-House: Research and Project Depth

Assess ownership, technical depth, collaboration, and learning through a substantial research or project example.

Practice focus: End-to-end research project review. Experiment design and result interpretation. Collaboration, challenge, and reflection.

Illustrative practice follow-ups: “Probe one technical decision to its evidence.” “Ask how collaboration changed the final result.”

Practice this round

Bloomberg Data Scientist interview questions

  • Discuss your research and prior experience. Candidate report
  • Solve a problem that tests data structures, algorithms, and problem-solving skill. Candidate report
  • Write Structured Query Language (SQL) to find the second-highest salary in each department. Independent guide
  • Find the first recurring element in a collection. Independent guide
  • Implement binary search and explain its time complexity. Independent guide
  • Use raw Bloomberg Terminal user-interaction logs to identify user-journey drop-off points and propose a churn-prediction model. Independent guide
  • Clean messy data with missing values, perform exploratory analysis, and analyze timestamp alignment or rolling transaction-volume averages. Independent guide
  • Explain a past project in depth, including its technical details, coding, and modeling work. Candidate report
  • Discuss empirical data and data distributions. Candidate report

What candidates and sources report

  • Bloomberg says its general screening stage uses a video or telephone interview with its in-house Talent Acquisition team. Bloomberg
  • Bloomberg says Data Science phone interviews can cover data structures, algorithms, problem solving, foundational NLP and ML, applied ML, and open-ended ML questions. Bloomberg
  • Bloomberg says Data Science interviews often begin with a discussion of the candidate's research and experience. Bloomberg
  • Bloomberg invites a Data Science candidate to an in-house interview after successful phone interviews and a mutual match. Bloomberg
  • Bloomberg's Data Science in-house interview includes three technical rounds. Bloomberg

How to prepare

  • Practice algorithm reasoning: Solve representative data-structure problems in code, state complexity, and complete a verbal manual dry-run without compiler, tests, or CI.
  • Refresh applied ML foundations: Review model choice, evaluation, leakage, NLP basics, data quality, and open-ended tradeoffs. Explain each topic with a small example.
  • Prepare project evidence stories: Build concise situation, action, outcome, and reflection stories for research, collaboration, challenge recovery, innovation, and measurable impact.

Mistakes to avoid

  • Do not give a broad résumé summary without evidence.
  • Do not claim team outcomes as your individual contribution.
  • Do not jump to an algorithm before clarifying constraints.
  • Do not state complexity without linking it to the chosen structure.
  • Do not describe a model without its evaluation design.

Questions to ask your interviewers

  • How are the two Data Science phone interviews divided across algorithms, machine learning, and experience?
  • What format and duration does each of the three in-house technical rounds use?
  • Does the current process include live coding, SQL, a case study, or a presentation?
Open the Data Scientist practice plan

Sources

Latest catalogue research: . Practice exercises and follow-ups are our own; they are not confidential interview questions.

Independent preparation using Bloomberg as a practice target. Not affiliated with, endorsed by, or sponsored by Bloomberg.