Hiring a DevOps Engineer? This page maps what the role usually asks for to the work I’ve done, with a link to each piece of evidence.

RoleDevOps Engineer
LocationTracy, California (San Francisco Bay Area)
Work arrangementRemote anywhere in the U.S., or hybrid in the Bay Area
AvailabilityOpen to new roles now

What the role asks for, and where I’ve done it

The job asks forWhat I’ve doneEvidence
Infrastructure as codeBuilt a multi-tenant AKS platform with Terraform modules, where onboarding a customer is a 1-line change to customers.tfAKS case study
CI/CD pipelinesGitHub Actions pipeline with 23 backend tests at 98.55% coverage, end-to-end tests in ephemeral k3d clusters, and automated releasesCI/CD repo
Security in the pipelineTrivy image scanning gate; HIGH/CRITICAL findings cut from 20 to zero. Restricted Pod Security Standards and Cilium network policies per tenantCI/CD repo · AKS case study
Kubernetes and GitOpsFlux CD reconciling an AKS platform and a 3-node Raspberry Pi K3s cluster from Git; secrets encrypted with SOPS and Agepi-cluster repo
Monitoring and incident responsePrometheus and Grafana with Telegram alerts; 4 real incidents diagnosed and written up as postmortemspi-cluster repo
Backups and recoveryDaily PostgreSQL backups to Azure Blob Storage, and a restore tested end to end in a DR labDR lab write-up
Documented decisionsEach major choice recorded with the alternatives and the tradeoffs acceptedDecision records

Background

U.S. Navy veteran (avionics electronics technician), then 10+ years in regulated healthcare diagnostics operations at Genomic Health / Exact Sciences, where following procedures exactly and documenting every deviation was the job. I bring that same habit to infrastructure: runbooks, postmortems, and changes made through Git.

Core stack: Kubernetes (AKS, k3s, k3d) · Terraform · FluxCD · GitHub Actions · AWS · Azure · Docker · Prometheus / Grafana · Python · Bash

Next step