My advantage isn't just what I've built — it's how I approach complex systems across domains.

I build systems that hold up under real-world complexity.

Most of my work has lived at the intersection of telecom platforms, supply chain and device lifecycle systems, and fraud detection and operational tooling.

These aren't clean environments. They involve multiple stakeholders, legacy constraints, and high scale with real financial impact. I focus on creating structure where there isn't any — designing platforms that simplify complexity without losing capability.

I train my ability to see systems through art.

Outside of product, I run a growing painting studio focused on detailed, large-scale work. Painting trains my ability to see structure, balance, and signal in ways that directly translate to system design.

That practice isn't separate from my product thinking — it directly influences how I design and evaluate systems.

I've built and sold products outside enterprise environments.

Through TextNinja and Motovate, I built a telematics-driven product, sold into fleet operators including large global organizations, and learned how products succeed — or fail — in real-world conditions.

This wasn't theoretical. I had to sell, deliver, and prove value in environments where behavior change mattered.

This gave me something most product roles don't: a direct understanding of the buyer, the operator, and the end user — at the same time.

I connect business, technology, and operations — and make them work together.

Across my work, I've consistently operated in the gaps: business intent to technical implementation, system capability to real-world usage, and strategy to execution.

• Integrating external systems like Apple GSX and eSIM provisioning flows
• Designing internal tools used by thousands of operators daily
• Translating ambiguous requirements into working, scalable systems