About
I am a Cloud and DevOps engineer. I design and operate infrastructure that engineering teams depend on in production. My focus is on reliability, automation, and systems that are simple enough to maintain long after I hand them over.
Why Infrastructure Instead of Features
Most engineers want to build the product. I prefer building the platform underneath it. A well-designed deployment pipeline, a properly monitored cluster, or a clean CI/CD system does not get attention — but it determines whether the product team can ship with confidence or spends half their time debugging infrastructure.
Reliability over complexity
A simple system that works under pressure is better than a sophisticated system that fails unpredictably. I choose boring, proven tools over interesting, untested ones.
Automation by default
If a task will be done more than once, it should be automated. Manual processes are error-prone and do not scale. Every deployment, every environment setup, every recovery procedure should be codified.
Observability as a requirement
A system without monitoring is a system you cannot operate. I build observability from the start — dashboards, alerts, structured logs — not as an afterthought after the first outage.
Simplicity
Every additional service, abstraction, or dependency is a future maintenance burden. I add complexity only when the problem genuinely requires it, and I remove it when it no longer does.
Security by design
Security is not a separate phase. Non-root containers, least-privilege access, encrypted communication, and proper secret management are built into the architecture from the first commit.
How I Work
I work with clients the same way I work with engineering teams — clear communication, honest timelines, and no surprises.
Discovery
I start by understanding the actual problem. What exists today, what is painful, what the team needs. Requirements are clarified before any architecture is proposed.
Planning
I propose an architecture with clear tradeoffs. What this approach gains, what it costs, what alternatives exist. No implementation starts without an agreed plan.
Implementation
I build iteratively — small, working increments. Each milestone is deployable and testable. Progress is visible throughout, not revealed at the end.
Documentation
Every system I build includes operational documentation. Architecture decisions, deployment procedures, troubleshooting guides, and runbooks. The system should be operable by someone who was not involved in building it.
Handover
I transfer knowledge to the team that will maintain the system. Walkthrough sessions, documented procedures, and a clean codebase. My goal is that the team never needs to call me back for something I should have documented.
Technologies
Cloud
AWS, Google Cloud, Azure
Infrastructure
Docker, Docker Compose, Nginx, Linux
CI/CD
GitHub Actions, Jenkins, GitLab CI
Monitoring & Observability
Prometheus, Grafana, Loki, AlertManager, OpenTelemetry
Languages & Scripting
Python, Bash, Node.js, TypeScript
Want to work together?
I am available for freelance Cloud and DevOps engineering work. If you have a project that needs reliable infrastructure, let's talk.