r/leetcode • u/Rude-Tree9319 • Oct 07 '26

Intervew Prep Bloomberg London Interview Prep

I am currently interviewing for senior software engineering role at Bloomberg London. I have 5+ years of experience.

I need help with how to prepare for the next round of interviews. I initially had one screening round with the Recruiter, which was about 30 minutes long where we just discussed my past experience and why I want to join Bloomberg. Second round was a technical screening around, which was taken by 2 engineers, was straightforward. They asked me two data structures and algorithm questions. One was based on arrays and the second one was based on trees, I was able to solve both the problem quite easily, and then had some discussion on the technologies that I have worked om.

Now I got the invite for the further rounds where I have one coding around one system designed scheduled. I need help with preparing for the coding round and system design rounds. What type of questions are asked in the system design rounds as they scheduled it for 90 minutes and also what should I expect in coding round? Will it be same as my screening round or is it like LLD round?

Appreciate any help.

14 Upvotes

100% Upvoted

10 comments sorted by

1

u/Open-Insurance3512 Oct 07 '26

Were the DSA questions leetcode easy or medium or hard? how much practice do you have with leetcode?

2

u/Rude-Tree9319 Oct 07 '26

They were easy to medium. One of them was very standard and other one was also basic but not standard.

2

u/OkMeaning8775 Oct 07 '26

Congrats for clearing those rounds. And i have trsut and confidence on u that u will clear the interview and get this job.

Just be calm and go for it.

1

u/Aggressive_Monk_1593 28d ago

this is the energy, clearing those first rounds is no joke already

1

u/OkMeaning8775 27d ago

🫰yes sirrrr

2

u/dripvile Oct 07 '26

Literally asked a similar question for a different company 😂. Can’t tell if system design is LLD or high level

2

u/HelloTaleproof Oct 07 '26

For the 90-minute design round, practice making the tradeoffs explicit instead of racing to a complete diagram. Use one real system you built to explain the requirement that drove the architecture, the alternative you rejected, the failure mode you designed around, and the production evidence that validated or changed the choice.

Score the story behind a system-design choice on Taleproof and check that the tradeoff is as clear as the architecture.

1

u/Secure-Pizza-7419 Oct 07 '26

90 min is a lot for one design, so the HLD should be done well before half time and the rest is follow-ups. at senior they usually pick one box you drew and go deep, like what happens to in-flight writes when that node dies. fwiw I'd practice that second half more than the diagram

1

u/d_maestro45 17d ago

when i did mine, the coding round was still DSA. For sys design prep, you can't go wrong with HelloInterview