Internship DevOps Engineer resume example

• Under supervision, split Terraform plans by environment, reviewed resource replacements before approval, and rehearsed restoration of the previous deployment with the on-call engineer.
• The team standardized progressive delivery and automated rollback checks for 27 services; I supported research preparation, validation, and documentation under mentor review. The team kept the service stable through the next period of peak demand; confirmed with my mentor that my contribution was limited to the assigned support and validation work.
• The team set service-level indicators and actionable alerts for 16 customer-facing paths; I supported research preparation, validation, and documentation under mentor review. The team reduced repeat incidents from the same failure mode; confirmed with my mentor that my contribution was limited to the assigned support and validation work.
• Under supervision, 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.
• Under supervision, built Python monitoring checks for AWS resource drift and Linux service failures, resolving stale alerts before publishing the on-call documentation.

• In a mentor-reviewed simulation, 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.
• As a second supervised exercise, 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.
• Under supervision, the team moved 83 manually managed cloud resources into reviewed Terraform modules; I supported research preparation, validation, and documentation under mentor 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.