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
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.
The initial recruiter call included 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 differen
One phone interview plus six onsite. The phone interview was just a discussion of past projects. The onsite consisted of: * Three programming interviews * One lunch * One discussion Overall, the company's atmosphere appeared lifeless and dull. Th
One of the best interview experiences I had. The whole process was smoothly organized. It started with a technical phone screen that tested your basic DS knowledge. The final on-site consisted of 6 rounds of interviews, each 1 hour long. Everyone wa
The initial recruiter call included 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 differen
One phone interview plus six onsite. The phone interview was just a discussion of past projects. The onsite consisted of: * Three programming interviews * One lunch * One discussion Overall, the company's atmosphere appeared lifeless and dull. Th
One of the best interview experiences I had. The whole process was smoothly organized. It started with a technical phone screen that tested your basic DS knowledge. The final on-site consisted of 6 rounds of interviews, each 1 hour long. Everyone wa