- Work/Life Balance
- Culture & Values
- Career Opportunities
- Comp & Benefits
- Senior Management
I have been working at Cloudera full-time (More than a year)
- Face paced, execution focused culture with a huge dose of humanity
- Intelligent, experienced co-workers, many of whom have long tenures and believe in the tech/long-term prospects of the company
- Management and colleagues care about your overall work experience and career progression
- Lot's of challenging problems to work when you're trying to make an open source software business with a complex product work at scale
Bottom line: people are respectful of your time and life and aren't political. It's a high energy atmosphere where you wake up excited to go to work.
- Scaling an open-source software business based on support is difficult.
- A merger is highly disruptive so it takes time to get back into execution mode. I would say we've been through the worst of this for 2 months and it's definitely showing.
- Dealing with general pessimism from outside analysts and a low stock price isn't for everyone.
- Still not a huge organization by some standards so it's not a place to get "lost" in the mix. It's very much all hands on deck.
Advice to Management
This is complex stuff, it's easier for people to feel nervous when they don't fully understand the tech/use cases/value. I think robust education around product (especially CDP) for the rank and file would be helpful. $750M in revenue = massive value creation. I think it's easy for that to get lost on people when the stock price is low.
I applied through a recruiter. I interviewed at Cloudera (San Francisco, CA (US)) in March 2018.
The initial recruiter call includes standard questions about my work experience and what I am looking for in my next role. I was puzzled when the recruiter mentioned that I did not have enterprise software experience (which I did, but with a different vendor than what they were looking for) and was skeptical that I fit the job position. Anyway, they decided to move forward with the technical phone interview.
The technical phone interview was rather unpleasant. The interviewer called in 5 minutes late. We also experienced technical difficulty setting up the collaborative coding tool. After a few minutes resolving this issue, I finally got the chance to type in my solution. I explained my approach and provided examples to test my code. The code ran fine with my test cases. However, the interviewer seemed dissatisfied with my solution, saying it was wrong, but was unable to point out why my logic was wrong nor provide counter-examples to fail my code. Time ran out, and I was left with the conclusion that they would not move forward with the process, and the impression that the interviewer was not knowledgable about the interview question he's asking.