Senior infrastructure and enterprise storage engineer in Seattle, with over two decades in enterprise operations. I work backline escalation on enterprise distributed NAS platforms, hold subject matter expertise on a defined set of platform subsystems, and am moving deliberately into automation and systems design.
What I bring is judgment between tools rather than a count of them. Knowing when a problem wants a script, when it wants configuration management, and when it wants orchestration is a different skill from knowing the syntax of all three, and it is the part that holds up when a change has to be safe to run twice against a production system. That judgment came out of twenty-three years of production incidents rather than out of a course.
Backline escalation resource since December 2018 on enterprise distributed NAS, and the named subject matter expert for remote support connectivity and telemetry transport, cluster health assessment frameworks, clusterwide event logging and notification delivery including SMTP and quota alerting, and distributed filesystem job engine execution and recovery.
Work reaches me already escalated. That means production-impacting outages, Severity 1 recovery under aggressive deadlines, and politically sensitive accounts where the technical fault and the customer relationship have to be repaired in the same engagement. Alongside the casework I facilitate corrective-action reviews, mentor engineers on escalation handling and troubleshooting method, and route field-observed failure patterns back to platform engineering, where that feedback has influenced firmware and platform changes.
What I can be held to. Systems design and the reasoning behind the design. Shell and scripting craft in Bash and PowerShell, with Pester coverage on the PowerShell I ship rather than confidence in its output. Incident, escalation, and failure-mode analysis under real time pressure. Runbook and troubleshooting-guide authoring that survives handoff between shifts and regions. Linux and Windows systems administration, and enterprise storage at scale.
What I am applying, framed as practice rather than authority. Containers and Docker. Observability and monitoring design, built on production experience with SolarWinds Orion, SCOM, Datadog, and PagerDuty. I write about these as applied practice and say so when a piece documents a first pass rather than a settled approach.
What I am building toward. Ansible, Kubernetes, Terraform at depth, cloud at depth, and GitOps. I learn these in public and I do not claim them.
Campus network and systems administration across 196 wireless access points and 55-plus virtualized Windows servers. NOC operations spanning 750-plus physical and virtual Linux and Windows servers across multiple data centers, including PowerShell-driven patch deployment to 215 servers. Sole IT administration for a roughly 100-person organization running its own Active Directory, Exchange, and backup stack. The through line is production ownership rather than project work.
Red Hat instructor-led coursework through my employer: RH124 (v8 and v9.3), RH134 (v8 and v9.3), and RH024 (v9.3). Kepner-Tregoe structured problem solving, 45 hours. These are course completions, not exams. I have not sat EX200 and I do not claim RHCSA.
Older repositories here are coursework from earlier study and do not represent current work. The tooling I build day to day runs inside customer environments and is not publishable.