Mid-level
Prepare for the Bloomberg Software Engineer interview with 6 practice rounds and what each one looks for. Pick any round and an AI interviewer runs it with you at full length, with follow-up questions. Afterwards you’ll see what went well and what to work on next.
Your first round is free. No card needed.
Next: your first round
Assess motivation for Bloomberg, role fit, relevant skills, and clear discussion of prior work.
Probe strengths, weaknesses, and relevant skills.
Ask for decisions and outcomes in one past example.
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
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
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
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.
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.
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?
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 full round yet.