Internship Infrastructure Engineer resume example

• Under supervision, reconciled cloud IAM policies with service ownership, tested workload identity in staging, and removed unused access only after checking scheduled-job dependencies.
• The team created self-service environments from reviewed modules and policy checks; I supported research preparation, validation, and documentation under mentor review. The team removed the longest wait from the end-to-end workflow; confirmed with my mentor that my contribution was limited to the assigned support and validation work.
• The team migrated 19 services to multi-zone scheduling with disruption budgets; 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 an AWS workload-identity migration using Terraform plans, removed 28 unused cloud keys and completed service-by-service rollback checks before rotation.
• Under supervision, built Python observability checks for Kubernetes and database connectivity, resolved silent networking failures and published a tested troubleshooting runbook.

• In a mentor-reviewed simulation, defined AWS networking in Terraform with separate ingress, application, and data tiers; tested route tables and least-privilege security groups before allowing service traffic.
• As a second supervised exercise, added cloud configuration automation with drift reports and recovery checks. Used flow logs for troubleshooting to distinguish DNS, routing, and application failures during a restore exercise.
• Under supervision, the team implemented workload identity and removed 126 long-lived cloud keys; 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

• 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.