From reverse-engineering malware to reverse-engineering bad products — I made the switch.
I started as a Software Engineer in Cybersecurity, spending years deep in code, vulnerabilities, and system architecture. Then something clicked: the hardest problems aren't always technical — they're about people, decisions, and building things that actually matter.
So I crossed over. Now I live at the intersection of APIs · Business · Data · UX, connecting the dots to ship products that work in the real world.
Product Management — Translating messy problems into clear roadmaps and shipped features API Strategy — Thinking in systems, integrations, and developer experience Data-Informed Decisions — Letting numbers challenge assumptions, not just confirm them UX Thinking — Because the best security is one users don't need to think about Cybersecurity Background — Still haunts me (in a good way) when reviewing architecture decisions
Software Engineer (Code) → Cybersecurity Engineer (Defense) → Product Manager (Strategy)
Security taught me to think adversarially. Engineering taught me to think in systems. Product taught me to think in outcomes.
LayerTools & Concepts🔌 APIREST · GraphQL · Webhooks · OpenAPI📊 DataSQL · Analytics · Funnels · Cohorts🎨 UXUser flows · Wireframes · Jobs-to-be-done🔒 SecurityThreat modeling · Auth · Zero Trust
📌 What You'll Find Here
Mybe Nothing for public but my private is full of Repos, experiments " MVPs, and notes from the overlap between product thinking and technical execution. No fluff. Just things I've actually worked on or learned from.
I'm always up for conversations about product strategy, API design, cybersecurity UX, or career pivots.