Entry-level DevOps Engineer resume example

• With a senior colleague reviewing the change, provisioned Kubernetes environments with reviewed Terraform plans and CI/CD promotion gates. Tested rollback on a failed health check so the previous release could be restored without a manual configuration change.
• Within an assigned workstream, added Linux service monitoring and a Python check for expiring certificates, stale deployments, and disk pressure; linked alerts to an owner and a tested recovery command.
• Within the assigned scope, split Terraform plans by environment, reviewed resource replacements before approval, and rehearsed restoration of the previous deployment with the on-call engineer.
• Within the assigned scope, owned a Kubernetes rollout checklist using Terraform plans and CI/CD health gates, reducing failed deployment recovery from 28 to 12 minutes in a staging drill.
• Within the assigned scope, built Python monitoring checks for AWS resource drift and Linux service failures, resolving stale alerts before publishing the on-call documentation.

• The team right-sized compute from utilization and commitment data across 11 workloads; my scope was data preparation, quality checks, and follow-up documentation under senior review. The team kept the lower-effort process in place after handoff; documented my assigned work separately from the team result and confirmed it with a senior colleague.
• Within the assigned scope, reviewed a proposed change against the existing interface contract, reproduced a reviewer’s edge case, and added the missing test or example before merging the change.
• Within the assigned scope, investigated a failure reported by a downstream team using the exact version and input they supplied. Reduced it to a reproducible test, delivered the fix with compatibility notes, and confirmed the original case passed before closing the report.

• Within the assigned scope, the team moved 83 manually managed cloud resources into reviewed Terraform modules; my scope was data preparation, quality checks, and follow-up documentation under senior review
• Built an isolated fixture with normal, malformed and interrupted inputs; recorded the expected response before running the implementation so failures were distinguishable from a changed assumption.
• Packaged the reproduction steps, configuration and regression tests with the project; checked the instructions from a clean environment and documented the unsupported cases instead of claiming production readiness.
• Owned the independent regression fixture using isolated inputs, resolved a failing edge case and released a reproducible test package with expected outputs.

Relevant coursework: Algorithms, operating systems, databases, computer networks

Kubernetes · Terraform · AWS · CI/CD · Observability · Incident response

• Published an independent technical note using the project’s before-and-after traces, explaining the failed assumption, regression coverage and cases the implementation does not support.