Pros
- Within the technical organization, the work was pretty easy. CPG inherited a product and stack from Code42 and just had to keep it from tipping over onto itself. - My team was fun to work with - Compensation was pretty good (initially) when the company was launched, because the market conditions necessitated it
Cons
- The product is centric to a model that is rapidly dying. "Documents that exist on people's laptops" and the need to back them up, is a model of operation that is rapidly dying in the current era of software. - The work was easy because the leadership teams had no idea what to do to grow the company and had more or less stopped trying. The full leadership team meets every morning and it is not uncommon for the day's direction to be changed based on that day's whims. - A private equity group that owned the company placed priority on acquisitions - and a company that was acquired performed almost a reverse takeover of the company. The new CTO used Crashplan's revenue to fund technical roadmap initiatives that solely benefitted his former employees in India, and proceeded to start drawing down technical employees in North America - Technical leadership was risk-averse to a fault. It was common that initiatives to streamline software operations were spiked because of lack of understanding, and perceived risk. - There was a lot of misplaced faith in some leaders who were demonstratably unequipped for the jobs they were tasked with (Product/Engineering/QA management) I would be shocked if Crashplan, as both a product and a company, were still a going concern in the same format in January 2027.