DevOps Engineer - Remote
yo ai labsPhoenix (AZ)
DevOps Engineer - Remote
Posted yesterday
yo ai labsPhoenix (AZ)
SENIORITY
Senior
About the role
Job Description:
DevOps Engineer Role Type: Contractor Location: RemoteJob Overview We are seeking experienced DevOps Engineers to create and evaluate production-style infrastructure and automation tasks for next-generation AI systems. You will work on CI/CD, Kubernetes, infrastructure as code, Linux, and cloud environments while ensuring solutions are accurate, reproducible, and technically sound. No prior AI experience is required—your DevOps expertise and engineering judgment are what matter most.
Key Responsibilities:
Design realistic DevOps tasks covering CI/CD, containers, Kubernetes, IaC, monitoring, and incident response.
Create working reference solutions with clear setup and validation steps.
Review AI-generated solutions, identify failures, and provide precise technical corrections.
Maintain high standards for correctness, reliability, and reproducibility.
Provide structured feedback to improve AI-generated DevOps workflows.
Required Skills:
KubernetesTerraformCI/CDPythonLinuxDockerGitCloud Platforms Infrastructure as Code
Required Qualifications:
3+ years of professional experience in DevOps, SRE, Platform, or Infrastructure Engineering.
Strong coding skills in Python, Go, Bash, or TypeScript.
Hands-on experience with CI/CD tools such as GitHub Actions, GitLab CI, or Jenkins.
Practical experience with Docker, Kubernetes, and at least one major cloud platform.
Infrastructure as Code experience with Terraform, Ansible, Pulumi, or Cloud
Formation.
Advanced Linux and Git skills. Strong written and spoken English.
Availability of at least 20 hours per week.
Preferred Qualifications:
Experience with Prometheus, Grafana, Datadog, or Open Telemetry. Background in security, secrets management, or platform reliability. Open-source contributions or technical writing experience. Previous experience with AI training data or model evaluation.
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.