Taro Logo

Losing some sheen the last couple of years

Software Engineer
Current Employee
Has worked at Cloudera for less than 1 year
October 2, 2015
San Francisco, California
3.0
Doesn't RecommendPositive OutlookApproves of CEO
Pros

Smart Team of Engineers Interesting Problems 'Big Data' interest/demand seems to be on the rise in the industry Great office perks Wednesday no-meeting / WFH day

Cons

Lots of good people leaving – right after they hit the 4-year mark.

Setting sights to compete with Teradata, etc., means reduced focus on other things that Hadoop has tons of potential for.

Skewed investments favor certain teams, while some teams are left without adequate resources.

Marketing talks about being a Hadoop company, but the focus lately has been on customer lock-in with a proprietary Management Layer and pushing Impala (which is not really a bad thing, maybe, since it's a differentiator) and new tech that does nothing to extend the Hadoop ecosystem anyway.

Don't really have adequately differentiating/better technology (which cannot be replicated by competitors easily) to warrant not going IPO for this long.

Hortonworks is grabbing more developer mind share, and MapR has a substitute for HDFS that justifies its proprietary license by simply being more reliable and faster.

Engineering cycles are wasted on irrelevant initiatives that don't really push the product forward.

Was this helpful?

Cloudera Interview Experiences