If you can't make it to CEO's select few, your daily role will be maintaining legacy systems. Legacy systems are written in classic ASP, VBScript and some JS. All business logic is in SQL stored procedures, finding the cause of a bug would be similar to finding a needle in a haystack. There is no architecture, it feels like it was developed on purpose to make you appreciate the OOP notion and higher level languages. Documentation is generally non-existent or out-dated, code is rarely commented. Whilst you are working on company's cash cow legacy systems, committing career suicide by dealing with long abandoned technologies, CEO's select few will be working on current tech stacks. However due to CEO's high standards, new product development will undergo lots of radical changes along the way, causing company to go in circles.