There is a moment in every technologist’s career where the work stops being about the technology itself. You have built the thing, deployed the thing, automated the thing, written the blog about the thing. And yet, something nags at you. Not because the work is unfulfilling, but because a different question starts occupying your mind.
It is no longer “how do I build this?” It becomes “should we build this at all?”
This is the story of why I chose a career in Product Management.
In this blog series, I will walk you through core milestones, defeats, wins, and special moments that shaped my career; and quite frankly, shaped me as a person.
Starting with the WHY
If I had to pinpoint a defining moment in my career journey, it would be my bachelor’s thesis. I chose VMware ESXi as part of the software stack for my lab. It was a technical decision at the time, nothing more. But that decision introduced me to virtualization, which led me to infrastructure, which led me to storage, which eventually led me to Pure Storage. Every career is a chain of small decisions that only make sense in hindsight, and that thesis was my first link.
My first job was with a Value-Added Reseller as a Field Systems Engineer. I racked hardware, configured DR solutions, built clustered and virtualized environments across different vendors. It was hands-on, physical, and deeply satisfying. I got promoted to Solution Architect, a role I held for four years, where I learned to see the bigger picture: how different technologies fit together, how to design for a customer’s actual needs rather than just their stated requirements, and how to present a solution that makes sense to both the technical team and the decision-makers.
After a transformative year pursuing my MSc in Computer Science at Newcastle University, I received an opportunity to join Pure Storage. They were building a new Cloud Product Specialist team at their Prague R&D office, and the chance to contribute to something innovative was impossible to pass up.
The Gravitational Pull Toward Product
At Pure Storage, I started as a Cloud Solutions Engineer, serving as the technical authority for Pure Cloud Block Store across AWS and Azure. I loved the work. I was designing hybrid cloud architectures, pioneering integration patterns with native cloud services, and building enablement programs for field teams and partners across EMEA.
But something was shifting.
I found myself spending less time on the “how” and more time on the “what” and “why.” When I collaborated with engineering teams, I was not just asking how a feature worked. I was asking why we were building it, who it was for, and whether it was the right thing to build in the first place. When I spoke with customers at conferences and meetups, I was not just answering their technical questions. I was listening to their pain points, mapping patterns across conversations, and thinking about what our product should do next.
I did not realize it at the time, but I was already doing product management. I just did not have the title.
The Community as a Catalyst
One of the most unexpected catalysts in my move to PM was community involvement. As a VMware vExpert and AWS Community Builder, I had the privilege of speaking at conferences, writing technical blogs, and engaging with practitioners who were using our products daily.
In 2023, I delivered five sessions in three days at VMware Explore Barcelona. That experience was exhausting, exhilarating, and deeply formative. Not because of the presentations themselves, but because of what happened between them. The hallway conversations. The coffee chats. The candid feedback from users who told me what worked, what did not, and what they wished our product could do.
That same year, I participated in the Veeam Community Hackathon and our team won first place by building a PowerShell SDK for Veeam Backup & Replication’s REST API. The hackathon was a reminder of something important: the best ideas come from understanding a real problem deeply enough that the solution feels obvious.
These experiences gave me a front-row seat to what customers truly need. And they made me realize that I wanted to be closer to the product: not just explaining it or integrating it, but shaping it.
The Leap
The transition from Senior Technical Product Specialist to Senior Product Manager was not a clean break. It was a gradual evolution, and honestly, that is what made it work. My technical background was not something I had to leave behind. It became the foundation I built on.
As a PM, I suddenly had to think about user experience, business cases, competitive positioning, and go-to-market strategies. I had to write PRDs instead of reference architectures. I had to prioritize features instead of building them. I had to say “no” to ideas I personally found exciting because the data said something different.
It was uncomfortable. It was humbling. And it was exactly what I needed.
What PM Means to Me Today
A year later, I have noticed a shift in what I seek as rewards in my day-to-day work. It is no longer about just delivering projects or ticking tasks off a list. It is about the human impact.
The moments that truly bring me joy are when I know I have made someone’s day a little easier. Whether it is simplifying a process, solving a tough challenge, or offering clarity in a complex discussion. I also find deep satisfaction in turning ideas into innovations, especially when it means challenging the status quo. There is something deeply rewarding about taking an idea from a spark of inspiration, nurturing it, and watching it evolve into something tangible that creates real value.
Many people think product management is all about building features or managing backlogs. What they might not realize is that it is equally about storytelling and decision-making. A significant part of my role is translating complex analytics and technical details into clear, compelling narratives that resonate with different audiences, whether it is engineers, executives, or customers.
That is the part no one tells you about when you are considering PM as a career. The job is not about having the best ideas. It is about creating the conditions for the best ideas to emerge, and then having the conviction to see them through.
So, Why Product Management?
Because after 10 years in tech, after racking servers, writing Terraform modules, speaking at conferences, and winning hackathons, I found that the work I cared about most was not the building. It was the deciding. The understanding. The connecting of problems with thoughtful solutions.
Product Management is not a departure from my engineering roots. It is the natural evolution of them. Every architecture I designed, every customer I spoke with, every blog I wrote prepared me for this role in ways I could not have predicted.
If you are an engineer or a technologist wondering whether PM is right for you, here is my honest take: the technical skills will give you credibility. The customer empathy will give you direction. But the thing that will make you a good PM is the willingness to stop being the person with all the answers and start being the person who asks the right questions.
That is the journey I am on. And this blog series is my attempt to share it, one chapter at a time.
Thank you for reading. If you have any questions or want to share your own experiences, feel free to reach out on LinkedIn.
comments powered by Disqus