Software Engineer Interview Experience - San Francisco, California
Process
I was contacted by a recruiter via email and subsequently had several conversations regarding possible positions. The recruiter was very professional and efficient.
I had the phone interview the following week and was notified that I passed two days later. I then had the onsite interview one week after that and received the results in three days. The overall process was very smooth and efficient.
Questions
Nothing particularly hard. Prepare well on data structures and algorithms, and prepare to write code on a whiteboard.
Was this helpful?
Interview Statistics
The following metrics were computed from 6 interview experiences for the Cloudera Software Engineer role in San Francisco, California.
Success Rate
Cloudera's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having mixed feelings for Cloudera's Software Engineer interview process in San Francisco, California.
Cloudera Work Experiences
- 4.0Great Wlb, No IssuesSoftware Engineer • Former EmployeeSan Francisco, California, United StatesApril 1, 2023Pros: Good WLB for this job.Cons: No complaints for the company.
- 1.0Shittiest Company to Work AtSoftware Engineer • Current EmployeeSan Francisco, California, United StatesDecember 22, 2022Pros: They observe a concept of "unplug days."Cons: They have absolutely zero vision for the product. They acquired two startups to pivot into public cloud from their on-prem business, yapped about it for a whole year, calling them the future of the company, only to lay them off after a year and stick with their on-prem customers. They are planning for a slow death.
- 3.0Good Work, Unfocused EngineeringSoftware Engineer • Former EmployeeSan Francisco, California, United StatesAugust 28, 2021Pros: Generally good working conditions, compensation, and coworkers. Lots of problems to work on for motivated people. Opportunities to contribute to open source. A lot of good parts of the tech stack you can work on or learn from. I'd recommend working here over many alternatives.Cons: Engineering's focus is split too much between products, components, cloud, on-prem, and multiple major versions. This always made it harder to execute on building a great product, but I think it got worse over time. Executives, support, and sales engineers can't keep up with everything, and it makes things harder.
Cloudera Interview Questions
