The recruiter was flexible and easy to work with. After going past the coding challenge, a phone screen was set up with an engineer from the team. The engineer showed up to the call about 20 minutes late and apologized for being held up in another meeting. I made it a point to convey that I had another meeting after the call, so I couldn't run late, and he seemed understanding.
The interview question itself consisted of a string problem, which I solved in a straightforward manner using recursion and included unit test cases as well. It was all pretty no-nonsense. The interviewer, however, seemed unprepared, as he was not aware of my background and pulled up my resume five minutes before my next meeting to talk about it. I had an abrupt ending to the interview due to my hard stop but was satisfied with my response to the technical portion of the interview.
I received an automated email from "recruiting" stating that they would not be moving forward with the process. They seem like a great company, but it would mean a great deal if the recruiting team had a slightly more personal touch when getting back to candidates with feedback, especially if rejecting over seemingly innocuous things.
The following metrics were computed from 6 interview experiences for the Cloudera Software Engineer role in San Francisco, California.
Cloudera's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Cloudera's Software Engineer interview process in San Francisco, California.