Andrews DeanFor years, the technology industry offered an unusually simple career promise. Start as a developer, analyst, tester, designer, or consultant. Learn the work. Become a lead, then a manager, then a senior manager. And if you stayed long enough and performed well enough, a Director, VP, CTO, or CPO title waited somewhere further up the ladder.
For many people who entered technology in the late 1990s or early 2000s, that promise worked remarkably well. But there was something unusual happening around them that we don't talk about enough: they weren't only climbing the ladder.
The ladder itself was growing.
I think that distinction matters more than we normally acknowledge.
The generation that grew with the industry
Imagine someone who entered software in 2001. Technology teams were considerably smaller than they are today. India's IT services industry was still expanding internationally, product companies were growing, outsourcing was accelerating, and new development centres were being created everywhere.
Then came twenty years of extraordinary expansion. A company with a few hundred technology employees became a company with several thousand. A team serving one geography became a global organisation. New offices appeared, new business units were created, new products required new leadership teams, and every time the organisation grew, another layer of senior positions came with it: a new delivery centre needed a Delivery Head, a new product division needed a VP, a new geography needed its own leadership, a larger engineering organisation needed Directors, and a growing technology function needed architects, program leaders, product heads, engineering heads, and eventually executives.
So the people who began their careers during that period accumulated experience while the number of senior opportunities around them was also increasing. That doesn't mean their promotions were undeserved. Far from it. But they had something working in their favour that the next generation may not have to the same extent: demographics. They were becoming senior inside an industry that desperately needed more senior people.
Now look at what is happening to the generation that followed them.
The 2008 generation is arriving
Think about someone who started working in technology around 2008 or 2010. They've now spent sixteen to twenty years in the industry, and there are a lot of them. Over the years, thousands of developers became senior developers, then leads, then managers, then senior managers. Business analysts became product managers, then senior product managers. Project managers became program managers. Delivery managers started running larger teams and accounts.
And naturally, many of those professionals now look upward: Director, Vice President, Head of Product, Head of Engineering, CTO, CPO, Business Unit Head.
The problem is mathematical. There simply cannot be an executive position for every experienced professional. Imagine a stadium where, over the years, we dramatically increased the number of people entering through the gates, but the VIP box never expanded at the same rate. Eventually a very large number of capable people arrive at the point where they expect to move upward, only to discover the number of seats above them is limited.
This might become one of the biggest career questions facing experienced technology professionals over the next decade.
The corporate pyramid has a limit
Organisations are pyramids for a reason. A company may need hundreds of engineers, dozens of engineering managers, ten Directors, perhaps three Vice Presidents, and one CTO. The higher you go, the fewer positions exist. That was always true. What's changing is the number of people arriving at those upper-middle levels at the same time.
For years, we treated the career ladder almost like an escalator: developer, lead, manager, senior manager, director, VP. Keep moving, keep gaining experience, keep collecting larger responsibilities, and eventually the next title arrives. That assumption is beginning to weaken. The future of a successful technology career may look much less like a straight ladder and much more like a collection of different paths.
The manager who only manages may face the hardest question
There's another force making this more complicated: AI.
Think about how much traditional management work revolves around information: status updates, meeting notes, project tracking, resource planning, reporting, documentation, follow-ups, summaries, dashboards, coordination, approvals, and presentations explaining what everyone else has been doing. For decades, organisations needed layers of people to gather, interpret, move, and communicate that information. Increasingly, software can do a meaningful portion of it.
That doesn't eliminate management. But it changes what good management is worth. A manager whose value comes from judgment, customer understanding, leadership, commercial thinking, technical awareness, decision-making, and developing people can remain enormously valuable. A manager whose primary role is moving information between people may find the next decade uncomfortable.
And this creates an important distinction: there's a difference between having twenty years of experience and having one year of experience repeated twenty times. That line may sound harsh, but I think it's going to matter.
Experience alone will not protect a career
Consider two professionals. Both started in 2010. Both have twenty years of experience by 2030.
The first person has spent the last seven years managing delivery: attending meetings, reviewing reports, escalating issues, tracking deadlines, managing a team, approving work. They're competent, and they know the organisation extremely well. But they've gradually moved further away from technology, customers, product decisions, and the actual creation of value.
Now consider the second person. They also manage. But they understand how AI is changing their work. They understand customers and can discuss product strategy. They understand enough technology to challenge technical decisions. They know the economics of the business, and they can work with senior executives and still sit with engineers and understand the problem being solved. They've built things, changed things, owned outcomes, taken difficult decisions.
Both CVs may say twenty years of experience. Their market value could be completely different.
Let me say the important part plainly: twenty years of experience will matter far less than what those twenty years have made you capable of doing. I think that will be one of the defining career principles of the next decade.
So where does everyone go?
This is where things get interesting. The obvious assumption is that if there aren't enough executive positions, experienced technology professionals face a bleak future. I don't think that's necessarily true. I think the definition of career success itself will change.
Some professionals will still become executives, running large engineering organisations, products, businesses, accounts, or technology functions. But many others will choose, or eventually need, different paths.
Some will become deep specialists: principal engineers, enterprise architects, cybersecurity experts, AI specialists, distinguished engineers, platform architects, people whose value comes from solving problems very few others can solve. Others will move closer to the business, owning revenue, customers, products, transformation programs, partnerships, or entire capabilities. Others may leave the traditional corporate ladder completely, through consulting, advisory work, fractional leadership, entrepreneurship, teaching, board roles, or independent products, or smaller companies where twenty years of experience can have far more influence than it might inside a company of 100,000 employees.
The second half of a technology career may therefore look very different from the first. And that might actually be a good thing.
Maybe the career ladder was always too narrow
There is something strange about how we have historically defined professional success. An excellent engineer eventually becomes a manager. An excellent manager eventually becomes a senior manager, then Director, then VP. Every step supposedly represents progress.
But what if someone doesn't want to manage 500 people? What if someone loves solving difficult technical problems more than managing the people who solve them? What if someone reaches a point where autonomy matters more than hierarchy? Our traditional career model often treats these choices as a lack of ambition. I suspect that will change.
A 48-year-old Principal Architect with extraordinary expertise may have a better career than a struggling Vice President whose days are consumed by internal meetings. A 50-year-old independent consultant working with four companies may have more freedom and income than someone chasing another corporate promotion. A former engineering leader may build a small AI company with ten people and create more value than they ever did managing hundreds.
The definition of "senior" may slowly separate from the definition of "manager." And that is probably overdue.
The future isn't necessarily worse
When I think about professionals who started their careers in the late 2000s, I don't think their future is worse than the generation before them. But I do think it will be less automatic.
The previous generation sometimes benefited from being experienced at exactly the moment the technology industry needed experienced people everywhere. The next generation is entering its senior years at a time when organisations may become flatter, AI may remove some coordination work, and thousands of equally experienced professionals will compete for a relatively small number of traditional executive positions.
That means waiting for the organisational chart to decide your career becomes dangerous. You have to decide what you are becoming: a business leader, a technology specialist, a product thinker, an AI leader, a commercial leader, a consultant, an entrepreneur, an advisor, or perhaps some combination of them.
The answer doesn't need to be decided at 35. But I think the question needs to be asked much earlier than most of us currently ask it, because eventually the corporate ladder narrows. And when it does, the strongest career position may belong to the person who doesn't need the next rung.
A different question for the second half
For the first ten or fifteen years of a career, asking this question makes sense: what position comes after this one? It gives you direction. You learn the skills required for the next role, take on larger responsibilities, and build credibility.
But somewhere around the middle of a career, the question needs to change. Instead of what title comes next, ask what am I becoming valuable enough to do next. Those two questions lead to very different careers. The first depends heavily on someone creating a position above you. The second creates options. And options may become the most valuable form of career security experienced technology professionals can build.
If you have already spent fifteen or twenty years in technology, perhaps the most important career decision isn't how to secure your next promotion. It is deciding what you want the next fifteen or twenty years of your professional life to be worth.
What does the second half of your technology career look like?