I currently work as a Site Reliability Engineer, after moving through support and infrastructure roles that kept me close to the day-to-day realities of operating systems for other people. That path still shapes how I work now: understand the system, stabilize it, and improve the way it is run so fewer things depend on memory, luck, or a late-night manual fix.
Professional Profile
About
Platform engineering and automation work shaped by years in IT operations, support, and hands-on troubleshooting.
Technologies I Use
The platform layers, tooling, and infrastructure systems that show up most often in my work
platform-engineering
HealthyPlatform Engineering
Multi-cluster Kubernetes and OpenShift operations across AWS and on-premises environments.
automation-delivery
ActiveAutomation and Delivery
Provisioning, publish workflows, and lifecycle tooling built to reduce manual steps and standardize execution.
secrets-observability
MonitoringSecrets and Observability
Operational plumbing for credentials, logging, and visibility across production and non-production systems.
independent-infrastructure
ActiveInfrastructure Beyond Work
Self-managed environments that reinforce the same habits I use professionally.
Where that experience comes from
Current engineering responsibility, earlier operations work, and the independent infrastructure that keeps sharpening those habits
Site Reliability Engineer II
Building shared automation, cluster provisioning, secrets infrastructure, and observability workflows for a seven-cluster platform spanning AWS and on-premises environments.
IT Operations and Support
Years of work across workstations, lab systems, thin clients, networking, printers, and device management that built the troubleshooting habits and operator empathy I still rely on.
Home Lab and Independent Builds
A self-managed platform built around Proxmox, k3s, containerized services, and Cloudflare deployments that gives me room to test ideas, sharpen automation, and keep learning.
Core Strengths
Platform ownership, automation, and practical engineering habits
Kubernetes and OpenShift operations
Day-to-day engineering across clustered environments, including upgrades, ingress, storage, observability, and the steady operational work that keeps platforms dependable.
Infrastructure and lifecycle tooling
I enjoy building the scripts, workflows, and provisioning paths that remove manual drift, reduce error-prone handoffs, and make repeated work easier to trust.
Security and observability integrations
Secrets management, logging, monitoring, and the connective plumbing between systems are a large part of what makes an environment actually operable.
Troubleshooting that leads to a fix
I like troubleshooting, but I care most about what remains afterward: clearer documentation, better tooling, stronger visibility, and fewer ways for the same issue to happen again.
Why IT Still Matters To Me
The support background behind the way I think about engineering work
I still care deeply about IT because it sits at the point where systems meet real operational pressure. Support work taught me to take infrastructure personally: if a process is confusing, fragile, or impossible to recover without a specialist, that is an engineering problem even if the software technically works.
That is also where my interest in automation comes from. I like replacing ad-hoc procedures with repeatable ones, building guardrails around sensitive workflows, and making technical work easier for the next person to operate. The goal is not automation for its own sake. The goal is fewer brittle steps, fewer avoidable mistakes, and a calmer environment to maintain.
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 keep building dependable systems, improve the way environments are operated, and use automation to remove unnecessary toil. The work pages remain here as added context, but the center of the site is still the engineering background and résumé.
How I approach the work
The engineering habits and operating priorities that shape the way I build and support systems
Automation-first engineering
The most satisfying work is removing risky manual steps. I like taking operational tasks that used to depend on tribal knowledge and turning them into documented, repeatable tooling.
Platform and cluster operations
I work across Kubernetes and OpenShift environments with an emphasis on upgrades, observability, ingress, secrets, storage, and the operational details that keep platforms stable.
IT roots that still matter
My support and operations background still shapes how I approach engineering work: communicate clearly, debug methodically, and pay attention to the people who have to operate the system after the change ships.
Reliability through execution
I enjoy troubleshooting, but I care more about what happens after the incident. The goal is to leave behind a cleaner operating path, better visibility, and less repeated effort.
Additional work
Other services and project work that still reflect the same troubleshooting, delivery, and practical build mindset
IT Support
Outside work for troubleshooting, setup, networking, and general technical cleanup.
Explore IT Support3D Printing
Project-based design and printing work for prototypes, replacement parts, and one-off builds.
Explore 3D PrintingWebsite Building
Simple, professional websites for individuals, small businesses, and projects that need a clear online presence.
Explore Website Building