| layout | default |
|---|---|
| title | About |
| permalink | /about |
I didn't set out to become a Product Manager.
Like many people in tech, my career began with writing software. Back in 2006, I was fascinated by solving technical problems and building systems that people could rely on. Over the years, I grew into technical leadership and engineering management, working with teams, delivering software, and learning what it takes to build products at scale.
Somewhere along the way, my curiosity shifted.
I found myself spending less time thinking about how to build something and more time thinking about why we were building it. I enjoyed technical challenges, but I became increasingly interested in understanding customer problems, making trade-offs, and shaping the direction of a product.
That curiosity eventually led me into Product Management.
Today, I'm a Product Manager at ArmorCode, where I work on enterprise integrations, APIs, and platform capabilities for cybersecurity products. My engineering background still influences the way I approach product decisions. It helps me connect customer needs with technical realities and collaborate effectively across engineering, design, customer success, and leadership.
The topics that consistently capture my attention include:
- Enterprise integrations
- Platform products
- APIs and developer experience
- Cybersecurity
- Artificial Intelligence
- Product strategy
- Systems thinking
I enjoy learning how complex systems fit together, whether they're technical architectures, organizations, or products.
For a long time, most of my writing lived in notebooks or drafts that never went anywhere.
I wanted a place that was entirely my own. A place where I could slow down, think more deeply, and share ideas without worrying about algorithms or character limits.
This website is that place.
You'll find reflections on product management, enterprise software, AI, career growth, and the lessons I continue to learn along the way. Some posts will be practical. Others will simply be attempts to understand a problem a little better.
I don't expect to publish every week.
But when I do publish, I hope it's something worth your time.
If something here resonates with you, I'd be glad to continue the conversation. Feel free to connect with me on LinkedIn.