About
I am a technology executive and infrastructure leader with 19 years of experience building and operating enterprise and global environments.
My work sits at the intersection of deep technical execution and operational leadership. I have designed, operated, and supported large-scale LAN, WAN, SD-WAN, and Wireless infrastructures across hundreds of sites, often acting as a senior escalation point during critical incidents.
I am particularly interested in how networks behave in the real world — under latency, loss, scale, organizational constraints, and imperfect conditions. I focus on performance analysis, observability, troubleshooting, and building systems that are resilient, understandable, and operable over time.
Beyond hands-on engineering, I bring an entrepreneurial mindset to infrastructure. I treat systems as products, value clarity over complexity, and invest heavily in documentation, automation, and repeatable processes that enable teams to operate effectively.
Today, I am focused on roles and projects where technical depth, ownership, and long-term thinking matter.
How I Think
Tools change. Technologies evolve. What remains constant is how problems are approached.
I approach network engineering as a system, not a collection of isolated components.
When facing a problem, I prioritize understanding impact before jumping to solutions. I look for signals, patterns, and constraints, using metrics and observability to guide decisions rather than assumptions.
Incident response, for me, is not about heroics. It is about structured thinking: detect early, isolate accurately, validate hypotheses, act deliberately, and always close the loop with learning and improvement.
I strongly believe that good engineering is defined not only by how systems work when everything is ideal, but by how they fail, how they recover, and how understandable they are to the people operating them.
- Metrics before opinions
- Trade-offs over best practices
- Systems over quick fixes
- Clarity enables scale