I applied through a recruiter. The process took 1 week. I interviewed at Bloomberg (New Brunswick, NJ) in Feb 2022
Interview
Very Difficult to understand coding puzzles not found on Leetcode or any other Algo & DS site. Interviewers were nice and professional. Still questions were very difficult for any Sr developer, including them, to answer during an interview. These interviews have the same Big-Tech pattern of a high filtration process that kicks out a lot of good candidates for the certainty of hiring the right one. Honestly, unless you have all the free time in the world, its a low low hit ratio and a crap shoot. Better off spending your interviewing efforts elsewhere.
Interview questions [1]
Question 1
1) Identify the parent child relationship among the following rows.
Parent row: any row which can be represented by summation of the consecutive rows following it.
(If the consecutive row is a Parent then it's children may be collapsed/skipped during summation.
2) Question 1: Given 4 random generated numbers from 1-10, write a program to decide whether it is
viable to use operations (limited in +, -, *, and /) on each and every number exactly once
to generate result 24.
Terrible communication. Got passed between 3 different recruiters all of whom gave specific dates for updates and blew past them. Descriptions of what would be covered in the interviews are wholly inaccurate (don’t bother reading the PDF they sent to “prep” you, almost none of it came up in any of the 3 interviews I did with them.)
Interviewers themselves were decent but clearly had exact “right” answers they were looking for. What’s the point of a leetcode question where there’s only one way to implement it? What’s the point of a system design interview where you’re having a candidate parse through a complex system that they clearly already know everything about and are just looking for 1-2 EXACT modifications to check off their boxes? Was there even a right answer? I genuinely don’t know what this company was looking for. Waste of time, waste of effort, waste of resources. Avoid, avoid, avoid
Interviewed with two separate teams. Coding rounds. Leet code style question. The interview went on for 1 hr. Waiting for the next steps. The seem to like link lists and arrays