AWS Cloud Engineer (Serverless / Lambda)

Job Description

AWS Cloud Engineer (Serverless / Lambda)

\n

Location: 100% remote

\n

Salary: 125-150k

\n

\n

We’re looking for a hands-on AWS engineer to build, deploy, and support serverless APIs and cloud infrastructure. AWS is the team’s primary cloud platform, and Lambda sits at the center of the work. The team builds APIs with AWS SAM and CloudFormation, deploys through GitHub Actions, and manages infrastructure with Terraform.

\n

The most important skill for this role is troubleshooting. When something breaks, you’ll be the person who can trace the problem across both the application code and the AWS infrastructure underneath it and get things running again.

\n

\n

What You’ll Do

\n

\n
• Build and maintain serverless applications and APIs using AWS Lambda
\n
• Develop and deploy APIs using AWS SAM and CloudFormation
\n
• Maintain and improve CI/CD pipelines in GitHub Actions
\n
• Work within existing Terraform stacks to manage and update infrastructure
\n
• Design and support REST APIs and middleware integrations between systems
\n
• Diagnose and resolve production issues across application and infrastructure layers
\n
• Support containerized workloads on ECS as needed
\n

\n

\n

Required Skills

\n

\n
• Strong, hands-on AWS experience in a production environment
\n
• AWS Lambda. Deep, practical experience building and running Lambda-based applications.
\n
• AWS SAM and CloudFormation for building and deploying APIs
\n
• CI/CD with GitHub Actions
\n
• APIs and integration. Solid understanding of REST APIs and middleware patterns.
\n
• Infrastructure as Code. Working familiarity with Terraform. You don’t need to be an expert, but you should be comfortable reading and updating existing configurations.
\n
• Strong troubleshooting skills across application code and AWS infrastructure, especially under pressure
\n

\n

\n

Preferred Skills

\n

\n
• Containerization and Amazon ECS experience
\n
• General familiarity with AWS security best practices (deep security expertise is not required)
\n

\n