Bloomberg Entry-level Software Engineer Interview Experience
Bloomberg · Entry level · Software Engineer
I went into the hiring manager round thinking it would be another chill recruiter-style conversation, and instead I got hit with system design, language tradeoffs, and object-oriented follow-ups. That was easily the most surprising part of the whole loop.
Interview process
I interviewed for an entry-level Software Engineer role after applying through my university, and the whole process was fully virtual. I did not have any OA or HackerRank up front. My loop was two technical coding rounds, then a recruiter conversation, then a hiring manager final, although I heard some people get parts of that bundled into more of a superday depending on availability. The coding rounds were standard LeetCode-style questions and felt collaborative, but the hiring manager round surprised me because it was more technical than I expected and included system design and language tradeoff questions. The process moved pretty fast overall, and I made it through the final round but did not get the offer.
Interview rounds · 4
- 1
Technical round
CodingData Structures & AlgorithmsMy first round was a pretty standard coding screen in a shared editor, about 10 minutes of intro and then mostly LeetCode-style coding with a friendly interviewer who would nudge me if I missed something.
Q1. Given a crashed system of processes, how would you find the first process that failed and caused the rest to crash?
How they answeredI treated it like a graph or tree problem where I had to find the parent process that initiated the crash. I asked clarifying questions because they definitely wanted me to pull requirements out of them. My first approach was more like O(n^2), and then she pushed me to make it more efficient, which is when I tightened it up. It felt like an easy-medium or medium LeetCode problem, not a weird practical Bloomberg-specific one.
Follow-up questions- Do you have any clarifying questions about the process relationships and inputs?
- Can you make your solution more efficient?
Q2. How would you reverse a linked list?
How they answeredThis one was much simpler. We had already spent a lot of time on the graph question, so she mostly wanted me to explain the approach instead of fully coding it. I walked through it in pseudocode and explained the pointer updates. It was basically a standard reverse linked list question.
- 2
Technical round
CodingData Structures & AlgorithmsThe second technical was another coding round, but this one got harder as it went because the interviewer started with a simpler version and then added a constraint that forced me to rethink the whole approach.
Q1. You have a lock with combinations. How would you find the combination that opens it?
How they answeredAt first I talked through a simpler brute-force style approach because he started with just the lock and rotations. The tricky part early was even thinking through how to model the rotations. Then he added dead ends, and that changed the problem a lot because I had to rethink my whole approach. That is when I realized it was basically Open the Lock and a BFS problem, where I skip banned states and explore the next valid combinations.
Follow-up questions- What if some combinations are dead ends, and if you hit one you cannot continue from there?
- 3
Recruiter screen
BehavioralProject DiscussionThe recruiter round was the easiest and most conversational part of the process, probably around 30 minutes, and it felt more like a personality and fit check than an interrogation.
Q1. What attracted you to Bloomberg?
How they answeredShe added more color on the environment and the different groups you can join there. It felt a little conversational, but they moved on pretty quickly.
Q2. Which experience on your resume prepared you best for this role?
How they answeredI talked through the experience on my resume that I felt lined up best with the role and why it prepared me. This part was pretty straightforward and not super deep. It felt like they mostly wanted to hear that I could connect what I had already done to entry-level software engineering work.
Q3. Tell me about a hard situation with a teammate, and how would you handle a problem with a coworker?
How they answeredThey asked the usual teamwork and conflict questions. I answered it in a STAR format and talked through how I would address the issue directly, work through it with the teammate, and think about when to escalate. It was very standard behavioral stuff, not adversarial at all.
Follow-up questions- Who would you go to, or what would you do if there was a problem with a coworker?
- 4
Final / onsite round
System DesignConceptBehavioralProject DiscussionI went into the hiring manager round expecting another chill fit conversation, but mine was noticeably more technical with a system design prompt, language tradeoffs, and deeper follow-ups on decisions I had made in past work.
Q1. Tell me about yourself and walk me through your experience.
How they answeredI gave my background and talked through my past experience, but unlike the recruiter round, he kept pushing on why I had made certain decisions. He seemed really focused on my thinking process, not just what I had done. The whole tone was, why did you choose that, what was your reasoning, and how do you make decisions technically.
Follow-up questions- Why did you decide to do it that way?
Q2. How would you build a system to process and connect user information?
How they answeredIt was something like designing a user-information processing system. It was finance-adjacent, but not a business or markets case study. I talked through how I would build it, how the pieces connect, and how information flows between components. It felt very object-oriented. This was the part that caught me off guard because I had expected a more behavioral hiring manager chat, so I was definitely less prepared here.
Follow-up questions- What components would you include?
- How would those components pass information between each other?
Q3. What is your favorite language, and why Python?
How they answeredI said Python because it is user-friendly and has a lot of libraries like NumPy. He immediately pushed on why not Java, so I had to compare them instead of just naming a favorite. We also got into C and when I would use each language depending on the situation. It definitely felt like he was testing whether I actually understood the tradeoffs behind the tools I say I like.
Follow-up questions- Why Python compared to other languages?
- Why not Java?
- In what situations would you use Python, Java, and C?
Q4. How big was your team, and how did you work with them?
How they answeredHe asked about my team size and how we split up work. I explained that we each had our own role and divided responsibilities across the team. He did not go super deep on conflict here. It was more about whether I could explain how I work with other people in a technical setting.
Tips from the candidate
I would tell a friend to really grind LeetCode for this one, especially medium and some harder questions, because the coding rounds are not freebies. After that, know your resume cold, especially your projects, what you used, and why you used it. I would also prep some basic system design and object-oriented programming because the hiring manager round can get more technical than you expect. If they ask why you chose something, have an actual reason ready, not just a buzzword answer.
Company culture
Bloomberg felt way more people-focused than a lot of other big companies I interviewed with. It did not feel like they were interviewing just for the sake of interviewing. They gave prep resources and workshops, the interviewers were warm, and even in coding rounds they would nudge me if I got stuck instead of just letting me die in silence. I also never had an OA with them, and from everything I heard it seemed like actual people were reviewing resumes. They were pretty clear that even though Bloomberg is known for finance, they really want candidates to see them as a tech company, and I never needed finance domain knowledge to get through the process.