Denver, COremote

Salary
$80–$90/hrfrom the description
Posted
Jul 28, 2026
Location
Denver, CO
Last confirmed open
Jul 29, 2026

What this job asks for AI summary

A remote W2 contract role supporting Phase 2 of a Manufacturing Traceability program in the life sciences sector. The engineer will design and build GCP infrastructure using Terraform Cloud to underpin AI and data analytics workloads, including data ingestion pipelines, reusable infrastructure templates, and regulated manufacturing environments. The position requires deep hands-on expertise in GCP services and infrastructure-as-code, with collaboration across data, analytics, and cloud platform teams.

Senior level · 13+ years · Remote · Contract

Must have (16)
TerraformTerraform CloudGCPBigQueryDataplexDatastreamVPCKubernetesCloud RunGitHubGitHub ActionsArgoCDCloud DeployCloud SpannerdbtIAM
Nice to have (5)
SnowflakeMongoDBCloud SQLBackstage or RoadieGemini

“or” means any one of them counts — you don't need all of them.

Posted 11 times — it's one opening, so apply once.

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 1,200 people nationally plausibly meet what this posting asks for (software developers). range 250–1,800

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.

What gives you an edge
dbt4%IAM7%BigQuery8%Terraform11%GCP13%

Rare in this occupation — lead with these, and say what you built with them.

What won't set you apart
GitHub Actions40%

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). This posting is about at that midpoint.

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 29, 2026. It is a model, not a headcount.

Why we read it this way (8)

The title reads 'Senior Staff' — a compound level not matching a single standard band. The advertised level is treated as Senior based on the 'Senior' modifier; the actual requirements (13+ years, broad architectural scope) also support Senior on the career ladder, not Staff or Principal, as the JD is a staffing-firm posting without evidence of org-wide technical authority.

The 13+ years figure appears under 'Experience Requirements' but is qualified with 'preferred', so it is treated as a strong preference rather than a hard gate; however, it is used to set the role-level experience floor.

GitHub Runners is listed alongside GitHub in the JD; it is captured under GitHub Actions as the canonical name for GCP-adjacent runner-based CI/CD, since 'GitHub Runners' is not a separately marketed product.

Backstage and Roadie are listed as interchangeable options in the JD ('Backstage or Roadie') and are captured as a single skill with an alternative.

Cloud Run and serverless VMs are listed together; Cloud Run is captured as the named GCP product. Generic 'serverless' and 'VMs' are not emitted as standalone skills.

Regulated industry experience is explicitly called 'a plus' in the JD and is not captured as a named technology skill.

SOC confidence is Medium: the role writes substantial infrastructure-as-code (pointing to 15-1252 Software Developers) but also has significant infrastructure operations and administration duties (pointing to 15-1244). The code-shipping emphasis on Terraform, GitOps, and reusable templates tips the classification to 15-1252.

Posting is for a contract engagement — the market benchmarks below price full-time roles, so read the comp comparison with that in mind.

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.

Apply

Apply on employer site ↗