Entry-level Software Engineer Interview Experience
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.
- Technical interview
- Recruiter screen
- Final round
Interview tips
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.
Questions asked
Overview
I 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.
Question types asked
Specific questions asked
Why did you decide to do it that way?
I 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.
How would you build a system to process and connect user information?
What components would you include?
How would those components pass information between each other?
It 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.
What is your favorite language, and why Python?
Why Python compared to other languages?
Why not Java?
In what situations would you use Python, Java, and C?
I 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.
How big was your team, and how did you work with them?
He 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.
Get full access with a membership, or share your experience to try it free.
