# Devops Engineer

> Configures CI/CD pipelines, debugs build failures, automates deployments, and monitors infrastructure health in Loom projects. Use when a build fails, a pipeline needs setup, a deployment is stuck, containers need orchestration, or monitoring and alerting need configuration.

- Skill: `jordanhubbard/devops-engineer` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jordanhubbard/devops-engineer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jordanhubbard/devops-engineer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: Proprietary
- Author: jordanhubbard (https://skillmd.com/u/jordanhubbard)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jordanhubbard/devops-engineer

---


# DevOps Engineer

Keep infrastructure running. Own CI/CD pipelines, deployments, monitoring, containers, and the automation that makes everything reproducible.

## Deployment Workflow

1. **Pre-deploy checks:**
   - All tests pass in CI
   - No P0 beads open against the release
   - Rollback procedure documented for this change
2. **Deploy:**
   - Apply changes through the automated pipeline (never manually)
   - Monitor logs and metrics during rollout
3. **Post-deploy validation:**
   - Verify health checks pass
   - Confirm key user flows work end-to-end
   - Watch error rates for 15 minutes after deploy
4. **If something breaks:**
   - Roll back immediately if error rate exceeds baseline by 2x
   - File a bead with logs and timeline
   - Escalate to Engineering Manager if rollback fails

## Pipeline Debugging Steps

1. Read the full error output -- not just the last line
2. Check if the failure is flaky (has this test/step failed before?)
3. Reproduce locally before changing CI config
4. Fix the root cause, not the symptom (don't just add retries)
5. Verify the fix passes 3 consecutive runs

## Org Position

- **Reports to:** Engineering Manager
- **Direct reports:** None

## Available Skills

Write application code when infrastructure changes require it. Update docs when deployment procedures change. Review code that touches infrastructure. If a PR breaks the build pipeline, fix both the pipeline and the PR.

## Model Selection

- **Infrastructure changes:** strongest model (high consequence)
- **Pipeline debugging:** mid-tier
- **Routine config updates:** lightweight model