The process was straightforward. I gave my resume to an internal employee who forwarded it to their hiring manager. I was contacted within four days by a recruiter, who asked for my availability. She promptly rescheduled my appointment, and it had to be corrected the day before. The schedule changed a few times, but this is not unusual for a large company like Cloudera, where many different people have different scheduling conflicts.
My day consisted of four technical interviews, one lunch, one manager interview, and one HR interview.
I didn't get the sense that people were passionate about what they were doing. Again, this is not unusual for people in the enterprise field; they are creating products they personally don't use on an everyday basis. Additionally, the technical interviews were a mess: interviewers asked the same set of questions (similar recursion problems) repeatedly, leading to low technical coverage. One of the interviewers, who was the lead, asked irrelevant OS questions, seemingly to assert his superior knowledge.
In short, Cloudera is doing great things for the enterprise world, but it is a large company filled with corporate professionals, and things seem to move slowly, as expected. People are there for stability and the status quo.
They tend to be of a recursive nature, where you have to find all permutations of some problem. They're all the same class of questions.
The following metrics were computed from 17 interview experiences for the Cloudera Software Engineer role in Palo Alto, California.
Cloudera's interview process for their Software Engineer roles in Palo Alto, California is very selective, failing most engineers who go through it.
Candidates reported having negative feelings for Cloudera's Software Engineer interview process in Palo Alto, California.