Los Angeles, CAremote

Salary
$170,000–$205,000from the description
Posted
Jul 16, 2026
Location
Los Angeles, CA
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A broad, cross-cutting engineering role responsible for cloud infrastructure, Kubernetes platform operations, CI/CD and GitOps pipelines, security patterns, and data platform tooling — primarily on Google Cloud Platform. The work spans building reusable infrastructure components, improving developer experience, supporting observability, and providing architectural guidance across multiple engineering teams. Best suited to a generalist staff-level engineer comfortable owning complex problems across the full stack rather than a single specialty.

Staff level · 10+ years · Remote · Full-time

Must have (10)
GCP, AWS or AzureTerraformKubernetesDockerGitHub ActionsArgo CDPython or Shell ScriptingCI/CDGitOpsobservability
Nice to have (10)
SentryHelmPostgreSQLdbtBigQuerySnowflakeAirflowGKEKafkaPub/Sub

“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 2,250 people nationally plausibly meet what this posting asks for (software developers). range 950–3,400

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
Terraform11%

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

What won't set you apart
Docker53%Python51%CI/CD45%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 (9)

The role is explicitly titled and framed as Staff Software Engineer, and the requirements support that level: 10+ years of experience, cross-domain technical ownership, architectural guidance across multiple teams, and org-wide impact — genuine Staff scope.

GCP is listed as the preferred cloud platform under the required section ('preferably on Google Cloud Platform'); it is treated as a hard gate on cloud infrastructure experience, with GCP as the named primary. AWS and Azure are listed as alternatives since the JD uses 'preferably' to indicate GCP is the strong preference but not an absolute exclusive gate.

Python and Bash are presented as interchangeable scripting options ('Python or Bash') in the requirements section; Python is listed as the primary with Bash as the alternative.

Observability is listed as a required capability (metrics, logs, traces, alerting, dashboards, SLOs, incident response); specific tools — OpenTelemetry, Prometheus, Grafana, Sentry — appear in the responsibilities narrative ('such as … or similar systems') rather than the hard requirements block, so they are marked preferred.

Helm, Argo CD, and GitHub Actions all appear in the required section; Helm also appears in the Nice to Have section but its first mention is in the required responsibilities, so it is retained as preferred given the 'Nice to Have' section explicitly calls it out as a bonus signal — however, GitHub Actions and Argo CD are firmly in the required block and are marked required.

All data platform tools (dbt, BigQuery, Snowflake, Airflow, Kafka, Pub/Sub, PostgreSQL) appear either in the responsibilities narrative or the explicit 'Nice to Have' section; none are gated in the 'You Must Have' block, so all are marked preferred.

GKE, Workload Identity Federation, Artifact Registry, Cloud Run, Cloud Functions, and related GCP services are listed under 'Nice to Have' and are marked preferred.

The posting states the role is not eligible for immigration sponsorship and is remote within most US states (with some exclusions); no specific excluded states are named.

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

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 ↗