I’m an infrastructure engineer focused on systems reliability and distributed compute at scale. I spend my time making sure things don’t break and figuring out why they did when they inevitably do.

---

For those interested in a personal story, I didn’t get into this through a textbook. I got into it because I was bad at video games.

Not “swipe a card on aimware” bad… More like “I need to understand exactly how someone is drawing those boxes around people through walls” bad. That question pulled me down a rabbit hole of reverse engineering, Windows internals, and low-level systems programming that kept me occupied for the better part of five years. I ended up collaborating with professional security research teams globally, contributing to tooling, analysis, and research that required actually understanding how systems work at their lowest levels.

---

At some point, the cat-and-mouse between cheats and anti-cheats and anti-anti-cheats becomes its own kind of horror. What I found genuinely interesting was instead the systems underneath. Infrastructure has the same quality I loved about security research where the problems are organic and the solutions aren’t prepackaged. No two incidents are the same. No two architectures are the same. I love to operate as a one-man think tank thrown against problems that don’t have Stack Overflow answers yet.

---

Currently finishing a B.S. in Computer Science at Southern New Hampshire University. Previously mentored senior engineering capstone teams at the University of Oklahoma’s Gallogly College of Engineering, where I helped build a HIPAA-compliant AI-powered QA platform for 911 call centers, deployed for the City of Norman. On the side I’ve shipped consumer-facing tools including a real-time inventory monitoring system that started locally and scaled to nationwide reach.

If you want to talk infrastructure, reliability, or anything that requires reading disassembly at 3AM — I’m reachable at email on the sidebar.