A recruiter reached out on LinkedIn, and I applied.
The screening round was held in the first week of December. It had two questions; I didn't feel they were too difficult, just very long. The interviewer was nice, and the key is to communicate and explain before diving into the problem.
I got a call the next day to schedule onsite interviews. One good thing is they schedule onsite interviews on two different days. If day one doesn't go well, they cancel the second day's interview, which is a time saver, to be honest.
For the virtual onsite, day one involved a graph question. I gave a brute-force solution, or what I could think of initially, with some observations. It required a hint from the interviewer. I took the hint, explained the optimized approach, and coded it.
The second interview on day one was system design. The key is to talk more and start from a basic system rather than going for something extravagant. They focused on REST endpoints, the database schema, and how to optimize searching in the system.
I got an email from the recruiter the next day stating the interviewers were pleased and wanted to continue with the second day's interview.
The second day's interview was with a senior manager and team lead; it was behavioral. I don't know what went wrong, but I received a rejection email from the recruiter the next day stating, "At this time, it doesn't feel like a match based on my skillset."
Something about the Sink Node.
Design Book Upload
The following metrics were computed from 100 interview experiences for the Bloomberg LP Senior Software Engineer role in New York, New York.
Bloomberg LP's interview process for their Senior Software Engineer roles in New York, New York is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Bloomberg LP's Senior Software Engineer interview process in New York, New York.