At Cloudera, we believe that data can make what is impossible today, possible tomorrow. We empower people to transform complex data into clear and actionable insights.
To that end, we deliver an Enterprise Data Cloud for any data, anywhere, from the Edge to AI. Powered by the relentless innovation of the open source community, Cloudera accelerates digital transformation for the world’s largest enterprises.
As a Software Engineering Intern at Cloudera you will:
-Be matched to a team aligned with your interests and skillset
-Work on a meaningful project that will have an impact within the company
-Meet, work and cross-collaborate with teams across the organization
-Participate in fun events including Fireside Chats with execs, tech talks, and competitive games
-Experience working on large-scale distributed systems
-Excitement about and experience in contributing to open source projects
-Solid understanding of TCP/IP, Network Programming and Operating Systems
- Great Team -- We’re a tight-knit team of talented engineers that really enjoy working together on challenging problems. Cloudera engineering also includes many of the top luminaries in Hadoop and related open source communities. We frequently interact with the research community, collaborate with engineers at other top companies and host cutting edge researchers for tech talks.
- Open Source -- We contribute to and deliver an open-source platform, composed primarily of Apache Software Foundation projects. Most of our developers are either Apache committers or on the road to becoming one.
- Innovative work - Cloudera pushes the frontier of big data and distributed computing, as our track record shows. We test and deploy our code on clusters with hundreds of nodes, terabytes of RAM, and petabytes of storage. We work on high-profile open-source projects, interacting daily with engineers at other exciting companies, speaking at meet-ups, etc.
-Must be currently enrolled in college, boot camp or have related work experience (possible full-time conversion after the program)
-A basic foundation in systems software, algorithms, data structures, and object-oriented design skills
-Fluency in one of the following languages (Java, C++, or Python).
-Knowledge of UNIX/Linux or Windows environments and APIs
A sample interview loop might include:
Recruiter screening call or meeting. The recruiter screens for general role fit, and fact-finds to prepare the rest of the loop. (This could instead be done by a hiring manager, especially if the company doesn’t have recruiters.)
Technical phone screen. A phone conversation tests for core skills, typically basic programming or technical concepts. (Some companies may conduct two phone screens to gather more signal, or so a second interviewer can offer perspective.)
Take-home evaluation. This is a variant of the basic skills screen that may take the form of an online challenge or simpler take-home test. (Many companies skip this.)
Onsite interviews. These typically extend half or most of a day and include three to six interviews in several formats, covering:
a. in-person coding questions
b. non-coding technical questions
c. behavioral questions
d. wrap-up conversation with the hiring manager that includes questions, concerns, or loose ends, and sets expectations on next steps
e. some kind of social event, like lunch with the team.
Interviewer feedback. Each interviewer offers written feedback on the candidate, and/or discussion among the interviewing panel.
Post-interview follow-ups. Calls, meetings, and possibly second onsite visits allow the hiring team to assess anything not yet covered or to gather more signal on something interviewers disagree about.
Reference checks. The hiring manager or interviewers call past employers and colleagues to verify aspects of the candidate’s experience.
Decision. The company gives either a rejection or an offer. An offer leads to an acceptance or rejection by the candidate.