Senior DevOps Engineer
Duetto Research
—
Jul 26, 2026
—
Jul 27, 2026
What this job asks for AI summary
A senior infrastructure role focused on designing, building, and maintaining the AWS-based systems that underpin a SaaS revenue management platform serving the hospitality industry. Day-to-day work spans cloud architecture, infrastructure-as-code with Terraform/Terragrunt, CI/CD pipelines, observability tooling, and participation in an on-call rotation. Suits an experienced DevOps or SRE engineer comfortable owning infrastructure decisions end-to-end and collaborating closely with development teams.
Senior level · 5+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 3,600 people nationally plausibly meet what this posting asks for (software developers). range 1,500–5,400
Applicant volume Light — Few people clear these requirements, so an application that does clear them gets looked at. Worth applying to even if you miss a nice-to-have.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
SOC classification is a genuine judgment call: the posting emphasizes architecting, building, and owning infrastructure with IaC (Terraform/Terragrunt), CI/CD pipelines, and GitOps — work that ships tooling and automation code — which points to 15-1252 Software Developers. However, the heavy AWS ecosystem administration, on-call operations, and monitoring focus also fit 15-1244. 15-1252 was chosen as primary because the role is explicitly asked to 'architect and build' rather than primarily operate existing systems.
AWS is listed as preferred with Azure/GCP accepted as alternatives ('AWS preferred, Azure or GCP also welcome'); marked as a hard gate on cloud infrastructure capability with alternatives captured accordingly.
Terraform and Terragrunt are listed together as a single requirement ('Terraform/Terragrunt in production'); Terragrunt is captured as an alternative since either satisfies the IaC requirement.
Chef and Puppet are listed as interchangeable ('Chef or Puppet'); one skill emitted with the other as an alternative.
DataDog, Prometheus, and Grafana are listed as interchangeable monitoring options; DataDog is the primary with the others as alternatives.
Individual AWS service names (IAM, VPC, EC2, RDS, S3, Lambda, CloudWatch, etc.) are all listed explicitly in the requirements section. ELB, API Gateway, Secrets Manager, KMS, and CloudTrail were also named but are sub-services/features of the broader AWS ecosystem already captured; the most distinct named services are included.
The language list (Java, Ruby, Bash/Zsh, HCL, Python, JavaScript) is framed as 'read well enough to move fast' — a reading/comprehension bar rather than deep expertise, but it appears in the requirements section so it is marked as required. HCL is the configuration language for Terraform and is already implied by the Terraform requirement; it is omitted as a standalone skill to avoid redundancy.
ECS/EKS and SOC2 appear under the 'Strong candidates may also have' section, making them preferred rather than required.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.