Riverside, CAremote

Salary
$5,000from the description
Posted
Jul 5, 2026
Location
Riverside, CA
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A senior-level infrastructure role focused on modernizing a multi-cloud environment, with GCP as the primary target platform. The work centers on replacing over-engineered systems — including Kubernetes clusters — with lighter serverless runtimes like Cloud Run and AWS ECS, migrating infrastructure-as-code from Terraform to Pulumi, and building robust CI/CD pipelines via GitHub Actions. Suits an experienced, self-directed engineer comfortable owning infrastructure end-to-end with minimal oversight.

Senior level · 5+ years · Remote · Contract

Must have (7)
GCPAWSPulumi or TerraformGitHub ActionsDockerKubernetesLinux
Nice to have (5)
GCP Cloud RunAnsibleMySQLDjango, Flask, Celery or ZopeSlack, Jira or Sentry

“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 10,600 people nationally plausibly meet what this posting asks for (software developers). range 6,300–15,900

Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.

What gives you an edge
Pulumi11%Terraform11%GCP13%

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

What won't set you apart
Docker53%Linux45%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 28, 2026. It is a model, not a headcount.

Why we read it this way (10)

This role is based in Latin America and is explicitly restricted to Latin American contractors — the US-based flag is set to false accordingly, even though the caller requested a national remote pool framing.

The posting is structured as an independent contractor engagement (monthly contractor salary) rather than a traditional full-time employment arrangement, despite being described as 'full-time'; employment type is set to Contract.

Pulumi is the stated forward-looking IaC standard, but the JD explicitly accepts candidates with 'expert-level Terraform' who are willing to transition — both are captured as required alternatives of each other.

Kubernetes is listed as required context ('expert-level architectural context') even though the role's explicit goal is to migrate workloads *away* from it; it is retained as a hard gate because the JD places it in the Required Qualifications section.

GCP Cloud Run and AWS ECS appear in the responsibilities narrative and are called out as the target serverless platforms, but they are not explicitly listed under Required Qualifications — marked preferred accordingly.

Ansible appears only in the responsibilities narrative ('Leverages Ansible'), not in the Required Qualifications section — marked preferred.

MySQL, Django/Flask/Celery/Zope, and Slack/Jira/Sentry integrations all appear under Preferred Qualifications — marked preferred.

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

Caller marked this a fully-remote role — scored against the national candidate pool.

This role's work location reads as outside the US — the candidate pool, comp, and contention benchmarks here are US-only (BLS employment, Adzuna/USAJOBS demand, and certified H-1B wages), so treat them as a rough US reference, not a local market.

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 ↗