Cloud Engineer Expert

About the role

<p>Cloud engineers to build the infrastructure and automation scenarios frontier AI labs use to test model judgment.</p>

<p>AfterQuery builds the expert evaluation data that frontier AI labs use to measure and improve their models. We're hiring cloud engineers as contractors to author and grade the infrastructure and automation scenarios those evaluations run on.</p>

<p><strong>What you'll actually do</strong></p>

<ul><li>Author realistic cloud scenarios, from architecture design through incident response</li><li>Write reference answers with the architectural reasoning behind each decision</li><li>Grade model output for correctness, security, and cost efficiency</li><li>Flag configurations that read plausible but would fail or overspend in production</li></ul>

<p><strong>Who this is for</strong></p>

<ul><li>Engineers with at least 2 years of cloud engineering on AWS, Azure, or GCP</li><li>Practitioners with hands on infrastructure as code experience such as Terraform or CloudFormation</li><li>Engineers with depth in at least one area such as networking, containers, serverless, or cost optimization</li><li>Clear writers who can document the reasoning behind an architectural decision</li></ul>

<p><strong>Contract and pay</strong></p>

<ul><li><strong>$85 to $165/hr</strong>, paid weekly via Stripe. Your rate is set from your experience, not negotiated down after you start.</li><li>Fully remote, fully async. No fixed hours.</li><li>Minimum 10 hours per week, no maximum. Scale up or down week to week.</li><li>No screen recording, no keystroke monitoring, no idle timers.</li><li>Independent contractor. Ongoing project work rather than single task batches.</li></ul>

Why apply

• $85 to $165/hr, paid weekly via Stripe
• 100% remote and fully async
• Shape how frontier models reason about cloud infrastructure
• Ongoing project work with hours you set each week

Responsibilities

• Author realistic cloud scenarios from architecture design through incident response
• Write reference answers with the architectural reasoning behind each decision
• Grade model output for correctness, security, and cost efficiency
• Flag configurations that read plausible but would fail or overspend in production

Required qualifications

• 2+ years of professional cloud engineering experience on AWS, Azure, or GCP
• Hands on infrastructure as code experience with Terraform, CloudFormation, or similar
• Depth in at least one area such as networking, containers, serverless, or cost optimization
• Clear written English for documenting architecture and operational reasoning
• Able to commit at least 10 hours per week

Preferred qualifications

• Certifications such as AWS Solutions Architect, Azure Administrator, or GCP Professional
• Kubernetes and container orchestration experience
• Multi cloud or large scale migration experience