If you have an upcoming Bloomberg interview for a software engineering role, this document is the collection of resources, questions. and tips that will most likely get you an offer.

Interviewing at Bloomberg

The interviewing process is pretty straightforward at Bloomberg:

Step 1

Apply online on their career website

< Resume />

Step 2

If they like your application, You will receive an email asking to schedule your phone interview

< One 45 min coding interview />

Step 3

If the initial interviewer gave you a positive feedback then you will be proceeded for the onsite interviews

< Generally two coding Interviews />

Step 4

System design Interview (depending on the experience)

Party

Voila, you got an offer! 🥳

https://open.spotify.com/embed/track/6CSLNGruNhqpb5zhfs5n3i?utm_source=generator

Beware: What to keep in mind? (Things that go wrong)

There are a few things I learned by getting reading tons of interview experiences on Leetcode and personally getting rejected at Interview.

Always code optimally!!

Don't waste their time and especially your time on brute force solutions (Just brief them about it - 30 secs)

Take fewer hints

Take zero if possible and only when if absolutely necessary (dead end situation)

Write neat and tidy code

Always think you have to get it merged in the production and people are ready to reject your PR.

Proper variable & function naming - absolutely avoid s, a, A or functions like solve, go)

Use the code space properly - cleaner if, for, while and function blocks.

Own your thoughts

If you have a solution in mind, you should be able to sing it like a song. Explain you thinking process (this is what they are interested in).

Take a moment, build the explanation in your head and tell them step by step - data structures involved, algorithm paradigm, time complexity and space complexity etc.

Interview Checklist

  1. Read back the question to your interviewer(s) so you all are on the same page.
  2. Clarify the situation, and you doubts and whether you should assume anything
  3. Things might have already started hitting your brain - so instead of uttering something not useful, think for a moment and form your explanation for the solution.
  4. Take them through your solution - each and everything - what data structure you are using and why? what is time and space complexity? Could you do better?
  5. Incorporate interviewer's feedback in your approach.
  6. After they are satisfied with your solution start coding.

Practice: Bloomberg Tagged Question

Untitled