Skip to content

About

Operations leader. Systems builder.

I spent years running complex, distributed operations. I now apply the same discipline to building and testing technical systems.

Where I started

For most of a decade I led multi-location operations: a ten-location district with more than four hundred employees, spanning convenience retail, quick-service restaurants and full-service deli. The job was budgets, labor, inventory, audits, food safety, vendor coordination and, above all, people development. I built the training and onboarding systems that made performance consistent across sites, and I learned to read a business through its reports and its exceptions.

That work taught me something that shows up in everything I build now: systems fail at the boundaries. A process that depends on someone remembering a step will eventually break. A report that cannot be reconciled to its source cannot be trusted. The fix is always the same: make the rules explicit, make the gates measurable, and make the record honest.

Today I am a District Manager at Public Storage, where multi-location operations remain my formal role. The technical work on this site is independent project experience, except where a project is explicitly marked as built in role.

Why I moved into technical work

I expanded into engineering because I wanted to understand how the systems I depended on actually worked, and because the most interesting operational problems were increasingly technical: how to automate reporting, how to use language models without letting them invent numbers, how to tell a data defect from a reasoning defect, and how to know whether a system is secure rather than assume it.

So I built things. A deterministic trading platform that reuses the same components for backtesting and paper trading and refuses to act when any precondition is unmet. An AI operations assistant that calculates every metric with rules and reserves the model for interpretation. A Python port scanner written from raw sockets, and a Kali lab with intentionally vulnerable targets to practice against. Flask applications, Streamlit tools, automation scripts and local model experiments along the way.

How the two fit together

Operations leadership is not a detour from technical work; it is the reason my technical work looks the way it does. I know what a manager needs from a report because I was that manager. I know why a risk control must be enforced by the system rather than by discipline because I have watched discipline fail under pressure. And I know that a result only counts once it has been verified, which is why every project here carries the status it has actually earned and why the trading platform's soak certification is attributed to the exact build it came from.

I am not claiming a career spent as a software engineer or security analyst. I am claiming something I can show: substantial, hands-on experience designing, building, troubleshooting, evaluating and testing complex systems, with the judgment to know their limits.