You are reading a paid post from my newsletter — The Art of Doing Technical Program Management. I write with an aim to demystify the art of technical program management and deliver proven real-world strategies, practical advise and tips, and actionable frameworks to help you level up as a Technical Program Manager.
If you already are a subscriber and found this essay helpful, please share it with your colleagues and network. I am sure others might find it useful as well.
What and why to design a TPM career
Most careers in technology are not designed.
They simply unfold.
We take the job that seems interesting at the time, work hard, gain experience, and trust that the next opportunity will appear when we need it. For a long time, that approach worked reasonably well for everyone especially Technical Program Managers. Companies were growing, programs were becoming more complex, and TPM roles naturally expanded alongside them.
But over the past year, many conversations I’ve had with fellow TPMs have started to sound different.
Some are experienced TPMs trying to figure out their next move in a market that suddenly feels smaller. Others are TPMs who were recently laid off and struggling to land their next role. And some are early in their careers asking a question that didn’t feel urgent just a few years ago: Is TPM actually a long-term career?
Layer on top of that the rise of AI tools, shifting expectations inside engineering organizations, and companies reconsidering the structure of program management roles, and it’s understandable why many TPMs are feeling uncertain.
These are uncomfortable questions. But they are also useful ones.
Because when the environment around you becomes uncertain, it forces you to think more intentionally about something many of us previously left to chance: How your career is actually designed.
This post is my attempt to share how I think about designing a TPM career; not as a rigid framework or step-by-step playbook, but as a set of questions that helped me better understand my own path.
-
What Does a Fulfilling TPM Career Look Like for You?
-
Do You Want to Be an Individual Contributor or a People Manager?
-
Do You Actually Enjoy Ambiguity or Do You Just Tolerate It?
-
Do You Want to Be a Generalist or a Specialist?
-
What Size Problems Do You Want to Work On?
-
What Career Taxes Are You Willing to Pay?
-
Why Would Someone Hire You in an AI-Native World?
-
If the TPM Title Disappeared Tomorrow, What Roles Could You Step Into?
-
What Kind of Recognition Actually Matters to You?
-
What Kind of Career Regret Are You Trying to Avoid?
-
What Do You Want People to Say When a Tough Program Appears?
-
Bonus: Three Career Traps Many TPMs Fall Into
Think of what follows less as advice and more as a guided reflection. Now, let me walk you through what each of these questions hold in terms of key to your career.
How Should You Use These Questions?
The questions in this post are not meant to be skimmed quickly or answered in your head while reading. Their real value comes from slowing down and reflecting on them honestly.
-
If possible, write your answers down, even if they feel incomplete or messy at first.
-
Treat these questions less like a checklist and more like prompts for a conversation with yourself about the kind of career you want to build.
-
The goal is not to arrive at perfect answers immediately. The goal is clarity. Clarity about what energizes you, what tradeoffs you are willing to make, and what kind of reputation you want to build over time.
-
Once you have that clarity, these answers become something much more useful: a personal decision-making framework.
-
Whenever a new role, opportunity, or career move appears, you can use that framework to ask whether it actually aligns with the career you want to design.
Careers rarely unfold in straight lines. But having a framework for how you think about your career makes navigating those twists far more intentional.
Lets get started…
What Does a Fulfilling TPM Career Look Like for You?
Before thinking about promotions, companies, or titles, it’s worth asking a deeper question:
What does a fulfilling TPM career actually look like for you?
For some TPMs, fulfillment comes from operating in deeply ambiguous environments, working on cutting-edge technology, navigating messy cross-functional problems, and bringing clarity where none exists. For others, fulfillment comes from building and nurturing teams of TPMs while shaping how organizations operate.
For many people, the answer is unclear, especially early in their careers.
Our definition of fulfillment evolves over time. It is shaped by the companies we work at, the teams we collaborate with, and the tradeoffs we make as our lives outside of work change.
For me, a fulfilling TPM career looks something like this: working on complex cross-functional programs at the frontier of technology, surrounded by smart collaborators, where my impact comes from bringing clarity to chaos. At the same time, I want that work to coexist with the rest of my life, particularly the time I get to spend with my family.
That is my answer. Yours may look very different.
➡️ But even attempting to define it will anchor many of the decisions you make later.
Do You Want to Be an Individual Contributor or a People Manager?
Early in my career, I assumed that the only path forward was people management.
Promotions seemed to reinforce that idea. The organizational ladder appeared to move naturally from individual contributor to manager to senior leader.
But over time, I realized something important: people management is not simply the next level of the same job. It is a fundamentally different job.
Managing people means your primary source of satisfaction comes from growing individuals, mentoring TPMs, shaping careers, and building strong teams. Running programs becomes secondary.
For some people, that shift is incredibly fulfilling.
For me, the moments that feel most meaningful are when we ship something incredibly hard, when a complex initiative that once seemed impossible finally lands and changes the trajectory of a company.
Because of that, I’ve consciously chosen to remain on the individual contributor path while seeking roles with increasing scope and influence.
➡️ For many TPMs, this is the first real fork in the road.
Do You Actually Enjoy Ambiguity or Do You Just Tolerate It?
As you get higher in your career, the programs you work on become increasingly unclear.
-
Product requirements are incomplete.
-
Technical solutions are still evolving.
-
Stakeholders disagree about priorities.
-
Decisions are rarely straightforward.
Many TPMs say they thrive in chaos. But it’s worth asking a more honest question: do you truly enjoy that chaos, or have you simply learned how to tolerate it?
For some TPMs, ambiguity is energizing. It creates space to experiment, improvise, and find new ways to achieve impact.
For others, constant uncertainty becomes exhausting. The firefighting makes it difficult to see a clear sense of progress or growth.
Personally, the surge of energy I get from working on zero-to-one programs with unclear boundaries is intoxicating. Those are the moments where I feel I can contribute the most.
➡️ Looking back, it’s not surprising that many of the roles I’ve chosen have lived in those environments. You have to decide your happy place for yourself.
Hey, Its Aadil with a quick announcement.
I have launched my first new on-demand TPM Course right here on this newsletter — “Foundations Of Technical Program Management”.
📣 Subscribe to my new “On Demand Course” annual subscription (not the regular annual subscription which is different) and unlock my highly rated Maven course content + FREE access to all future courses.
🔥 50+ TPMs have taken the course live. Some used it to level up their TPM game while others used the content to MOVE INTO a TPM role.
In the modern AI world, the foundations of TPM role will be the key difference between churning AI slop or becoming an impactful AI native TPM.
💪🏽 Unlock your full TPM potential today!
Now, let’s keep going with this post. Thanks for reading.
Do You Want to Be a Generalist or a Specialist?
Many TPMs operate as generalists, moving across teams, products, and domains to create clarity across a vast landscape of dependencies.
Others prefer deep specialization, becoming experts in a particular technical domain such as infrastructure, machine learning systems, hardware, or security.