Which AWS services have you worked with?

What the interviewer wants to learn

  • The breadth and depth of your cloud experience.
  • Whether you’ve used services that are relevant to the role.
  • How comfortable you are with AWS’s ecosystem and terminology.
  • Your ability to pick the right tool for a given problem.

How to structure your answer

1. **Brief overview** – State the number of years or projects where you used AWS.

2. **Categorize services** – Group them (compute, storage, database, networking, security, analytics, DevOps, etc.).

3. **Highlight key projects** – For each category name one or two services you used and what you built with them.

4. **Show impact** – Mention any measurable outcome (cost reduction, performance gain, reliability improvement).

5. **Tie to the role** – End by linking the experience to the responsibilities of the job you’re applying for.

Example answer

“Over the past three years I’ve built and operated several production‑grade applications on AWS. For compute I mainly used EC2 for custom Linux workloads and ECS/Fargate for containerized microservices, which let us scale automatically during traffic spikes. Our data lives in S3 for object storage, with Glacier for long‑term archival, and we use RDS (PostgreSQL) for relational data and DynamoDB for a high‑throughput key‑value store. To handle messaging we set up SQS queues and SNS topics, and for monitoring we rely on CloudWatch dashboards and X‑Ray tracing. I also scripted deployments with CloudFormation and later moved to Terraform for IaC. These services together helped us cut infrastructure costs by about 20 % while improving uptime to 99.95 %.”

Mistakes to avoid

  • **Listing services without context** – “I’ve used EC2, S3, Lambda…” without explaining what you did with them sounds superficial.
  • **Over‑inflating experience** – Claiming deep knowledge of a service you only touched once can be exposed in follow‑up questions.
  • **Getting too technical or too vague** – Balance detail (e.g., “used CloudFormation to create VPCs, subnets, and autoscaling groups”) with a clear business outcome.
  • **Ignoring relevance** – Focus on services that matter to the job description; don’t spend time on obscure services unless they’re directly applicable.
  • **Neglecting security and best practices** – Mention IAM roles, encryption, or compliance if they were part of your work; omitting them can suggest a gap in responsible cloud usage.

More technical concept questions