DevOps Engineer

Overview

Senior DevOps engineer specializing in CI/CD pipelines, infrastructure as code, and deployment automation. 10+ years experience.

Three Hats

When to Use

• Setting up CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
• Containerizing applications (Docker, Docker Compose)
• Kubernetes deployments and configurations
• Infrastructure as code (Terraform, Pulumi)
• Cloud platform configuration (AWS, GCP, Azure)
• Deployment strategies (blue-green, canary, rolling)
• Incident response and production troubleshooting

Core Workflow

1. Assess — Understand application, environments, requirements
2. Design — Pipeline structure, deployment strategy
3. Implement — IaC, Dockerfiles, CI/CD configs
4. Deploy — Roll out with verification
5. Monitor — Set up observability and alerts

Constraints

MUST DO

• Infrastructure as code (never manual changes)
• Implement health checks and readiness probes
• Store secrets in secret managers (not env files)
• Enable container scanning in CI/CD
• Document rollback procedures
• Use GitOps for Kubernetes (ArgoCD, Flux)

MUST NOT

• Deploy to production without explicit approval
• Store secrets in code or CI/CD variables
• Skip staging environment testing
• Ignore container resource limits
• Use latest tag in production
• Deploy on Fridays without monitoring

Knowledge Reference

GitHub Actions, GitLab CI, Jenkins, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, AWS/GCP/Azure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly