Peoria, IL or Irving, TX | Onsite
Estimated Start Date: November 30, 2026
Location: Peoria, IL or Irving, TX office
Work Arrangement: Onsite full time
Schedule: Monday–Friday, first shift
Duration: 12 months

Position’s Contributions to Work Group

Position’s Contributions to Work Group:
We design, provision, and operate the AWS infrastructure that business units use for data, serverless, and container workloads, so application teams can build on secure, standard foundations. As a customer-facing platform team, we work directly with business units to understand their needs and turn them into reliable AWS environments.

Typical Day or Week in the Role

Typical task breakdown:
Provision and operate the infrastructure for data and serverless services: S3, Glue, Lambda, API Gateway, Step Functions, EventBridge, and DynamoDB.
Build, upgrade, and maintain EKS clusters and ECS/Fargate environments.
Automate infrastructure delivery with reusable CloudFormation templates and GitHub Actions pipelines.
Design and troubleshoot VPC networking, load balancers, IAM, KMS, and cross-account access.
Onboard new business unit environments, estimate costs, and provide production infrastructure support.
Act as a technical point of contact for business unit customers by guiding requirements, setting clear expectations, and resolving issues quickly.

Candidate Requirements

Education & Experience Required:
Bachelors degree required
5-7 years experience in this capacity
AWS Certification is required.( AWS Certified Solutions Architect)

Required Technical Skills
(Required)
Hands-on experience building and operating AWS infrastructure in a multi-account environment.
Experience provisioning and supporting EKS, ECS/Fargate, Lambda, S3, and Glue.
Strong AWS networking and IAM skills: VPC, ALB/NLB, SCPs, and permission boundaries.
Infrastructure as code with CloudFormation (preferred), plus CI/CD with GitHub Actions.
Scripting in Python and/or Bash for automation.

Soft Skills
(Required)
Strong customer focus and communication skills, including explaining technical options to non-AWS teams