Cloud Developer AWS

Cloud Developer AWS

• Bachelor's degree in computer science, engineering, information systems, or equivalent. • Hands on AWS experience with ECS Fargate, Lambda, EC2, IAM, RDS, S3, and either EKS or ECS. Working knowledge of VPC and VPC endpoints. • Terraform module consumption. Contribution to shared modules preferred. • Python for automation, including boto3 and AWS SDK or REST API usage. Reusable, tested code, not glue scripts. • GitLab for source control and CI/CD: pipeline authoring, merge reviews, and protected branch workflows. • Experience pairing directly with application or development teams. • Agile/Scrum experience with two week sprints. • One AWS Associate certification (Solutions Architect Associate, Developer Associate, or SysOps Administrator Associate). • Banking or financial services experience. • Experience running or debugging containerized workloads in ECS Fargate or EKS in production. • Exposure to any AWS reliability service, for example Resilience Hub, Fault Injection Simulator, backup and restore, or cross region DR. • Basic AWS cost awareness: reading a cost report, understanding tagging for cost allocation. • SQL sufficient to query a cloud inventory or cost dataset. • Experience teaching, mentoring, or leading pair programming, brown bags, or workshops. • Comfortable writing docs that reduce future tickets. The CORE Engineer is a hands on cloud developer embedded with application teams across the full cloud lifecycle: initial migration, day two operations, and ongoing reliability improvements. The primary job is pair programming with cloud champions inside app teams, using the Terraform modules, pipelines, and platform services already provisioned by the Cloud Infra Engineering, Cloud Automation, and Cloud Platform teams. • Pair programming with app teams to build their first cloud MVP on AWS, using enterprise Terraform modules and GitLab pipelines. Transfer knowledge; do not create dependency. • Hands on AWS work across ECS Fargate, Lambda, EC2, IAM roles, RDS, S3, EKS, SNS and SQS, and API Gateway. Working knowledge of VPC and VPC endpoints is sufficient; the network foundation is owned by Cloud Platform and Security. • Terraform: consume enterprise modules confidently, and contribute improvements back to Cloud Infra Engineering via merge requests when a pattern is missing. • GitLab: author and maintain CI/CD pipelines (Trupipeline), run merge reviews, and onboard app teams onto the enterprise SDLC. GitLab is the primary source of record. • Python automation with boto3 and AWS APIs: build reusable tools that wrap AWS services into simpler, safer, developer friendly workflows. Turning repeat manual tasks into a small Python utility is the default response, not the escalation. • Reliability enablement: working knowledge of Resilience Hub, AWS Fault Injection Simulator, and Application Recovery Controller, OR the ability to automate them via boto3 so app teams can consume them without deep AWS expertise. Either path is acceptable; both is preferred. • Labs and office hours: contribute to hands on labs, cover the daily office hours rotation, and convert repeat questions into docs or lab content. • Dojo engagements: run dedicated 4 to 6 week engagements with app teams new to cloud, walking them through architecture, forecast, labs, and their first path to prod.