Tech stack
Where the depth actually is.
Not a logo wall. Every row below is a tool we've actually run in production, with the reason we reach for it instead of the obvious alternative.
Core: battle-tested
Cloud
Default unless a client is already committed elsewhere — deepest service catalog, and most hiring teams already know it.
Containers & Orchestration
Docker for packaging by default. Kubernetes only once a workload actually needs orchestration, not as a resume line.
Proof: Kubernetes Research Platform →Infrastructure as Code
Terraform provisions, Ansible configures what’s on top. State and playbooks live in your repo, not a SaaS dashboard.
CI/CD
Jenkins where a client already runs it. GitHub Actions for anything greenfield — no reason to bolt on a separate tool.
Observability
Prometheus and Grafana by default. Elastic Stack added once logs need to be searchable at scale, not just metrics on a dashboard.
Systems
Linux and bash are the floor everything else sits on. Python takes over once a script outgrows what bash should reasonably do.
Proof: Automated Content Pipeline →Capable on request
Cloud
Other stacks
Why the split matters
Core tools transfer to any cloud. If your stack runs on GCP or Azure instead of AWS, the underlying DevOps practice, the IaC discipline, the CI/CD shape, the observability approach, doesn't change. Just ask what that looks like on your provider.