Skip to content
/work

Engineering case studies

Systems built in production environments. No employer names — scale and constraints only.

CASE 01 · FLAGSHIP

Stevens Knowledge Hub

Next.js · React · TypeScript · Node TS API · Python Scapy / pyshark · PostgreSQL · S3 · Docker · LLM explanations

Protocol education and analysis platform in the W. Richard Stevens tradition: annotated PCAP decode, guided reading, learning paths, protocol playground, multiplayer analysis sessions, legacy hall.

↳ The book I learned from, rebuilt as software.

CASE 02

PAN-OS fleet automation platform

DuckDB · Python · Node · D3

Pre/post upgrade behavioral validation, CVE exposure mapping, config drift detection and real-time upgrade telemetry across a large firewall fleet.

↳ Upgrade risk made measurable before the change window opens.

CASE 03

PingVault

BGP · Python · DuckDB

Network intelligence and BGP cascade forensics platform — reconstructing propagation, blast radius and timing after a routing event.

↳ Answering what actually happened, once the event is over.

CASE 04

Azure cross-tenant Cloud NGFW hub

Azure · Cloud NGFW

Cross-tenant inspection hub for a large healthcare enterprise: one isolated Azure subscription, Cloud NGFW as SaaS, and route lists as the authorization mechanism.

↳ Attachment and route boundaries that survive an org chart.

CASE 05

Multi-tenant Strata Cloud Manager

Strata Cloud Manager · Prisma Access · Prisma SD-WAN

Tenant hierarchy, naming standard and identity plane for a large healthcare enterprise that keeps acquiring companies it cannot fully absorb.

↳ Hierarchy keyed to who manages, not where.

CASE 06

GlobalProtect M&A reference architecture

GlobalProtect · Routing · Identity

Remote-access pattern for absorbing acquired networks without collapsing address space or trust.

↳ A repeatable integration path instead of a bespoke one per acquisition.

CASE 07 · HISTORICAL

Expedition

Migration tooling · Config parsing · Firewall migration

Early adopter of Palo Alto Networks' firewall migration tool, and a member of the customer group that helped frame key requirements during its early development. Historical.

↳ Where the validate-both-ends migration methodology came from.