Trace

I am a Linux, Cloud, and Infrastructure Engineer with a strong foundation in system administration, technical support, troubleshooting, automation, and production operations.

My career has been shaped by a long-standing interest in how systems work beneath the surface: Linux, networking, storage, identity, monitoring, containers, automation, and cloud infrastructure. Before moving into professional infrastructure roles, I spent years independently learning Linux and sysadmin work through personal servers, homelab projects, self-hosted applications, and hands-on troubleshooting. That self-directed background gave me the practical mindset I still rely on today: build things, break things, understand why they failed, and improve them.

Professionally, I have worked in infrastructure and technical support environments where reliability, clear communication, and disciplined troubleshooting matter. I have supported Linux systems, investigated alerts and incidents, worked through complex technical issues, participated in on-call rotations, and helped maintain service continuity in operational environments.

My strongest area is Linux. I have experience with Oracle Linux and RHEL-like systems, including troubleshooting, package and repository management, system upgrades, boot-level issues, storage and volume management, PAM integration, CVE mitigation, networking, and cloud-hosted instances. I enjoy going deep technically and prefer to understand the root cause of a problem rather than applying surface-level fixes.

I am also actively building stronger expertise in cloud infrastructure, DevOps, and reliability engineering. My experience includes OCI-related support scenarios, AWS-focused learning, Docker-based self-hosted services, monitoring workflows, and automation using shell scripting, systemd, cron, and incron.

Outside of work, I maintain a homelab and self-hosted infrastructure. This includes dedicated servers, Dockerized applications, WireGuard VPN, Nginx-based services, monitoring workflows, and custom automation. One project I am particularly proud of involved redesigning a systemd-based automation workflow that previously relied on hundreds of long-running processes. I replaced it with a cleaner event-driven design using decoupled microservices and queuing systems, making the system more efficient and maintainable.

I approach infrastructure work with a troubleshooting-first mindset. When something breaks, I focus on understanding the impact, gathering evidence, isolating the failure domain, applying the safest effective fix, documenting the resolution, and looking for ways to prevent recurrence. I value clarity, ownership, technical honesty, and continuous improvement.

My career direction is toward roles that combine Linux engineering, cloud infrastructure, automation, and reliability. I am especially interested in DevOps Engineer, Cloud Engineer, Linux Engineer, Infrastructure Engineer, Site Reliability Engineer, and Technical Support Engineer roles with strong technical depth.

What makes my profile different is that my interest in infrastructure did not start with a job title. I spent years learning independently, building systems, running servers, reading documentation, and solving practical problems before entering professional infrastructure work. That background gave me persistence, curiosity, and a genuine investment in the craft.

In short, I am an infrastructure-focused engineer who enjoys solving difficult technical problems, improving system reliability, automating operational work, and growing toward deeper Linux, cloud, DevOps, and SRE expertise.