AWS Engineer Job Description Template (2026)

Last updated: August 26, 2026

A lot of AWS engineer job descriptions read like a service catalog. EC2, S3, Lambda, VPC, IAM, RDS, all listed in one long paragraph with no indication of which ones actually matter for the role or how deep the candidate needs to go with each. That approach doesn’t filter anything. It attracts everyone who has touched the AWS console once and repels the engineers who could tell, from a vague JD, that nobody on the hiring side has thought carefully about what this role actually needs to do.

This template fixes that. It’s built from the job descriptions that have actually produced strong nearshore AWS engineer placements, not a generic list pulled from a certification syllabus.

Why Most AWS Engineer JDs Attract the Wrong Candidates

Two problems show up constantly. First, the JD lists every AWS service the company has ever touched as a “requirement,” which filters out strong candidates who are honest about not having deep experience with all fifteen listed services, while attracting candidates who claim familiarity with all fifteen and have shallow experience with most of them.

Second, the JD says nothing about what the engineer will actually be doing day to day. “Manage AWS infrastructure” could mean running a Well-Architected cost review for a Series B startup or maintaining a single EC2 instance for an internal tool. Candidates can’t self-select accurately against vague scope, so you end up interviewing people who aren’t a fit and losing people who are, because the JD didn’t tell them enough to know they should apply.

The 7 Sections Every AWS Engineer JD Needs

1. Role summary (3 to 5 sentences)

What does this engineer own, and why does the role exist right now? Name the specific trigger: a migration, a cost problem, a team that’s grown past what the current infrastructure owner can maintain alone.

2. Primary responsibilities (5 to 8 bullet points)

Specific, not generic. “Design and maintain Terraform modules for our multi-account AWS Organizations setup” tells a candidate more in one line than “manage cloud infrastructure” tells them in a whole paragraph.

3. Required technical skills

The 3 to 5 things a candidate absolutely cannot lack. For most mid-to-senior AWS roles, this is core compute and networking (EC2, VPC, IAM), at least one infrastructure-as-code tool (Terraform or CloudFormation), and a specific database or storage service relevant to your stack.

4. Preferred technical skills

The differentiators. EKS experience, multi-account governance, cost-optimization work, a specific compliance framework. These separate a strong candidate from an exceptional one, but shouldn’t disqualify someone who’s missing one or two.

5. Experience level definition

Don’t say “senior.” Say what senior means for your environment: has independently designed a production VPC, has led an incident postmortem, has managed infrastructure at a specific account or spend scale.

6. Collaboration and communication expectations

Will this person carry a pager? Attend daily standups? Write architecture decision records? State it. This is the section most JDs skip entirely, and it’s the one that prevents the worst post-hire surprises.

7. Engagement model and compensation range

Contract, contract-to-hire, or direct hire? A real range, not “competitive.” Candidates increasingly skip listings that hide this, and it wastes fewer hours for both sides when it’s stated upfront.

Required vs. Preferred: How to Split AWS Skills

The single most common JD mistake is putting everything in “required.” Here’s a working split for a mid-to-senior AWS infrastructure role:

Adjust this split based on your actual environment. A team running a single-account EC2 setup doesn’t need to require multi-account Organizations experience. A team already on EKS shouldn’t treat container orchestration as optional.

Experience Level Definitions That Work

“5+ years of AWS experience” tells you almost nothing about capability. Here’s a framework based on what the engineer has actually owned, not tenure:

• Junior (1-3 years): Has deployed and maintained infrastructure following existing patterns and Terraform modules someone else designed. Comfortable with EC2, S3, and basic IAM. Needs review on networking and security changes.
• Mid-level (3-6 years): Has independently designed a VPC, written production Terraform modules from scratch, and handled at least one significant incident. Comfortable making IAM and networking decisions with light review.
• Senior (6-10 years): Has led a Well-Architected Framework review, owns account-level cost strategy, has designed disaster-recovery architecture, and mentors less experienced engineers. Makes architecture decisions independently.
• Lead/Architect (10+ years): Owns multi-account governance strategy, sets infrastructure standards across teams, and has led at least one major migration or replatforming effort end to end.

Adapting the JD for Nearshore AWS Hiring

A few adjustments matter specifically for a nearshore AWS engineer JD. State the time zone expectation directly: “Costa Rica-based candidates working core hours aligned to US Central/Eastern time.” This filters correctly without excluding qualified candidates who happen to be in a different country.

Add an explicit English communication requirement tied to the actual work: “Must be able to write clear incident postmortems and participate in live architecture discussions in English,” not just “fluent English required,” which candidates interpret inconsistently.

State the on-call structure clearly. If the role includes rotation into a live incident-response schedule, say so, including roughly how many days per month. Ambiguity here creates the most post-hire friction.

Complete AWS Engineer Job Description Template

Job Title: AWS Cloud Infrastructure Engineer (Mid-to-Senior)
Location: Remote, Costa Rica-based, core hours aligned to US Central/Eastern
Engagement: Contract-to-hire, 6-month conversion window

Role Summary: We’re looking for an AWS engineer to own infrastructure design and reliability for our production environment as we scale from a single-region deployment to a multi-region architecture. You’ll work directly with our engineering team, not a managed services desk, and will be expected to make independent architecture decisions within defined guardrails.

Responsibilities: Design and maintain Terraform modules for VPC, compute, and data layer infrastructure. Participate in on-call rotation (approximately 1 week in 4). Lead quarterly Well-Architected Framework reviews. Own IAM policy design and least-privilege access reviews. Collaborate with application engineers on deployment pipeline design. Write clear incident postmortems and architecture decision records.

Required: 4+ years hands-on production AWS experience. Independent VPC and IAM design experience. Terraform or CloudFormation proficiency. Experience with RDS or equivalent managed database services. Clear written and spoken English for live incident communication.

Preferred: EKS or ECS experience. AWS Certified Solutions Architect or SysOps Administrator. Multi-account AWS Organizations experience. Cost-optimization or FinOps background.

Compensation: $4,800 to $8,500/month all-inclusive, based on experience level.

Common AWS JD Mistakes That Shrink Your Candidate Pool

Listing every AWS service the company has ever used. If your app touches 20 different services, that doesn’t mean the new hire needs deep expertise in all 20 on day one. Pick the 4 or 5 that matter most for the first six months.

Requiring a specific certification instead of the underlying skill. “Must hold AWS Certified Solutions Architect” filters out excellent engineers who never got around to scheduling the exam despite having the actual capability. Make certifications preferred, not required, unless a client contract specifically mandates them.

Omitting the on-call reality. If the role includes real incident response responsibility, hiding that until the offer stage produces declined offers and wasted interview cycles. State it in the JD.

No compensation range. AWS engineers, especially senior ones with multiple offers in flight, increasingly skip listings without a range. It costs you candidates you’d otherwise have gotten a call with.

Frequently Asked Questions

Disclosure: Kore BPO is a nearshore and offshore staffing agency. This template reflects patterns from job descriptions that have produced successful AWS engineer placements for our clients.