01 — About
Systems-level engineering, shipped under real constraints
I work close to the metal — C and C++17, data structures, algorithms, concurrency, and manual
memory management — while shipping production software that government staff and the public
depend on every single day.
At the Pinellas County Clerk of the Circuit Court, I designed a fully offline,
AES-256 encrypted application that automates Florida probate guardianship court
filings, and I maintain public platforms in the DNN CMS serving roughly 500,000 residents and 500+
internal staff. A court environment is unforgiving in a useful way: accuracy, auditability, and
accessibility aren't features I add later — they're the requirements.
Outside of work I build C/C++ engines around graph algorithms, polymorphic architecture, and
multithreading, and I hold them to the same bar: CMake builds, GitHub Actions CI, and
regression checks on every push. I benchmark instead of guessing — that's how I know A*
explores 97% fewer nodes than Dijkstra on my graphs rather than just assuming it does.
I'm seeking a software engineering internship — in defense, aerospace, or any team
where correctness and performance genuinely matter. I'm a U.S. citizen and eligible for a security
clearance, and I'm equally at home on a systems codebase or a full-stack product team.