3 ms·
Not OP, but there are some common problems, assuming they were a non-founder CTO: - Instead of leading an eng team, maybe CTO meant "our entire tech team". -
by shimon 8y ago
Not OP, but there are some common problems, assuming they were a non-founder CTO:
- Instead of leading an eng team, maybe CTO meant "our entire tech team".
- Maybe the founders sucked, or had personal conflicts.
- Maybe the business was broken in ways a technologist can't fix.
- Maybe the business was viable but this individual did not enjoy being a part of it. Could be anything from "there are too many salespeople yelling into phones all around me" to "the technical problems were not the sort I am interested in / good at solving".
- rhymenoceros 8y agoIndeed. Also, non-founder CTOs often find themselves in the odd position of being responsible for success and delivery but not being able to influence overall company strategy, particularly in tech-focused companies. It's almost like being a second-class citizen of the leadership team. Not all companies are like this, but smaller ones that are looking for CTOs (whether due to founder splits or turnover) often are. The other thing that sometimes happens is when a CTO position is carved out for a company that is doing well but needs "maturity," typically due to missed deadlines/etc. This can be a pretty terrible experience unless this sort of thing floats your boat - a lot of the downsides of working for a large company, but still the risks of working for a small one.
- simonebrunozzi 8y agoMan, you're good! The two co-founders had personal conflicts; the business was broken, and never became viable. And a few other things...