IT Systems Engineer · Fort Lauderdale, FL
Systems engineer who writes the software.
7+ years as the sole or lead technologist for multi-site networks, Linux and Windows systems, Microsoft 365 and endpoint fleets, and the Python and JavaScript automation that ties them together. Now building LLM tooling for operations.
Open to systems and platform engineering roles
Isolate
Find the layer the fault lives in before touching anything: cable, route, port, certificate, config.
Fix
Fix it there, not three layers up where the symptom showed.
Script
Turn the fix into automation so the same ticket never needs a human twice.
Selected work
Reads Zendesk tickets and their screenshots, looks people up in an admin portal that has no API, fixes the common cases in a real browser, and drafts replies a second model checks.
proves Handles the common cases end to end, and a second model checks every reply before it goes out.
Captions the other side of a call from the sound card, with a jargon panel and notes plus timing metrics afterwards. No bot joins the call.
proves Live audio pipeline designed around one constraint: nothing visible to the other party.
A voice front end that sends each spoken request to the cheapest tier that can handle it: no model, Claude Haiku, or a full agent session that asks permission out loud.
proves Routes by cost, and asks permission out loud before anything that acts.
41 Docker scenarios that break real boxes (systemd, networking, Docker, GPU) and verify your fix, plus a printable cheat sheet.
proves Troubleshooting method as a repeatable exercise: isolate, fix, prove.
Arcade
Snake and Breakout, because every portfolio should have an arcade. Mouse, keyboard or touch. Press play on one and the other pauses.
Snake
Eat the dots, don't bite yourself. The walls wrap around.
Breakout
Clear the bricks and catch the falling pickups. Move the mouse (or drag) to steer.
drag to move · tap to launch / fire
Reading list
emudhra.we-have-a-problem.com 1066 points 381 comments 16h ago
nullpt.rs 928 points 195 comments 10h ago
blog.google 836 points 698 comments 10h ago
Contact
Recruiter, hiring manager or fellow engineer: leave your name and email and I'll write back. A note about the role or problem helps.