A few people have asked me to try and define the perfect startup organization chart. I don’t believe that one exists. Every team configuration is different. But I do have more insight into understanding your startup team. This time I thought I’d try and address engineering talent. Often I’m asked by startup CEO’s about how to best build an engineering team. I have much experience in this domain.
Because more technology people probably read startup blogs I’m guessing this post will come under more scrutiny. The terms “CTO” and “VP Engineering” have such stigmas associated with what they are that I’m sure some people will feel uncomfortable with the definitions I’ve put forward. Still, I believe I’m offering an accurate representation of the ideal configuration of the main technology leaders.
This post is designed mostly for non-technical founders. I hope many will read this and have an answer for the question, “what’s the different between a CTO and a VP of Engineering?”
via www.bothsidesofthetable.com
This is a post well worth reading. Every technology company worth a damn has a CTO archetype even if they don't have the title itself. VP of Engineering on the other hand is an important though thankless task which can go unrecognised.
CTOs need a bit of Showmanship to communicate complex ideas to people who's only questions will be 'How much will this cost us?', the VP of Engineering on the other hand has to ensure those complex ideas are put into practice by a bunch of people who can be complex in their own way and can react poorly to displays of Showmanship.
When it comes to developing products you need both those oars in the water or you'll find you’re rowing in circles.
