Interview Playbook / Finance

How Bloomberg Interviews in 2026: Process, Questions & What They Score

HOW TO READ THIS PLAYBOOK

Compiled from 20 public sources: candidate interview reports, coaching guides, and Bloomberg's own hiring pages. Interview processes change and vary by role, team, level, and region. This is one well-documented shape of Bloomberg's interviews to prepare against, not a script of what your interview will be. Confirm specifics with your recruiter. SupaCV is not affiliated with or endorsed by Bloomberg.

High confidenceLast verified SEP 202620 sourcesSources

Bloomberg L.P. is a private financial data and media company built around the Bloomberg Terminal. It hires across several distinct tracks (software engineering, data science, Financial Solutions / analytics and sales, and Bloomberg News), and each track runs a different loop. This dossier covers the software engineering track, because that is the track Bloomberg publishes the most detail about, the track with by far the most public candidate reporting, and the one behind the Terminal product the company is best known for. Where evidence exists for the data science and client-facing sales tracks it is called out in the notes. The Bloomberg News loop is not covered because no official page for it could be found; Bloomberg's FAQ says only that certain roles may require a pre-recorded video interview to evaluate language proficiency, verbal presentation and/or technical abilities, without naming which roles. The engineering process is coding-centric and typically runs four to five rounds. Bloomberg's own careers site describes an opening phone call from HR or an engineer about your interests, a 45 to 60 minute technical phone interview with an engineer, and then in-house rounds ranging from two hours to a full day, each round about an hour with two engineers from the hiring team. Coaching and candidate-report sites put the end-to-end timeline at roughly three to eight weeks, with the tightest aggregate estimate (from a site reporting 20 candidate submissions) at four to six weeks. Entry-level and intern applications are deliberately not tied to a specific team; Bloomberg says it uses the interview process itself to match you to a team. Bloomberg does publish an evaluation framework for engineering technical interviews: four "main pillars" listed in the FAQ on its How We Hire page. Those four items are reproduced verbatim in the framework field. Bloomberg does not publish a company-wide behavioral competency rubric, so any "four core values" behavioral rubric seen on third-party sites is not sourced to Bloomberg and is not used here. Notable Bloomberg-specific traits: interviews are described as interactive and collaborative rather than adversarial, the company is explicitly language-agnostic and lets you pick paper, whiteboard or laptop, it says it weighs problem-solving and coding fluency above finding the optimal solution or producing running code, and it publishes an explicit conduct expectation that candidates represent their own capability honestly, naming AI directly.

The Process

  1. 1

    Application, plus a Plum assessment for certain entry-level roles · varies

    Bloomberg says Talent Acquisition reviews every application and that certain entry-level roles also require a Plum assessment, which it describes as helping to evaluate qualities important for those roles; the page footnotes Plum with a Bias Audit link. The company states only that the review 'may take some time' due to application volume, so turnaround varies by role, region and volume. No source states a number.

    No published duration

  2. 2

    Screening call with in-house Talent Acquisition (or an engineer) · 20 to 45 minutes

    Bloomberg's How We Hire page describes this as a video or telephone interview with its in-house Talent Acquisition team; its experienced-hire engineering page says the opening call comes 'from HR or an engineer to better understand your interests'. Bloomberg gives no length. Fetched coaching sources report 20 to 30 minutes generally and 45 to 60 minutes for engineering roles (4dayweek), 30 to 45 minutes (Prepfully, TechPrep, Aced/Exponent), 30 minutes (interviewing.io) and 20 to 45 minutes (FinalRound). Length varies by function and level. Some engineering loops place the recruiter conversation later, after the coding rounds.

  3. 3

    Assessment, assessment day or pre-recorded video interview (role dependent) · varies

    Bloomberg states that certain entry-level roles require an assessment day or task, that you will be told by Talent Acquisition if your role needs one, and that assessments include but are not limited to pre-recorded video interviews, virtual skills assessments, writing tests and technical or coding assessments. It says pre-recorded video interviews evaluate skills such as language proficiency, verbal presentation and/or technical abilities for certain roles. Whether this stage happens at all varies by level, function and application route: Aced/Exponent reports campus and referral candidates often skip the online assessment while some online applicants get a short automated coding test first, and FinalRound says the online assessment applies mainly to entry-level technical roles.

    Not every candidate sees this stage

  4. 4

    Technical phone or Zoom interview with an engineer · 45 to 60 minutes

    This is the one duration Bloomberg itself publishes: a 45 to 60 minute conversation with one of its engineers, focused on coding fluency, problem-solving skills and computer science fundamentals such as data structures and algorithms, with time left for your questions. Coaching sources report one or two of these sessions, often run on HackerRank CodePair alongside Zoom. For students the equivalent opening round is a Zoom interview with an engineer covering technical ability plus background and interests. The data science track runs two phone interviews before an in-house visit, sometimes shadowed by members of other teams so you are considered for several teams at once.

  5. 5

    In-house or virtual onsite technical rounds · two hours to a full day, each round about one hour

    Bloomberg publishes this range for experienced engineering hires and says each round is about an hour with two engineers from the team you are interviewing for, so the company gets several perspectives. The student page says 2 to 3 technical rounds; the data science page says 3 technical rounds that become more high level and design oriented, plus lunch, an HR meeting and manager and stakeholder conversations, with an optional 30 to 60 minute research presentation. Coaching sources report 3 to 5 rounds. Total length varies by role and interviewer availability, and some candidates get the rounds spread across separate days rather than one Superday.

  6. 6

    Code review round (reported for some engineering loops) · about 60 minutes

    Two independent coaching guides describe a round where you review existing code rather than write new code. Prepfully describes several hundred lines of intentionally buggy code to critique as if reviewing a junior developer's pull request; TechPrep puts it at roughly 200 or more lines and says it is scored on bugs found, optimizations, maintainability and production readiness. Bloomberg does not document this round, and it does not appear in every reported loop, so treat it as team dependent.

    Not company-documented; team dependent

  7. 7

    System design and technical trade-off round · 45 to 60 minutes

    Reported as applying mainly to mid-level and senior candidates; Prepfully states entry-level candidates do not get system design questions. Aced/Exponent places system design, language trade-offs and project depth in the hiring manager round. interviewing.io reports that each team asks its own questions and may run a slightly different process, and that it is possible to get only coding questions with no system design at all, so presence and length vary by team and level. Design prompts skew toward financial systems (market data, order matching, time-series storage) rather than generic consumer scale.

    Level and team dependent

  8. 8

    Hiring manager and final behavioral round · 30 to 60 minutes

    Reported lengths differ: interviewing.io describes a one hour behavioral round plus a one hour final interview with a senior manager as part of a four hour virtual onsite; TechPrep reports a 30 to 45 minute engineering manager round and a separate roughly 30 minute HR closing call; Aced/Exponent puts behavioral questions and motivation in a 30 to 45 minute recruiter interview. Motivation ('why Bloomberg') is the consistent theme, and Bloomberg's own FAQ tells candidates to prepare it.

  9. 9

    Team matching, offer and onboarding · varies

    Bloomberg states that entry-level software engineering and intern positions are not specific to a team or department and that it uses the interview process to learn your skills and interests and match you to a team. Coaching sources describe team matching followed by offer and negotiation. End-to-end timeline estimates across fetched sources range from about 30 days measured from first interview to decision (4dayweek, which is not application to offer) to 3 to 7 weeks (Prepfully), 3 to 6 weeks (codinginterview.com), 4 to 6 weeks (Interview Query, from 20 candidate reports), 4 to 7 weeks (TechPrep) and 4 to 8 weeks (FinalRound). Typical total rounds: 4 to 5.

    Total-timeline estimates disagree across sources

Evaluation Framework

Bloomberg engineering technical assessment: four main pillars

Data Structure KnowledgeAlgorithms KnowledgeProblem Solving SkillsCommunication Skills

Published by Bloomberg on its How We Hire page, in the FAQ answer to "What happens in a technical assessment for Engineering roles?": "During our technical interviews, you will be assessed on four main pillars", followed by the four items above. The item names and count were re-verified against the live page on 2026-09-06 (twice, in two separate passes) and are copied exactly and completely. Scope and limits: this framework is stated for engineering technical assessments only. It is not a company-wide behavioral rubric, and Bloomberg publishes no leadership-principle style value list for interviews. Third-party claims that Bloomberg scores behavioral answers against "innovation, integrity, diversity and collaboration" (FinalRound) or against five attributes such as "ownership and impact" (codinginterview.com) are not traceable to any Bloomberg page and are excluded here. The only value language on Bloomberg's own hiring page is "doing the right thing" in the candidate conduct section, which is a conduct expectation, not a scored rubric. Bloomberg pairs the four pillars with stated interviewing conditions on the same page and on the engineering application-process pages: questions are open-ended, you code in whichever language you are most comfortable with, and the company says it focuses "more on your problem-solving skills and coding fluency than on finding the most optimal solution and running code." The experienced-hire page lists four items under a separate Tips heading: "Ask for help", "Verify it's the correct assumption", "Explain your thinking", "Listen carefully". Those are prep tips, not scored pillars, so they are kept out of the framework list. Source: https://www.bloomberg.com/company/careers/how-we-hire/

Sample Interview Questions

Coding: data structures and algorithms14 questions
  • Given a 2D grid of land and water, count the number of islands.Grid traversal with DFS or BFS, marking visited cells so each island is counted exactly once.
  • Design and implement an LRU cache with O(1) get and put.Hash map plus doubly linked list for O(1) get and put; be ready to justify the memory overhead of the list.
  • Given a collection of intervals, merge all overlapping intervals.Sort by start then sweep once, extending the current interval whenever the next one overlaps it.
  • Write code to check whether a binary tree is a valid binary search tree.Recursion with min and max bounds per subtree, or an in-order traversal checking strictly increasing values.
  • Write a program that checks whether a given binary tree is balanced.Post-order recursion returning subtree height and short-circuiting when heights differ by more than one.
  • Given a rotationally sorted array, write code that finds a particular element.Modified binary search that decides which half is sorted before discarding the other half.
  • Determine whether any two integers in a collection add up to a given value.One pass with a hash map of seen values versus sort plus two pointers; discuss the time and space trade-off.
  • Write a program that determines whether a permutation of a string is a palindrome.Character frequency counting; a permutation can be a palindrome only if at most one character has an odd count.
  • Reverse a linked list, then explain your approach.Iterative pointer reversal with prev, curr and next; be ready to describe it in pseudocode before coding.
  • Print the values at every level of a binary tree.Breadth-first traversal with a queue, using the queue size to mark level boundaries.
  • Find the longest substring without repeating characters.Sliding window with a hash map of last-seen indices to advance the left edge past repeats.
  • Given a series of stock prices, calculate the maximum profit from one buy and one sell.Single pass tracking the running minimum price and the best price difference seen so far.
  • Given candidate numbers and a target, return all unique combinations that sum to the target (Combination Sum).Backtracking with candidate reuse and pruning once the running total exceeds the target.
  • Merge two sorted arrays into one sorted array.Two pointers merging from the back when one array has spare capacity, avoiding element shifts.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

Coding: design in code1 question
  • Here is an existing code file of a few hundred lines. Review it: find the bugs, suggest optimizations, and tell us whether it is production ready.Reading unfamiliar code for bugs, edge cases, performance and maintainability, then explaining findings clearly.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

System design3 questions
  • Design an order matching engine.Price-time priority order books, matching semantics, ordering guarantees and a latency budget.
  • Design a system to handle stock market data and orders.Streaming ingestion, ordering and consistency guarantees, backpressure and fan-out to many consumers.
  • What aspects would you consider while building a scalable software tool, and how would you make sure a system has low latency?Throughput versus latency trade-offs, caching, sharding and pub/sub messaging with backpressure handling.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

Behavioral and motivation7 questions
  • Why Bloomberg? What draws you here, and how does this role fit your long-term career goals?
  • Walk me through a project on your resume. What were the technical design choices and challenges, why did you make those decisions, and what impact did it have?
  • Tell us what you learned from the most challenging project you have worked on.
  • Tell us about a time when you disagreed with a superior, or with a team decision. How did you handle it?
  • How do you manage stressful situations at work, especially under tight deadlines?
  • Tell us about a time when you had to make a big decision and it turned out badly.
  • How would you handle conflict in the office, or a team where colleagues held differing opinions?

Coach's Tips

Optimise for narrated reasoning, not a finished optimal answer. Bloomberg states on its own careers site that it focuses more on your problem-solving skills and coding fluency than on finding the most optimal solution and running code, and its student page says not to worry about compiling the code because it cares more about thought process than syntax. Silence while you think is the expensive mistake here, not a suboptimal first approach. Source: https://www.bloomberg.com/company/careers/how-we-hire/ and https://www.bloomberg.com/company/careers/application-process/engineering-student/

Treat the interviewer as a pair programmer. Bloomberg calls its technical interviews interactive and collaborative and publishes four in-interview tips: ask for help, verify it is the correct assumption, explain your thinking, and listen carefully. It also says its questions are open-ended by design and that when interviewers question your assumptions and change constraints it means they are excited about your approach. Ask clarifying questions and check assumptions out loud before you write code. Source: https://www.bloomberg.com/company/careers/application-process/engineering-experienced-hire/ and https://www.bloomberg.com/company/careers/application-process/data-science/

Prepare finance-shaped system design, not generic consumer scale. Reported design prompts cluster on order matching engines, stock exchanges, time-series storage for historical prices, and market-data and order handling, with the emphasis on throughput, latency and data consistency. Bring a rough latency budget and an opinion on ordering and consistency guarantees rather than a stock URL-shortener answer. Sources: https://interviewing.io/bloomberg-interview-questions, https://prepfully.com/interview-guides/bloomberg-software-engineer, https://www.techprep.app/blog/bloomberg-interview-process

For entry-level and intern roles, interview as if you are also picking a team. Bloomberg states these positions are not specific to a team or department and that it uses the interview process to learn your skill set and interests so it can match you. Being concrete about what you want to work on is functionally part of the assessment, and the company explicitly invites you to ask engineers how they work, what their day looks like, and about training and volunteering. Source: https://www.bloomberg.com/company/careers/application-process/engineering-student/

Decide your language and medium in advance, and say so. Bloomberg says it is language-agnostic, that you code in whichever language you are most comfortable with, and that you can indicate a preference for paper, whiteboard or laptop. Pick the language you can debug fluently under pressure rather than the one you think looks impressive, keeping the role in mind. Source: https://www.bloomberg.com/company/careers/application-process/engineering-student/ and https://www.bloomberg.com/company/careers/application-process/engineering-experienced-hire/

Take the published conduct expectation literally. Bloomberg's How We Hire page states that it expects candidates to represent themselves accurately and honestly across resumes, assessments, assignments and interviews, and names AI explicitly among the resources this applies to. Use AI to prepare, not inside an assessment, and make sure every line on your resume is something you can defend, because the reported hiring manager round asks you to defend the technical decisions on it. Sources: https://www.bloomberg.com/company/careers/how-we-hire/ and https://www.tryexponent.com/guides/bloomberg-software-engineer-interview

Common questions

How many stages are in Bloomberg's interview process?+

Bloomberg's process has 9 stages, in order: Application, plus a Plum assessment for certain entry-level roles, Screening call with in-house Talent Acquisition (or an engineer), Assessment, assessment day or pre-recorded video interview (role dependent), Technical phone or Zoom interview with an engineer, In-house or virtual onsite technical rounds, Code review round (reported for some engineering loops), System design and technical trade-off round, Hiring manager and final behavioral round, Team matching, offer and onboarding.

What framework does Bloomberg use to evaluate candidates?+

Bloomberg evaluates candidates against Bloomberg engineering technical assessment: four main pillars: Data Structure Knowledge, Algorithms Knowledge, Problem Solving Skills, Communication Skills.

What kinds of questions does Bloomberg ask?+

Bloomberg's question bank spans 4 categories: Coding: data structures and algorithms; Coding: design in code; System design; Behavioral and motivation.

How reliable is this Bloomberg interview playbook?+

This playbook is high confidence, compiled from 20 public sources, and last verified September 5, 2026. It describes one well-documented shape of Bloomberg's interviews, not a guarantee of what any individual loop will look like.

Sources

How similar companies interview

Compare Bloomberg's process with other Finance companies in this playbook:

Interviewing at Bloomberg?

Add it as a Target Role and tailor your resume against the actual job description.

Add Bloomberg as a Target Role