Already filled

Don't miss the next one. Get matching roles delivered to your inbox.

Cloud Architect

Job summary

Lansing

Work model

Hybrid · 3 days home
1 month ago
Job description

Interview Process

In-person interviews (will likely be held between 5/25-5/29)

Hybrid Work Schedule

  • Hybrid: Resource will be working a hybrid schedule. NO REMOTE ONLY OPTION.
  • Will need to be onsite from day 1, two days a week.

Required Qualifications

  • 5-6+ years hands-on experience building and operating production workloads on AWS, with deep knowledge of Elastic Beanstalk, EKS, EC2, RDS, VPC, IAM, S3, CloudWatch, and Secrets Manager
  • 3+ years hands-on with Kubernetes - production EKS preferred, including Helm, kubectl, ingress (ALB/NGINX), HPA, and troubleshooting pods/services/networking
  • Production experience with ArgoCD or Flux - designed app-of-apps structure, managed multi-environment promotion, and resolved GitOps drift in real workloads. This is non-negotiable.
  • Strong Azure DevOps Pipelines (YAML) experience - build pipelines, multi-stage release pipelines, variable groups, service connections, and self-hosted/Microsoft-hosted agents. Equivalent strong experience in another major CI/CD tool (GitHub Actions, GitLab CI, Jenkins) is acceptable if Azure DevOps can be picked up quickly
  • Solid Docker skills - multi-stage builds, image hardening, ECR
  • Infrastructure-as-Code in production: Terraform (preferred) or CloudFormation/CDK
  • Database familiarity - comfortable working with DBA teams on RDS (SQL Server and PostgreSQL), connection strings, secrets rotation, and migration cutover
  • Linux administration (RHEL/Amazon Linux/Ubuntu) and shell scripting (bash)
  • Source control with Git - branching strategies, pull requests, code review discipline
  • Strong written communication - must produce clear runbooks, architecture diagrams, and PR descriptions