My first post covered the shape of my career: from web developer to machine learning engineer, team lead, technical project manager, and product manager. This one is about something more useful than the journey itself.
It is about the decisions I made, and what I would tell someone standing at the same crossroads I once stood at.
Whether you’re a developer, product manager, founder, entrepreneur, or community leader, your career will be shaped far more by the decisions you make than the titles you collect.
Twelve years is long enough to notice a pattern. Almost none of the moves that mattered were about titles or salaries. They were about what I chose to learn, what I chose to walk away from, and when I chose to stay and go deep instead of chasing the next thing.
Build Deep Expertise Before Expanding Your Career
Early on, I spent years as a developer before moving into project and product management. Sometimes it felt slow when I chose to get a new skill instead of double the salary or when I opted to work in a dynamic environment rather than a comfortable position. Everyone around me seemed to be climbing the ladder faster.
It was not slow. It was the foundation. Understanding what problems matter to solve and how to get to the solution, why technical debt accumulates, and why estimates go wrong isn’t something you can fully learn from books or online courses. It has to be lived once.
Teams often struggle not because they can’t build software, but because they start building before validating the problem.
The advice here is not “stay technical forever.” It is: do not skip the depth stage to chase a management title too early. A product manager who never built anything may struggle to earn the trust of team. A product manager who spent years building often earns that trust by asking one thoughtful question in the right meeting.
Depth builds credibility. Breadth multiplies it.
The Best Career Moves Rarely Look Safe
Every significant transition I made looked uncertain at the time. From engineering into product, from employment into freelance work on Toptal, from a stable role into a plugin used by millions of sites, None of those decisions came with guaranteed outcomes.
What they had in common was a gap between what I currently knew and what the role demanded. I took the roles that helped me polish skills along with contributing to a meaningful purpose.
If you are early in your career and choosing between a comfortable role and an uncomfortable one that teaches you more, the discomfort is usually the better investment.
Comfort compounds slowly. Discomfort compounds fast.
The same principle applies to founders. It is tempting to optimize for certainty, but successful products rarely emerge from perfect plans. They emerge from informed experimentation and the willingness to learn quickly.
Staying Relevant Isn’t About Chasing Every Trend
Across twelve years, the tools changed constantly. Frameworks came and went. Cloud transformed infrastructure. Machine learning became practical. Now AI is reshaping how software is built. I did not stay relevant by learning every new thing that appeared. I stayed relevant by keeping one habit constant:
I kept building. Sometimes for work. Sometimes through experiments. Sometimes through community projects and volunteering. Sometimes simply to learn.
That habit made AI-assisted development feel like an evolution rather than a disruption.
The tools around building continue to change. The practice of building does not.
For anyone worried about being left behind by AI or the next shift in tooling, the answer is rarely “learn this specific tool faster than everyone else.” It is “keep solving real problems”.
AI has dramatically lowered the cost of building software. It has not lowered the cost of making poor product decisions. Building the wrong feature faster is still building the wrong feature.
Community Was Never a Side Project
For most of these twelve years, communities has been a constant alongside my professional work.
Organizing WordPress meetups and WordCamps, leading the Toptal Pakistan community, co-founding the QAU CS Alumni Network, speaking at conferences, collaborating with contributors worldwide, mentoring professionals, and helping communities grow rarely earn prominent space on a resume/CV or become talking points in interviews. Yet those experiences have taught me more about leadership, stakeholder management, and building products than many traditional roles.
Community teaches a different kind of leadership. You learn to influence people who owe you nothing. You align people with different priorities. You build trust instead of relying on authority. You create environments where people contribute because they want to, not because they have to.
Those are the same skills required to lead product teams, align stakeholders, and navigate complex organizations.
The Questions Young Professionals Ask Never Really Change
The questions I hear most often sound familiar.
Should I specialize in this field or switch to another high demand skill? Should I choose this safe job or that challenging one? Am I falling behind compared to everyone else?
After twelve years, my answers remain consistent.
- Specialize first, broaden later. Depth gives you credibility. Breadth without depth often creates opinions that lack experience.
- Choose the role that teaches you more, provided you can afford the risk. Sometimes challenging problems develop better professionals than comfortable routines.
- Finally, stop measuring your progress against someone else’s timeline.
Careers are not races with a shared finish line.
What Actually Holds a Career Together
Looking back, I don’t think my career was built by a master plan. It was built by a series of deliberate decisions.
- Choosing learning over comfort.
- Choosing skill before title.
- Choosing customer problems over shiny features.
- Choosing communities over networking.
- Choosing long-term growth over short-term promotions.
These does not look like a win at times. but that helped me to stay relevant in an infinite game.
Closing Thoughts
The next decade will introduce technologies we cannot predict today. Some roles will disappear. New opportunities will emerge.
The decisions, however, will remain surprisingly familiar.
- Will you keep learning?
- Will you stay curious?
- Will you choose growth over comfort when the opportunity appears?
Titles may open doors. Decisions determine where those doors eventually lead.
Tahir Shahzad
Tahir Shahzad is a Product Manager, Product Owner, and technology consultant with over a decade of experience helping startups and organizations build products people actually use. If you are working on a product problem worth solving, reach him at tahirshahzad.com/contact/
