Define workload-specific architecture, security, reliability, performance, cost, sustainability, automation, and operational ownership. Then compare every candidate with the same job-related scorecard and evidence standard.
Start with the role, evidence, and evaluation criteria.
To hire AWS developers, first define the exact workload, architecture, ownership boundaries, and risks the person will inherit. Evaluate candidates against workload-specific architecture, security, reliability, performance, cost, sustainability, automation, and operational ownership, using a consistent work sample and anchored scorecard instead of treating a technology keyword as proof of production ability.
Do not treat AWS as one role. Specify whether the need is application development, cloud architecture, DevOps, data, serverless, security, migration, or platform engineering and name the services the person will own.
Adjust weights to the workload, then define observable evidence for each rating before sourcing begins.
| Competency | What to examine | Evidence to request |
|---|---|---|
| Architecture | Workload, services, boundaries, tradeoffs | Design review against stated requirements |
| Security | Identity, network, data, secrets | Least-privilege and threat scenario |
| Reliability | Failure modes, recovery, observability | Incident and recovery exercise |
| Operations | IaC, delivery, cost, performance | Evaluate a proposed production change |
Do not treat AWS as one role. Specify whether the need is application development, cloud architecture, DevOps, data, serverless, security, migration, or platform engineering and name the services the person will own.
The role brief should name the production environment, team interfaces, first ninety-day outcomes, and who owns incidents, security review, migrations, and technical decisions.
Use a neighboring role page when the primary ownership boundary differs. Link clusters by decision need so search engines and buyers can distinguish each page's purpose.
Most teams hiring AWS engineers also need orchestration frameworks, container deployment, and automated pipeline tooling.
RELATED STACK
BROWSE ALL ROLES
Direct answers for role scope, technical assessment, adjacent roles, and compensation research.
A useful job description names the product or platform, current architecture, ownership boundaries, first ninety-day outcomes, and operational responsibilities. For AWS developers, explicitly cover workload-specific architecture, security, reliability, performance, cost, sustainability, automation, and operational ownership. Separate essential evidence from preferences, and identify which decisions the hire owns independently versus which require specialist or team review.
Prioritize capabilities tied to the live workload rather than a long keyword list. The scorecard should cover Workload, services, boundaries, tradeoffs, Identity, network, data, secrets, Failure modes, recovery, observability, and IaC, delivery, cost, performance. Weight each area according to business risk, then define observable strong, mixed, and insufficient evidence before candidate interviews begin.
Use a short work sample based on a sanitized version of the real job, followed by a structured discussion of choices and tradeoffs. Ask every candidate the same core questions. Score the submitted artifact, reasoning, verification, failure handling, security, and communication separately, then record evidence before making an overall recommendation.
Do not treat AWS as one role. Specify whether the need is application development, cloud architecture, DevOps, data, serverless, security, migration, or platform engineering and name the services the person will own. Make that distinction explicit in the title, scorecard, sourcing criteria, and interview plan before sourcing begins.
Cost depends on location, employment model, seniority, domain, scope, and the market date. Use current local compensation sources and recent comparable roles, document every assumption, and show a dated range rather than a universal average. Add platform or recruiting fees separately so hiring teams can compare total cost consistently.
