Fictional resume example. Names, employment histories and results are illustrative, not an actual employee record.
Zachary Palmer
Infrastructure Engineer with experience in platform reliability, capacity, automation, security, and developer velocity. Practical work includes Cloud IAM, Workload identity, Access reviews, Capacity planning.
Experience
JPMorgan Chase
Jersey City · United States
Infrastructure Engineer
Mar 2022 - now
- Defined AWS networking in Terraform with separate ingress, application, and data tiers; tested route tables and least-privilege security groups before allowing service traffic.
- 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.
- Reconciled cloud IAM policies with service ownership, tested workload identity in staging, and removed unused access only after checking scheduled-job dependencies.
- Owned an AWS workload-identity migration using Terraform plans, removed 28 unused cloud keys and completed service-by-service rollback checks before rotation.
- Built Python observability checks for Kubernetes and database connectivity, resolved silent networking failures and published a tested troubleshooting runbook.
Datadog
New York · United States
Infrastructure Engineer
Jan 2019 - Feb 2022
- Built utilization reports and automated rightsizing for 74 workloads. Kept the lower-effort process in place after handoff.
- 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.
- 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.
Selected project
Infrastructure Engineer — independent case study
Project owner
Feb 2024 - Jun 2024
- Implemented workload identity and removed 126 long-lived cloud keys
- 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.
Education
University of Washington
Seattle, Washington · United States
B.S. Computer Science
Sep 2013 - Jun 2017
Relevant coursework: Algorithms, operating systems, databases, computer networks
Skills
Role expertise
Cloud IAM · Workload identity · Access reviews · Capacity planning
Certifications
AWS Certified Solutions Architect – Associate
Amazon Web Services
Jun 2024
Publications
- 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.

