I'm Joe.
Nuclear & Cyber Defense Architect. Military by formation, engineer by trade, builder by habit. I came up through operations-heavy environments where the question is never "is the system elegant" but "does the system survive contact with reality." That bias bleeds into everything I ship: small surface area, boring tools, honest documentation.
I still hold the rank of E5 — Staff Sergeant, United States Air Force. The values it taught me are not decoration; they are how I work.
// altitude over detail — no employer names, no dates. specifics on request.
What I do
- Identity hardening across multi-cloud estates
- Policy-as-code that retires manual review queues
- Detection engineering — Sentinel / CrowdStrike
- Incident response & the post-mortems that follow
- Landing zones, IaC review culture from scratch
Stack
- security: identity, policy, IR, detection, threat modeling
- cloud: azure (primary), aws, terraform, bicep
- code: powershell, python, typescript, bash
- ops: linux, networking, observability, containers
- lead: small high-trust teams, written-first culture
In rough order of how reliably I'll answer:
- X / Twitter — @Tank23x0 fastest
- LinkedIn — /in/tank23x0 longer-form
- GitHub — Tank23x0 code
- Discord handle on file
For collaboration or "hey can you look at this" — DM on X is the fastest path.