The initial rounds involved two phone screens. These screens covered a mix of high-level questions about big data technologies and my experience, a few more specific technical questions about distributed computing concepts, and queries about my preferred working environments and how I collaborate in a team.
The final round featured more in-depth technical interviews. One focused primarily on a topic from my resume (ETL), while another assessed the depth of my understanding of core Hadoop technology. Other interviews were more general, focusing on my experience to date, my career aspirations, my interest in Cloudera, and answering my questions.
Every interviewer was friendly and helpful.
Advice from my recruiter proved valuable:
Cloudera aims to understand your depth and breadth of knowledge, but they don't expect you to be an expert in everything. Therefore, remain calm if you cannot answer a specific question.
How do I get new files into HDFS?
What's happening behind the scenes?
The following metrics were computed from 3 interview experiences for the Cloudera Solutions Architect role in New York, New York.
Cloudera's interview process for their Solutions Architect roles in New York, New York is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Cloudera's Solutions Architect interview process in New York, New York.