initializing render pipeline
Open to opportunities

Your Name Systems Administrator

I keep infrastructure boring — on purpose.

~/whoami

            

01 — Selected work

Systems I built, broke, and hardened

Infrastructure I designed, deployed and kept running — including the decisions I would make differently now. Each entry opens into the architecture, the constraints I worked under, and the source.

02 — Proof of work

What the work actually looked like

Consoles, dashboards, topologies and failures caught in the act. Each one is annotated with the symptom, the diagnosis and the fix — so you can judge how I reason under pressure, not just what I claim on a résumé.

03 — Generalist profile

Breadth is the specialty

Nothing here is self-scored. Every point on this radar is earned by a system above it or a documented fix below it — click any of them and you land on the evidence. It shows where I can work unsupervised, and where I am still building depth.

04 — Trajectory

How the generalist got built

Certifications, homelab milestones, and the incidents that taught more than any course.

    05 — Next step

    Let's talk about your infrastructure.