A VP Eng is responsible for providing a human API to engineering the CEO can understand. Its all about creating predicability out of uncertainty, and if the CEO doesn't feel predicability coming out of engineering, that puts his job on the line.
Some CEO's just get it, some need Gnatt charts and resource allocations on slides, some just need to to speak with confidence and act like an alpha male, etc. In short, if you can figure out how he communicates, then you're likely to get along. If not, it's unlikely you're going to make a great API/interface - and that's ok. Better to let someone else take on the role than to be frustrated.
Although I hate to advocate this, having a CTO role is a nice way to vest for another 6-12months, relax a bit and start looking for new opportunities.
Help them find a good VP, if you like the person then maybe they can help run interference with the CEO and let you focus on the things you like. If you don't like the new VP, then it's really time to move on to a new company.
Some CEO's just get it, some need Gnatt charts and resource allocations on slides, some just need to to speak with confidence and act like an alpha male, etc. In short, if you can figure out how he communicates, then you're likely to get along. If not, it's unlikely you're going to make a great API/interface - and that's ok. Better to let someone else take on the role than to be frustrated.
Although I hate to advocate this, having a CTO role is a nice way to vest for another 6-12months, relax a bit and start looking for new opportunities.
Help them find a good VP, if you like the person then maybe they can help run interference with the CEO and let you focus on the things you like. If you don't like the new VP, then it's really time to move on to a new company.