Free template · 2026

Cloud Engineer Job Description Template

A ready-to-use Cloud Engineer job description for 2026, with the interview scorecard and questions to hire one. Copy it as is or customize it free in about 15 seconds.

Includes the job description, an interview scorecard and questions for every round.

Mid-level in Latin America
$4,500/mo
Same role in the US
$11,875/mo
You save
Up to 62%

All-in monthly cost, 2026 rates.

Job description template
Copy text

Cloud Engineer

Build, operate, and improve reliable cloud infrastructure that supports the company’s applications and services across environments. You’ll work independently on well-defined work, collaborating with engineering and operations to deliver secure, observable, and cost-conscious cloud capabilities.

Responsibilities

  • Design and deploy cloud infrastructure components (networks, compute, storage, and supporting services) using infrastructure-as-code
  • Manage reliability through monitoring, alerting, and incident response support, including root-cause analysis and post-incident improvements
  • Implement security best practices across cloud resources (identity, access controls, encryption, and secure configuration)
  • Create and maintain standardized deployment and runtime patterns to improve repeatability and reduce operational overhead
  • Optimize cloud cost and performance by analyzing usage, identifying bottlenecks, and applying targeted improvements
  • Collaborate with software engineers to ensure smooth integration of services into cloud environments
  • Maintain and evolve documentation for infrastructure, runbooks, and operational procedures

Must-have qualifications

  • Hands-on experience deploying and operating AWS infrastructure in production
  • Proficiency with infrastructure-as-code (e.g., Terraform or CloudFormation) for repeatable provisioning
  • Working knowledge of cloud networking concepts (VPC, subnets, routing, security groups/NACLs)
  • Experience implementing observability (logging/metrics/tracing) and alerting practices for cloud systems
  • Strong understanding of IAM and secure access patterns in AWS
  • Ability to troubleshoot production issues and support reliability improvements based on evidence

Nice to have

  • Experience with container platforms (e.g., ECS or EKS) and common operational workflows
  • Familiarity with CI/CD integration for infrastructure or application delivery
  • Knowledge of cloud cost optimization practices and tooling

What success looks like in 12 months

  • Infrastructure is delivered reliably via infrastructure-as-code
  • Cloud environments are secure by default
  • Observability improves operational responsiveness
  • Operational stability improves through proactive reliability work
  • Cloud cost and performance are optimized based on measurable results

Logistics

  • Full-time (40 hours a week), remote from Latin America.
  • Working hours overlap with US business hours.

About the company

[About your company: what you build, your stage and team size]

Want it tailored to your stack, seniority and time zone?

Customize with the free generator →
Interview scorecard

Score every candidate against the same bar

Deliver secure, observable, and cost-conscious AWS infrastructure that improves reliability and enables teams to ship with confidence.

Outcomes to measure

What this hire should deliver in the first year. Replace [N] with your own targets.

  • Infrastructure is delivered reliably via infrastructure-as-code. Measure: Maintain [X]% successful infrastructure provisioning runs with no critical manual changes required for standard environments
  • Cloud environments are secure by default. Measure: Reduce high-severity access/configuration findings by [X]% across AWS accounts/environments
  • Observability improves operational responsiveness. Measure: Increase alert signal-to-noise by [X]% and reduce time-to-identify incidents by [X]%
  • Operational stability improves through proactive reliability work. Measure: Reduce production incident count by [X]% and/or reduce repeat incidents for the same root cause by [X]%
  • Cloud cost and performance are optimized based on measurable results. Measure: Lower monthly cloud spend by [X]% (or achieve [X]% improvement in cost-per-request) while maintaining agreed performance and reliability targets

Competencies and weights

What to evaluate, how much it counts and what a strong answer looks like.

AWS Production Expertise · 22%
Core requirement for operating and improving AWS environments independently in production. Evaluated in Round 1.

  • Weak: Can describe AWS services but struggles to connect them to production architecture, deployment, or operational decisions.
  • Meets the bar: Builds and supports AWS resources using sound patterns; can explain the operational impact of key configuration choices.
  • Strong: Designs and operates AWS production setups end-to-end, including tradeoffs, failure modes, and recovery strategies.

Infrastructure as Code · 20%
Ensures repeatable provisioning, reduces drift, and supports reliable delivery of infrastructure changes. Evaluated in Round 2.

  • Weak: Uses IaC inconsistently or requires guidance for state, plans, and safe change practices.
  • Meets the bar: Writes and maintains IaC modules/templates with safe change workflows and manages state appropriately.
  • Strong: Builds maintainable IaC patterns (modules, environments, testing/checks) that minimize drift and enable frequent iteration.

Networking and Security Groups · 16%
Networking correctness and security boundaries are required for secure, stable service connectivity. Evaluated in Round 1.

  • Weak: Has limited understanding of routing, subnetting, and security boundary behavior.
  • Meets the bar: Can design and debug VPC/networking and security group/NACL rules for expected connectivity.
  • Strong: Anticipates connectivity and security edge cases, and can quickly isolate misconfigurations impacting traffic flows.

IAM and Secure Access · 16%
IAM mistakes are high-risk; the role must implement secure identity and access patterns. Evaluated in Round 2.

  • Weak: Cannot consistently explain permission boundaries and least-privilege implications.
  • Meets the bar: Implements least-privilege IAM and secure access patterns; understands role assumptions and policy structure.
  • Strong: Proactively designs secure access models (roles, policies, boundaries, auditing) that prevent privilege escalation and support operations.

Observability and Alerting · 13%
Operational excellence depends on actionable telemetry and effective alerting. Evaluated in Round 3.

  • Weak: Sets up basic logs/metrics but struggles to translate telemetry into actionable alerts.
  • Meets the bar: Designs dashboards and alerts aligned to service health and incident workflows.
  • Strong: Establishes end-to-end observability (logs/metrics/tracing where applicable), reduces alert fatigue, and improves diagnosis speed.

Production Troubleshooting · 13%
Independently resolves production issues and drives reliability improvements based on evidence. Evaluated in Round 3.

  • Weak: Relies on guesswork or requires extensive guidance to debug incidents.
  • Meets the bar: Uses monitoring/telemetry and systematic investigation to identify and remediate production problems.
  • Strong: Performs high-quality root-cause analysis, identifies contributing factors, and implements durable preventative changes.
Interview questions

Questions for every interview round

Each round has an owner, a time box and questions that test the competencies above.

Round 1: AWS architecture fundamentals
Cloud Engineering Lead · 60 min

  1. Describe an AWS production architecture you deployed. What were the key components and the specific reasons you chose that design?
  2. Walk through a networking problem you debugged in production (connectivity, routing, or security rules). How did you isolate the cause and validate the fix?
  3. How do you decide what belongs in which subnet/security boundary when deploying a new service? Share an example decision and its tradeoffs.

Round 2: Infrastructure-as-code and security
Senior Cloud Engineer · 60 min

  1. Tell me about an infrastructure-as-code change you delivered safely. How did you manage state, review plans, and reduce risk during rollout?
  2. Describe how you structure IaC for multiple environments (dev/stage/prod). What conventions help prevent drift and mistakes?
  3. Explain an IAM design you implemented using least privilege. How do you handle permissions for service-to-service access and operational needs?
  4. Share an example where you improved security posture (encryption, access controls, secure defaults). What evidence showed the improvement?

Round 3: Reliability, observability, and incident response
Site Reliability Engineer · 60 min

  1. Describe your approach to observability for cloud systems. What telemetry do you prioritize and how do you tie it to operational actions?
  2. Tell me about an alerting strategy you built or improved. How did you reduce noisy alerts while preserving coverage?
  3. Walk me through a production incident you helped resolve. What signals did you use, what was the root cause, and what durable changes did you implement to prevent recurrence?

Red flags to watch for

  • Over-reliance on manual changes with limited IaC discipline or inability to discuss drift/state management
  • Vague explanations of IAM/least-privilege or inability to reason about security boundaries in AWS
  • Limited ability to connect telemetry to incident diagnosis and prevention (e.g., cannot describe concrete monitoring/alerting improvements)
  • Troubleshooting examples that do not include evidence-based investigation and post-incident remediation

How much does it cost to hire a Cloud Engineer in Latin America?

In 2026, a senior Cloud Engineer in Latin America costs $6,750 to $7,750 a month all-in, versus $14,625 in the US: up to 54% less. Mid-level starts at $4,500.

Country

Mid-level

Senior

Argentina

$4,500

$6,750

Brazil

$5,000

$7,500

Colombia

$4,500

$6,750

Mexico

$5,250

$7,750

United States

$11,875

$14,625

Monthly cost in USD, all-in: the talent's salary plus Teilur's flat 20% fee, from our 2026 rates. The United States row shows what the same role typically costs there.

Compare costs in the calculator →

Frequently asked questions

What does a Cloud Engineer do?

Typical responsibilities include: design and deploy cloud infrastructure components (networks, compute, storage, and supporting services) using infrastructure-as-code; manage reliability through monitoring, alerting, and incident response support, including root-cause analysis and post-incident improvements; implement security best practices across cloud resources (identity, access controls, encryption, and secure configuration). The full list is in the template above.

How much does it cost to hire a Cloud Engineer in Latin America?

In 2026, a senior Cloud Engineer in Latin America costs $6,750 to $7,750 a month all-in, versus $14,625 in the US: up to 54% less. Mid-level starts at $4,500.

Can I customize this Cloud Engineer job description?

Yes. Teilur's free Job Description & Scorecard Generator rewrites it for your stack, seniority, time zone and hiring urgency in about 15 seconds. No sign-up needed.

More free hiring tools

Keep going with the rest of your hire.

See all free tools →

Need to fill this role?

Teilur shortlists pre-vetted Cloud Engineers from Latin America in about 5 days. Flat 20% of what you pay, no subscription.