RoundHound
Get accessSign in
Prepare
HomeHomeJobsJobsPractice historyHistoryProgressProgress
Get full access?Sign in
Jobs/Bloomberg

Software Engineer

Bloomberg · Mid-level

Research from Oct 76 rounds, none tried
How did it actually go?

Next: your first full round

Do the Interest and Role Screen round.

One full round, as long as theirs, shows where you stand before you work on anything specific.

Set up this round →Practice the full interview day
Length40 min · Mid-level

The rounds

6 rounds · 4 h

Pick a round to see what it asks of you and where you stand on it.

Interest and Role Screen

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

Behavioral · 40 minSet up this round →
Not tried yetNo attempt yet.

What strong sounds like

  • Connects Bloomberg and role interest to specific engineering work and realistic responsibilities.
  • Clearly separates personal decisions and actions from team activity in a relevant example.
  • Names a challenge or weakness, explains the response, and states a concrete improvement.

Expect to be pushed on

Probe strengths, weaknesses, and relevant skills.
Ask for decisions and outcomes in one past example.

Shapes of problem you may get

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

How to prepare

  1. Choose a specific Bloomberg motivation

    Write three points that connect Bloomberg to your engineering interests, such as data-intensive systems, reliability, or user impact. Link each point to the Software Engineer role and work you want to do.

    Bloomberg says the first experienced-engineering call focuses on interests. Generic company praise will not show why this role fits you.

    Company researchEngineering: Experienced Hire Application ProcessInterview guide | Experienced Hires | Bloomberg LP

Your first try takes the full 40 minutes, like the real one.

What they look for

Researched yesterday

Bloomberg’s own guidance describes one or two phone interviews, including a 45- to 60-minute technical call on a computer, followed by in-house interviews. One 2025 Software Engineer candidate describes four virtual rounds of about 35 minutes, including coding and distributed-system design. The number of rounds, their order, and how much is behavioral aren’t confirmed for mid-level roles.

They reward

  • Use collaborative, interactive reasoning during technical discussions.
  • Clarify constraints before choosing a coding or design approach.
  • Explain actions, outcomes, trade-offs, and learning with specific evidence.

What 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.

How sure we are

Worth redoing if you hear something from the recruiter that contradicts this.

Attempts

Every round you’ve done for this job, newest first.

All attempts in History →

Interest and Role Screen, Technical Phone Coding, Onsite Coding: Stream Aggregation, Onsite Coding: Cascading Arrays, Onsite System Design, and Onsite Behavioral and Project have no attempts yet.

  • Select two personal examples

    Choose one collaboration example and one challenge or weakness example. For each, note the situation, your decisions, your actions, the outcome, and one concrete improvement.

    Bloomberg asks about strengths, weaknesses, relevant skills, and examples of collaboration and overcoming challenges in situation-action-outcome form.

    Company researchInterview guide | Experienced Hires | Bloomberg LP

  • Rehearse clear ownership language

    Briefly explain each example aloud using “I” for your decisions and actions. Mark any team result that you cannot connect directly to your own work, then replace it with a result you can explain.

    The round assesses prior work and role fit. Clear personal ownership makes your contribution easier to assess.

    Suggested approach

    • Then try the round

    You have one focused Bloomberg-and-role explanation and two example outlines with personal actions, outcomes, and improvements.

    Resources to focus on
    • Interview guide | Experienced Hires | Bloomberg LP

      Focus on “business interview” sections about Bloomberg’s work, values, and culture. The page is long, so select role-relevant material.

      Use it to replace generic motivation with two or three specific points about Bloomberg and your role fit.

    Do

    • Connect Bloomberg and role motivation to specific engineering interests.
    • Use situation, actions, and outcome for one collaboration or challenge example.

    Avoid

    • Do not give generic reasons for wanting Bloomberg.
    • Do not describe team results without explaining your own actions.
    Confirmed · 11
    • Bloomberg states that its experienced engineering interview process is customized to the role. Bloomberg says that no two interview processes will be exactly alike.
    • Bloomberg states that the typical experienced engineering process starts with one or two phone interviews and then continues with in-house interviews.
    • Bloomberg states that the first experienced engineering phone call is with Human Resources or an engineer and focuses on the candidate's interests.
    • 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.
    Likely · 1
    • A mid-level Software Engineer candidate may face production-oriented design follow-ups, because an exact-level 2025 report included market-data fanout design and adjacent senior postings require distributed-system and system-design experience.

    Worth asking them

    Questions that fill in what the research couldn’t tell us.

    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?

    Research status

    Collected Oct 7. If the recruiter tells you something this brief contradicts, correct it after the interview and the brief updates.

    Correct this brief