AWS Cloud Services Engineer
AWS Cloud Services Engineer
Posted today
SENIORITY
Senior
About the role
- AWS services (EC2, S3, RDS, Lambda, VPC, Route 53, Kubernetes)
- Infrastructure as Code: Terraform, Cloud
- FormationTroubleshooting Linux/Windows systemsAWS CLI, scripting (Python, Bash, PowerShell)AWS certifications (Solutions Architect preferred)
- Automation experience in relevant technologies and tools
- Candidate should be willing to do Application Support on rotation as needed by the customer
- Knowledge on JIRA
- Candidate should be hands-on and experienced to support AWS infrastructure, networking, cloud automation, and platform performance.
- He/She should be able to independently provide application support, code, test, debug, and deploy the code.
- Must be proficient and have automation experience in relevant technologies and tools.
- Candidate should be willing to do Application Support on rotation as needed by the customer.
- Candidate should be local to Dallas, 5 days onsite, no remote option.
- Good interpersonal skills
- Good communication/presentations skills
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
