Entry-level Infrastructure Engineer resume example

• With a senior colleague reviewing the change, defined AWS networking in Terraform with separate ingress, application, and data tiers; tested route tables and least-privilege security groups before allowing service traffic.
• Within an assigned workstream, 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.
• Within the assigned scope, reconciled cloud IAM policies with service ownership, tested workload identity in staging, and removed unused access only after checking scheduled-job dependencies.
• Within the assigned scope, owned an AWS workload-identity migration using Terraform plans, removed 28 unused cloud keys and completed service-by-service rollback checks before rotation.
• Within the assigned scope, built Python observability checks for Kubernetes and database connectivity, resolved silent networking failures and published a tested troubleshooting runbook.

• The team built utilization reports and automated rightsizing for 74 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 implemented workload identity and removed 126 long-lived cloud keys; 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

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