Learn the real system
Start with how the work actually happens.
Job titles and process diagrams rarely tell the full story. I talk to the people doing the work, trace the handoffs, and understand the incentives before proposing a fix.
About me
Strategic enough to see the operation. Technical enough to fix it.
My job titles have changed. The thread through all of them is the same: I learn how the whole system works, find where it breaks down, and build a practical way forward.
01 / The throughline
I don’t separate thinking from doing.
I’m a technology operations consultant and technical leader with experience across software, infrastructure, specialized hardware, cloud systems, remote support, and business operations.
I tend to become the person people find when something does not make sense. That can mean a device failing at a remote site, two companies whose products cannot exchange data, an inventory process nobody trusts, or an executive who needs a clear answer without a wall of technical language.
I learn what each department does, how work moves between people, and where information disappears. Then I work at whatever level the solution requires: redesign the workflow, connect the systems, write the automation, configure the infrastructure, disassemble the hardware, or document what keeps failing.
I find bottlenecks for a living—and I still enjoy being the person who gets called when “the service just isn’t working.”
02 / How I work
Useful beats impressive.
I care about building something the organization can actually operate after the meeting ends.
Fix the underlying failure
Do not normalize the recurring workaround.
A temporary recovery may be necessary. It should also create evidence for the lasting change: better visibility, stronger design, clearer ownership, or less fragile infrastructure.
Give the honest answer
I’m not interested in selling unnecessary work.
If the right answer is a smaller system, a reused server, an open-source tool, or less technology altogether, that is the recommendation. The goal is a durable result—not a larger invoice.
03 / Range
From executive reporting to the backplane.
The value is not knowing one tool. It is being able to follow a problem across the boundaries where most teams have to hand it off.
See
Monitoring, inventory, incident history, audits, reliability reports, executive summaries
Connect
APIs, automations, shared data views, vendor integrations, cross-team workflows
Run
Linux, cloud and on-prem infrastructure, Kubernetes, databases, remote systems
Repair
Tier 3 software, specialized computers, PCBs, backplanes, RF, SDR, remote hardware
Continue exploring
See how that approach shows up in the work.
Concrete systems, measurable changes, and the career path behind them.
View selected work