There is no one path to becoming a Chief Technical Officer (CTO) or Senior Vice President (SVP). Case in point, I'm just about to take a CTO position and my personal history looks like this: BA in English, then BA in Business Organization, MA in English, PhD in English with 18 years in development and project management concurrently with those latter degrees, and I haven't even sat for my PMP certification exam yet.
So, while your degrees will provide you with a great foundation of knowledge to perform well in your jobs, don't think they're automatic qualifiers. You must still do something with that knowledge, over time. Usually a lot of time.
One of those things is to gather enough experiences over time to be able to bring together a deep knowledge of business with a deep knowledge of technology, because as an executive position in a company, the person will be driving the technological strategy in order to align with overall business goals both now and into the future.
In general, I like to use Peter Kretzman's short post "Career tips for the CTO/CIO path" because it highlights the non-specific steps along the way, such as:
- Get broad (gather a LOT of related knowledge, either formally or
- Get mentored (there are experts inside and outside your company: find
- Get involved (in internal and external areas of the business)
- Keep up ("It’s a fire hose out there, trained at your eyeball." is my
favorite line. Take a look at answers to "What magazine / journal /
paper would you subscribe?" for how some people here at PM SE
stay informed in at least a few areas of their jobs)
Whatever the path you take, just keep moving it forward -- including failing forward (making mistakes and learning from them)!