I work where backend engineering, infrastructure, and production operations meet.
A career path traced through curiosity, complex systems, and a bias for understanding the whole stack — not just the layer that broke.
-
origin
I started in IT young, driven by curiosity about how systems work under the hood — packet flows, kernel timers, the quiet logic running underneath every service.
-
specialization
Over time I specialized in backend development and infrastructure, working in production environments where reliability and performance are not negotiable.
-
daily work
I debug complex issues, understand distributed systems, and improve stability across Linux, Kubernetes, Helm, CI/CD, cloud platforms, networking, logs, metrics, and application behavior.
-
trajectory
My goal is to operate as a senior Cloud and Infrastructure Engineer — scalable architectures, observability, automation, production-grade reliability.
Operating principles
- Reliability and performance matter most when systems are under real production pressure.
- Debugging starts by understanding the whole path: network, infrastructure, runtime, data, and application behavior.
- Automation comes after understanding the manual procedure — only script what you can already perform by hand and reason about end to end.
- Every incident leaves a trace: a runbook entry, a metric, or a fix at the right layer — so the next occurrence is shorter than this one.
Trust artifacts
- Enterprise cloud support experience across customer-facing production workloads.
- Documented incident response process with runbook follow-through and postmortem discipline.
- Hands-on ownership of Linux, Kubernetes, CI/CD, databases, and networking in the same delivery path.
- Public-safe technical case files that preserve real constraints and operational decisions.