Staff Platform Engineer, Service Infrastructure
Together AI · San Francisco, CA
$240,000–$280,000from the description
Jul 10, 2026
San Francisco, CA
Jul 21, 2026
What this job asks for AI summary
A staff-level infrastructure role embedded within a product engineering organization that owns API, web UI, billing, and identity platforms. The work centers on defining and improving service infrastructure patterns — covering Kubernetes, Terraform, networking, and cloud operations — and translating repeated problems into reusable tooling, standards, and frameworks shared across teams. Suits a senior engineer comfortable leading cross-functional technical initiatives and shaping infrastructure strategy hands-on.
Staff level · 7+ years · San Francisco-Oakland-Berkeley, CA · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 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 200 people in the San Francisco-Oakland-Berkeley, CA area plausibly meet what this posting asks for (software developers). range 100–260
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
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 $190,744 (middle half $167,095–$224,501). 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 role is a genuine hybrid between software/platform engineering (building reusable primitives, Helm charts, Terraform modules, GitOps workflows) and infrastructure/systems operations (networking, CDN, DNS, load balancing). 15-1252 was chosen because the JD emphasizes building and owning reusable infrastructure code and driving technical direction, rather than primarily operating existing systems.
Location is not explicitly stated in the posting; Together AI is headquartered in San Francisco, CA, and the role is described as full-time with no remote option mentioned, so the SF Bay Area CBSA is assumed.
The programming language requirement lists Go, Python, TypeScript, or similar — these are presented as interchangeable options for infrastructure tooling; Go is used as the primary with the others as alternatives.
GitHub Actions is listed in the responsibilities section as part of 'GitHub Actions/GitOps workflows' — it appears as a concrete named tool in the context of required deliverables, so it is treated as required.
Route 53, CloudFront, and ECR appear under the AWS bullet in the Requirements section but are framed as 'ideally including' — this softening language within an otherwise required bullet warrants treating them as preferred rather than hard gates.
Service mesh / zero-trust tools (Istio, Linkerd, Cilium, Envoy, SPIFFE/SPIRE) and policy-as-code tools (OPA, Gatekeeper, Kyverno, Sentinel) are listed explicitly under 'Nice to Have'.
Observability (metrics, logs, traces, dashboards, alerting, SLOs) is required per the JD but names no specific tool or platform, so it is omitted from the skills list per extraction rules.
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.