Had phone interviews with virtually every member of the team I would join, mostly ranging from 30 minutes to an hour each. The first interviews were mostly non-technical, but I had a series of 3 back to back to back phone interviews (each an hour in length) that were very in depth. One was purely about mathematics theory and statistics, one was about java programming technique, and the third was a more algorithmic problem that the interviewer and I went through in pseudo code.
Preguntas de entrevista [1]
Pregunta 1
The algorithm question was very difficult and required figuring out a grid search algorithm and analyzing its time complexity, and then various alternative implementations that would minimize data storage or the order of the algorithm.
Me postulé a través de una recomendación de un empleado. El proceso tomó 3 días. Acudí a una entrevista en Cloudera (Palo Alto, CA) en feb 2010
Entrevista
I interviewed with Cloudera in 2010 for a Software Engineering Internship position. The scheduling and efficiency of the organisation was exceptional - my initial interview was scheduled within 12 hours of emailing in my resume, and the following interviews were scheduled extremely fast as well.
As this was for an internship position - I was given the offer immediately after the second interview. The company was very fast and the interviewers gave very good and honest feedback. I requested to fly to Palo Alto and meet the team. This request was allowed, and I greatly enjoyed the process.
The recruiting process was substantially friendlier and more engaging than Facebook or Google, and on par with Palantir.
Preguntas de entrevista [1]
Pregunta 1
If you wanted to make a highly concurrent cache with a least recently used replacement policy, what data structures would you use? How would this scale per number of threads?
