I help keep mission-critical
healthcare platforms running.
I thrive at the intersection of engineering and complex systems — where running healthcare platforms at scale takes both deep technical judgment and the ability to bring teams along with you.
Service Engineer II · Health & Life Sciences S&P · Microsoft
I lead high-stakes escalations, drive service reliability improvements, and mentor engineers across enterprise Healthcare SaaS on Azure. I don't just solve problems — I help build the processes and playbooks that stop them recurring.
Nearly a decade in healthcare IT has given me a systems thinker's mindset and a sharp instinct for risk, resilience and accountability — the things compliance actually demands. I'm growing toward Principal and engineering management, where I can shape both how systems are built and how teams operate. The best engineering cultures treat those as inseparable.
Distributed platforms are only as debuggable as the view you have into them. I build diagnostic tooling that takes whatever identifier an engineer starts with and resolves the full picture around it — turning a multi-day investigation into a single query.
When a mission-critical system degrades, the technical fix is half the work. The other half is holding one clear, honest line across customer, engineering and leadership while the picture is still forming.
Every incident should leave something behind — a playbook, a new signal in telemetry, or a change to how the work is done. The goal is that the same problem never has to be solved twice.
Onboarding material, mentoring and regular sessions on the skills that are hardest to pick up alone — tracing a request end to end, backend investigation, running an escalation well. Ten engineers who can do the work beats being the only one who can.
The quality of the tooling sets the ceiling on the quality of the work.
A clearly bounded problem gets solved. An unbounded one just gets older.
Ambiguous data produces ambiguous conclusions — and in healthcare that is not a neutral outcome.
Every tool and every write-up is one less thing the next engineer has to work out alone.
Reliability isn't the absence of failure. It's what you've built to meet it.
A mix of platform, operations and people — the three things a seasoned professional is expected to hold together.
Things I've built. Some at work, some at 1 a.m., all because something should have existed and didn't.
Turns a boarding pass, train ticket or cinema booking into a pass that opens instantly with no signal. The barcode is transplanted byte for byte, never regenerated, so it scans exactly as the original does. Nothing is uploaded — there is no server to upload it to.
Point it anywhere on Earth and watch what's overhead. Live aircraft telemetry as an amber HUD over a dark map — route arcs, airport beacons, cinematic overlays. No backend, no API keys, entirely in the browser. The public ADS-B feeds closed browser access in 2026, so the demo is offline; the code and a CORS shim to revive it are in the repo.
Move a file between two devices on light alone. One screen encodes it into visual frames, the other's camera reads it back — no network, no pairing, no cable. One HTML file, nothing to install.
Telemetry from every client surface and backend path, correlated into one investigative view, plus a live geographic picture of platform activity. Started as a workaround for one stubborn case; now a daily tool across four functions and three continents.
Weekend builds that turned into something worth finishing.
An agentic AI concept for water conservation — tracks household usage against a personal baseline, then nudges, scores and rewards the reductions. Gamified because behaviour change rarely survives a spreadsheet.
Extending the life of retired business hardware — secure reuse, ownership transfer and donation before recycling is ever considered. Grew from one idea into a volunteer team across multiple offices and disciplines.
Where the thinking happens when I'm not at a keyboard — and where it happens when I am.
Where most of the thinking actually happens.
The only reliable way I know to stop thinking.
Building the thing that should exist, one late evening at a time.
Slow feedback loops, no dashboards, excellent teacher.
Got a stubborn system, an idea worth building, or a question you can't get a straight answer to? Say the true thing plainly — I'll do the same.
