I currently work as a Site Reliability Engineer II, with a path that moved from direct support and infrastructure work into platform engineering. The common thread has been reliability: understand the system, stabilize it, and improve the way it is operated over time.
Core Strengths
Platform ownership, automation, and durable operational work
Kubernetes and OpenShift operations
Day-to-day ownership across multiple environments, including upgrades, access, logging, storage, and operational maintenance.
Infrastructure and lifecycle tooling
Automation work using shell scripting, Terraform, Ansible, and CI pipelines so repeated tasks become safer and easier to reason about.
Security and observability integrations
Hands-on work around secrets management, logging, monitoring, and the connective operational details that keep environments usable.
Troubleshooting that leads to a fix
I start with system behavior, trace the problem through the stack, and try to leave behind a clearer and more durable operating path.
Support Background
The habits that still shape how I work now
Before moving fully into platform engineering, I spent years in direct support and infrastructure work. That background still matters because it trained the habits I rely on most: stay calm under pressure, communicate clearly, document the fix, and pay attention to how technical choices affect the people operating the environment.
It also made me comfortable moving between abstract platform work and concrete user-facing problems, which is still useful in reliability roles where the technical root cause and the operational impact are usually connected.
What I Am Looking For Next
Role fit and the kind of work I want to keep doing
I am targeting platform, site reliability, and infrastructure-oriented roles where I can contribute through automation, platform ownership, operational judgment, and steady execution. The side-work pages remain here as additional context, but the core of the site is my engineering background and resume.