Skip to content

Architecture Practice & Leadership

My architecture work extends beyond individual designs. I also contribute through standards, technical evaluation, cross-domain decision-making, automation enablement, mentoring, and the creation of reusable patterns that help other teams work more consistently.

These examples span multiple roles and stages of my architecture career and are selected for the architectural patterns they demonstrate rather than recency.

Selected Architecture Contributions

  • Led SD-WAN vendor evaluations and architecture design across multiple enterprises, providing C-level recommendations that balanced performance, cost, operational requirements, and roadmap alignment.

  • Integrated Secure Service Edge (SSE) into cloud and remote-access strategies using Zscaler, aligning security policy with distributed access models.

  • Authored AWS and Azure cloud networking reference architectures that provided reusable VPC/VNet patterns for Solutions Architects and application teams.

  • Designed resilient VPN architectures across on-premises, cloud, and remote-access environments, including active/standby failover, hub-and-spoke patterns, and automation-oriented provisioning approaches.

  • Integrated disaster recovery and failover considerations into architecture designs and validation planning.

  • Developed segmentation strategies for wireless and campus environments using SSID-to-zone mapping, peer-to-peer restrictions, policy boundaries, and evaluation of fabric-based approaches for broader enterprise segmentation.

Leadership & Enablement

  • Founded and lead the Design Engineer Council, creating a peer forum for architecture discussion, design review, technical standards, and engineering development.

  • Founded the NetDevOps working group to advance infrastructure automation, infrastructure-as-code practices, repeatable deployment patterns, and engineering adoption of automation.

  • Mentor engineers across network, cloud, and security domains, with emphasis on technical reasoning, architecture ownership, design quality, and independent decision-making.

  • Develop and deliver technical training across networking, cloud, SDN, EVPN, Ansible, Terraform, Python, and infrastructure automation.

  • Facilitate cross-functional architecture discussions to surface constraints, resolve dependencies, improve technical alignment, and give engineers a stronger voice in design decisions.

How This Fits My Architecture Practice

I view architecture as both a design discipline and an enablement function.

A strong architecture should not depend on one person continuing to interpret it. It should leave behind clear decisions, reusable patterns, standards, evidence, and enough shared understanding that other engineers can implement, operate, challenge, and improve it.