§ 01 · About
About Me
Senior Software Engineer based in the Pacific Northwest, with a decade of experience across the software stack. Currently advising federal teams on backend architecture and delivery standards at Peraton.
The career timeline is on the experience page. This page covers practice and methodology.
How I work
Practice
- Accessibility as Acceptance Criteria
- DHS Trusted Tester certification, issued April 2025. Audits against the DHS-published Trusted Tester test process, which conforms to the current Section 508 Standards (36 CFR 1194) and WCAG 2.x Level AA. Treated as merge-blocking acceptance criteria on every PR, not a remediation phase before ATO. Federal programs require it; it's also how I run non-federal work.
- Domain-Driven, Event-Driven
- Clean Architecture + DDD layering on NestJS, with bounded contexts that survive feature growth. Event-driven boundaries (WebSockets, queues) between contexts so a slow consumer can't cascade. The architecture is the constraint, not the framework.
- Built-In Quality
- SAFe 6 Agile SE practice. Architectural standards documented, code review enforced, coverage tracked against domain behavior rather than line count. Regressions caught pre-merge, not post-release.
Systems should be boring in production and interesting in design.
Beyond the stack
Interests
- Infrastructure as Code
- Production-grade homelab as a personal lab for the same patterns I push at work. Single-node Proxmox VE 9.x running K3s. Authentik OIDC out of cluster on a dedicated LXC so a cluster destroy/apply cycle never locks me out of the auth gate. Cloudflare Tunnel terminates every public hostname; zero open WAN ports. OpenTofu provisions, Ansible configures, Flux CD reconciles. This site runs on it.
- Low-Level Systems
- Memory layout, concurrency primitives, runtime cost. Rust as the primary tool. Built a Rust + Actix Web messaging PoC at Semper Valens establishing baselines for low-latency state synchronization.
Understanding the layers below makes you better at the layers above.