Open to work · Immediately
I like startup-style engineering: move fast, own the mess, ship the thing, then stay close enough to fix it when it breaks.
Most of my work sits around backend services, CI/CD, containers, Kubernetes, cloud infrastructure, observability, and deployment reliability.
I care about systems that are simple to run. A deploy should be boring. Logs should tell the truth. Infra should be understandable when the pager is loud.
I also read and learn backend engineering and distributed systems deeply, because the theory starts to matter once real systems hit load, latency, and failure.
Working principles
- Build small enough to debug.
- Ship fast, but keep a rollback path.
- Automate the boring failure-prone work.
- Make logs, metrics, and alerts useful before they are needed.
- Use simple infrastructure until the system earns more complexity.
Engineering focus
Backend Engineering
Building APIs, workers, queues, and data paths that can take real traffic and still be understood when something breaks.
Current threads: REST, Queues, Retries, Idempotency, Postgres, Redis, Kafka, Background jobs, and clean service ownership.
DevOps and cloud
Shipping code through CI/CD, containers, cloud infrastructure, and release flows that do not fall apart under pressure.
Current threads: CI/CD, Docker, AWS, Terraform, Linux, environments, rollbacks, secrets, and deploy hygiene.
Kubernetes and Infrastructure
Working with clusters, workloads, networking, metrics, and the infrastructure around services after they leave localhost.
Current threads: Kubernetes, Helm, Nginx, Prometheus, observability, scaling behavior, and cluster operations.
Distributed systems
Learning the parts of backend engineering that show up when one machine is not enough and failure becomes normal.
Current threads: replication, consensus, partitions, queues, caches, timeouts, coordination, and failure modes.