Systems Engineer / DevOps

I build calm, observable infrastructure that survives real traffic.

Linux. Kubernetes. Terraform. CI/CD. SRE practices. I reduce toil, harden deployments, and make incident response boring.

See projects Download resume
Availability
99.9%+
SLO-driven changes
Delivery
Minutes
Fast, safe pipelines
Cost
-20%
Right-sizing + finops
$ kubectl -n platform get deploy
NAME              READY   UP-TO-DATE   AVAILABLE
api-gateway       6/6     6            6
payments-worker   4/4     4            4

$ terraform plan -out tfplan
Plan: 2 to add, 1 to change, 0 to destroy.

$ gh workflow run deploy.yml -f env=prod
✓ queued  ✓ running  ✓ succeeded
GitHub Actions Kubernetes Terraform Observability

Selected work

Concrete outcomes. Replace with your real projects and links.

Platform baseline with Terraform

IaC

Standardized VPC, IAM, and EKS modules; policy guardrails; environment promotion with drift detection.

  • Terraform
  • AWS
  • OPA/Conftest
Repo Case study

CI/CD with progressive delivery

Delivery

Built pipelines with signed artifacts, gated rollouts, and automated rollback on error-budget burn.

  • GitHub Actions
  • Argo CD
  • SLSA
Diagram Write-up

Observability: metrics, logs, traces

SRE

Unified dashboards, alert hygiene, and trace sampling; shortened MTTR via structured runbooks and on-call tooling.

  • Prometheus
  • Grafana
  • OpenTelemetry
Dashboards Runbooks

What I’m good at

Strong opinions, loosely held. I optimize for safety, clarity, and operability.

Core

  • Linux administration, networking, hardening
  • Kubernetes operations, Helm, GitOps
  • Infrastructure as Code: Terraform modules + standards
  • CI/CD: build, test, deploy, release automation
  • Monitoring, alerting, tracing, incident response

Toolbox

  • AWS / GCP / Azure (pick what you actually use)
  • Docker, container registries, image signing
  • Prometheus, Grafana, Loki, Tempo / Jaeger
  • Nginx, HAProxy, service meshes (as needed)
  • Python / Bash, Go basics, YAML without tears

How I work

  • Design docs and runbooks people actually read
  • SLIs/SLOs, error budgets, alert fatigue reduction
  • Postmortems with clear follow-ups and owners
  • Secure defaults: least privilege, secrets hygiene
  • Cost awareness: right-sizing, reservations, cleanup

Experience

Swap in your real roles, companies, and dates.

2023 → Present
Company Name

Systems Engineer / DevOps

  • Built golden paths for services (templates, pipelines, observability defaults).
  • Improved deployment reliability with progressive delivery and automated rollback.
  • Reduced on-call noise by tightening alerts and adding actionable runbooks.
2020 → 2023
Company Name

Systems Engineer

  • Migrated legacy deployments to containers and standardized runtime configs.
  • Automated server provisioning and patching with repeatable playbooks.
  • Partnered with developers to remove toil and shorten lead time.

Contact

Open to platform, DevOps, and SRE roles.

Email you@example.com
GitHub github.com/USERNAME Public work
LinkedIn linkedin.com/in/USERNAME Reach out

What I like working on

Platform engineering, CI/CD, Kubernetes operations, observability, infrastructure automation, security hardening, and cost optimization.

If you send a job spec, I’ll reply with a 3–5 bullet match map and questions.