I'm drawn to products where reliability, adoption, and day-to-day operations are tightly connected. I like finding the friction that keeps showing up, understanding why it happens, and helping teams fix it in a way that actually holds up in real use.
Build-side foundation
Building software taught me what vague decisions really cost.
Working on front-end delivery and API-related implementation made one thing obvious early: when product intent is fuzzy, teams lose time, scope drifts, and avoidable rework piles up. That pushed me toward clearer problem framing and better decisions.
User proximity
Support work taught me to pay attention to patterns, not just requests.
Talking to users every day made it easier to separate one-off opinions from repeated pain. I kept seeing the same confusion, broken expectations, and workflow issues come back again and again.
Operational discipline
IT support made reliability and usability feel very concrete.
When internal teams depend on a system to do their jobs, unclear workflows and fragile tools become expensive fast. That experience made me care deeply about continuity, adoption, and how products behave under real pressure.
Product ownership
Product management is where those experiences came together.
Today I use that background to run discovery, shape priorities, define success metrics, and work closely with engineering and stakeholders to ship improvements that solve real problems.