I worked in a company where the VP of Engineering didn't report to the CTO. It made some sense because the CTO mostly directed the 6 months into the future visi

I worked in a company where the VP of Engineering didn't report to the CTO. It made some sense because the CTO mostly directed the 6 months into the future vision of the company (next features, next product). This worked ok because the CTO had a research team that reported to him and the VP of Engg had the development team reporting to him but it was not optimal. The issues we faced were: - CTO+Research team builds some amazing enhancements for the product but have to fight to get them into the next release (Dev claimed there was no time for regression testing..but next cycle there will be) - Dev team thought the research team were ivory tower elites (even though this was not the case). There were Ph.D.s and people who never went to college on the team. - Research team eventually thought they were superior (reaction to having all their input regularly ignored by dev team) In short, if your company has a legitimate need for a research or forward looking team, there may be a way to make this situation work, but not without regular political disputes and bitterness between teams. Try to find a way to have the VP report to you.