3 ms·
The split between VPE and CTO is that a VPE is operational and internal-facing whereas a CTO is strategic and external-facing. Neither role involves coding if y
by jandrewrogers 9y ago
The split between VPE and CTO is that a VPE is operational and internal-facing whereas a CTO is strategic and external-facing. Neither role involves coding if your company has a dozen engineers; senior individual contributors usually have a title like Chief Scientist or Distinguished Engineer.
A CTO role is essentially that of a Technical Product Manager. What distinguishes it from a traditional TPM is that, to do the role well, you also take on the aspect of being the technical "moral authority" for the company, setting the de facto engineering culture, and creating a compelling vision that goes beyond product management.
- taurath 9y agoI've seen it where they hire almost 80% junior programmers and have the CTO set the tone and pace and learning environment. It worked pretty well actually, but the core technology wasn't groundbreaking, more of a relationship based business doing complex CRUD.
- AznHisoka 9y agoall the rules go out the window if you are just building a CRUD app. i have seen non technical founders outsource everything to third world countries and still be successful.
- catwell 9y agoNobody has the same definition for the CTO / VPE split. If I search "CTO VP Engineering" on Google the first result is https://www.ivyexec.com/executive-insights/2015/cto-versus-vp-engineering-whats-the-difference/ https://www.ivyexec.com/executive-insights/2015/cto-versus-v... which defines the CTO as someone in charge of a small team doing "technical exploration". At other companies that role would be something like "Head of Research". Maybe it is time we stop using those titles. I personally saw that confusion cause serious issues at at least two companies.