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

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

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

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

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.

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.

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

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

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.

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