Cloud Engineer 2 - (AWS, Terraform, CloudFormation)
$232k-$284k
Apply (opens in a new tab)Cloud Engineer 2 - (AWS, Terraform, CloudFormation)
Posted yesterday
SENIORITY
Lead
SALARY
$232k-$284k
About the role
- This team is focused on providing cloud-based geolocation solutions in near-real-time directly to decision makers and warfighters around the world.
- Migrate applications to cloud environments
- Configure and maintain cloud infrastructures using tools such as Terraform and Cloud
- FormationTroubleshoot issues and identify root cause analysis
- Generate after action reports to include new requirements and improved Tier 1 SOPsUse ActiveMQ and/or Kafka
- Support deployment strategies for high-availability systems
- Design, implement, and maintain cloud infrastructure (e.g., modernization, migration, roadmaps, etc.), ensuring that systems are designed and maintained following best practices and governance requirements
- Build reusable modules (e.g., Helm Charts, Terraform, etc.) and enforce development standards for creation and maintenance of Infrastructure as Code (IaC)
- Continuously monitor the health and performance of the infrastructure and systems using logging and alerting, identify issues and implement solutions for improved efficiency
- Provide strategies for failure/recovery (e.g., backup, high-availability, etc.), cost optimization (e.g., tagging, budgets, rightsizing, autoscaling, etc.) and benefit analysis of cloud services
- Participate in continuous improvement initiatives to enhance system capabilities and efficiency
- Contribute to deliverables (e.g., architectures, runbooks, and operational procedures) and performance metrics, where applicable, and provide knowledge transfer to internal teams
- Stay abreast of emerging technologies and recommend enhancements to current systems
- Experience provisioning, configuring, and managing cloud infrastructure and services (e.g., compute, storage, networking, IAM)
- Experience designing and implementing secure, scalable cloud architectures
- Experience developing and maintaining Infrastructure as Code (IaC) using tools such as Terraform, Cloud
- Formation, AWS CDK, etc.
- Knowledge of container and platform workloads (e.g., Docker, Kubernetes/EKS/AKS/GKE)
- Experience configuring monitoring, logging, and alerting using tools such as CloudWatch, Prometheus/Grafana, ELK/OpenSearch, etc. and responding to incidents
- Experience implementing and testing backup, disaster recovery, and high-availability strategies
- Experience managing secrets and key management with tools such as KMS/KeyVault/Secret Manager, certificates, and rotation policies
- Experience optimizing cloud cost and performance (e.g., tagging, budgets, rightsizing, autoscaling) and producing usage/cost reports
- Experience troubleshooting cloud infrastructure issues across networking (DNS, routing, VPN), security, and service limits
- Experience documenting architectures, runbooks, and operational procedures
- Experience with Linux OSCLENG2 Qualifications:
- Six (6) years' experience in software development/engineering in programs and contracts of similar scope, type, and complexity, including at least four (4) years of experience in software development on systems utilizing cloud-related technologies is required
- Bachelor's degree in Computer Science, Engineering or related discipline from an accredited college or university is required. Four (4) years of additional experience in software development/engineering on projects with similar software processes may be substituted for a bachelor's degree.
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.
