Bloomberg SWE Internship & New-Grad Interview

The Bloomberg software engineer internship and new-grad loop is a lighter version of the full-time process, built around the same coding rounds. A recruiter screen comes first, then one or two technical screens run in HackerRank CodePair, then a superday. Students and new graduates usually skip the system design round, since nobody expects you to have architected a production system yet. Coding and the motivation questions carry the whole decision. What does not drop is the two-problem coding hour and the scored "Why Bloomberg?" conversation.

Bloomberg runs a large summer internship in engineering and hires new graduates into the same teams, mostly out of its New York and London offices. The product is the Terminal, a real-time financial information system, so the engineering leans toward building small correct stateful services rather than sprawling distributed systems. That bias shows up directly in what the interview asks, covered below and in more depth in The Coding Rounds.

How the student loop differs from full-time

The shape is the full-time pipeline with a stage removed. A recruiter call of thirty to forty-five minutes covers logistics and motivation. One or two technical phone screens follow. Each runs about an hour in HackerRank CodePair with a Bloomberg engineer on the call, and each carries two problems rather than one. The superday is the onsite: a couple of coding rounds and a behavioural or hiring-manager conversation. The system design round that a mid-level or senior candidate sits is generally not part of a student loop.

Team matching still applies. Passing the superday means Bloomberg has decided to hire you, not which team you join. That is a separate conversation, and it can add a week or two. For an intern it decides which product surface you spend the summer on, whether that is the Terminal's core data infrastructure, news systems, or trading. Ask what a team owns before you accept a match.

What the coding rounds test

The coding is recognisable interview material, mostly medium difficulty, with very little puzzle-box character. The distribution differs, because Bloomberg concentrates on a narrower slice of the syllabus than a generic large-tech loop. Design-in-code problems, where you build a small working structure such as a least-recently-used cache or a min-stack, recur throughout. Linked structures are weighted unusually heavily. Grid traversal leads the raw frequency, with a Premium question counting the single most-asked problem, and it often arrives reskinned as clouds and clear sky rather than land and water.

Dynamic programming, by contrast, is light. Word Break is essentially the only DP problem that recurs, so a week spent grinding DP has a poor return here. The full ranking, with the specific problems behind each category, is in The Coding Rounds and the pattern lessons beneath it. Because every round holds two problems, pace to roughly twenty minutes each and bank a working solution before you polish it.

Why Bloomberg is still a scored question

Even for an internship, motivation is genuinely assessed. It is asked early, on the recruiter call, before you have warmed up. Bloomberg is private, so it cannot compete on the equity upside a public technology company offers, and it knows most candidates arrive having never touched the Terminal. It therefore screens hard for people who want this specific job rather than any job. A generic answer about scale and impact reads as someone who applied everywhere with one cover letter.

Have a real answer ready, and keep it concrete. The breadth of data behind the Terminal. The latency constraints on market data. The newsroom that sits inside the same engineering company. Any of those is genuine, as long as you connect it to something you have built or care about. The full treatment, including the engineering-practice questions about testing that live in this round, is in The Behavioural Interview.

Timing and the application

Bloomberg recruits students on a university cycle that opens early. Postings for summer internships often go up the previous autumn, alongside on-campus recruiting and career fairs. They fill on a rolling basis, so applying late means competing for fewer remaining spots. Apply as soon as postings open. Use a referral or a campus event if you have one. And have your coding preparation underway before you submit, because the first technical screen can follow the application quickly.

Budget four to seven weeks from the recruiter call to a decision, plus team matching on top. If you have a preference between New York and London, raise it early, because the office you interview into shapes which teams are available to you.

What the pay looks like

The internship is paid, with competitive monthly compensation. If a strong summer leads to a full-time offer, know that Bloomberg is private and grants no equity. A package is base salary, a performance bonus set as a percentage of base by level, and usually a signing bonus. Public reporting puts full-time software engineer total compensation in the United States broadly in the low two hundreds of thousands, all cash, with New York toward the upper end. The negotiation that follows a return offer is genuinely different from a public-company one, and it is covered in Negotiating Your Offer.

Common questions