Risk Management Solutions Software Engineer Interview Questions
& Process

So the whole thing took from November to March, mostly due to the company being really slow and missing our scheduled calls. The first step was a recruiter call, super basic. Then a 1-hour call with the hiring manager, who actually missed our first meeting and was 15 minutes late to the rescheduled one. It was mostly behavioral questions like 'tell me about a time...' and some poking at my resume experience, which was fine if you were honest on your resume. After that, they booked me for a 3-hour call with two engineers, which turned out to be two 1.5-hour algorithmic rounds. They didn't check my availability and gave zero info on what to expect. The interviewers also missed this call, so we rescheduled again. Those algorithmic rounds involved 4 medium-hard LeetCode questions from Meta's list, which I solved, but the interviewers seemed to struggle keeping up and explaining them. They took ages to explain each problem, calling them 'easy' when they weren't, and we spent ages going over test cases. Then, another 3-hour block was scheduled without my input. This one had 2 LeetCode questions (easier, with edge cases) and a Systems Design question (Design Netflix, covering user side and uploads, requiring solid fundamentals and communication). They offered me a job at the very bottom of the second salary range they posted, which was already lower than the initial range and felt insulting after the intense interviews and their own scheduling issues.

After applying on their website, a recruiter contacted me. We scheduled an interview, but they canceled it 30 minutes beforehand. I had another interview for a different position with them that was canceled 3 hours before it was supposed to start. My interviews were canceled twice by RMS in the same week. It was a complete waste of everyone's time.

So, it was a live coding thing where we shared screens. They threw a medium-level LeetCode problem at me, specifically about implementing depth first search in a 2D matrix. The whole thing was half an hour, and this coding part was the last 15 minutes of it.