San Francisco, CAremote

Salary
$133,000–$184,000from the description
Posted
Jul 10, 2026
Location
San Francisco, CA
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

This infrastructure engineering role sits within a small platform team responsible for the systems that data engineers depend on daily. The work spans two main areas: deploying and maintaining workflow orchestration environments (Airflow, Flink) and owning core database infrastructure (DynamoDB, RDS). Day-to-day responsibilities include writing Terraform, managing Kubernetes workloads in production, and collaborating with data engineering teams to build reliable, scalable foundations.

Mid level · 2+ years · Remote · Full-time

Must have (4)
TerraformKubernetesAWSPython, Go, Java or Scala
Nice to have (3)
AirflowFlinkETL pipelines

“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 16,700 people nationally plausibly meet what this posting asks for (software developers). range 10,000–25,100

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

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 (7)

The JD states '2–4 years of software engineering experience' — this maps to Mid-level. The title carries no seniority label, so the title states no level.

The role writes infrastructure-as-code, builds deployment platforms, and ships production systems (Airflow/Flink environments, storage infra), making 15-1252 Software Developers the best fit over 15-1244 (ops/admin). Medium confidence because the role also has a meaningful operational/DBA dimension (DynamoDB, RDS ownership, capacity planning).

Python is listed as 'Python or a similar language' in the requirements section — alternatives populated with common substitutes; the requirement itself is a hard gate.

Airflow and Flink appear in the responsibilities narrative describing what the team builds, not in a dedicated requirements or preferred section. They are treated as preferred/stack context rather than hard gates.

ETL/data ingestion experience is explicitly called 'a strong plus' — treated as preferred.

The caller has declared this fully remote; the posting itself describes an in-office policy (4 days/week) for those near an office, but also references a 'fully remote program.' Remote=true per caller instruction.

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 ↗