Roles · City · 2026
DevOps Engineer Jobs in San Francisco: The 2026 Hiring
A DevOps engineer in 2026 is no longer one job. San Francisco shows 328 active DevOps engineer postings on LinkedIn as of May 2026 (Source: LinkedIn Jobs), and 798 senior DevOps engineer postings in the broader Bay Area (Source: LinkedIn Bay Area). Underneath that count, the role has fragmented into three structurally different jobs, with three different comp bands. Candidates who treat them as one job leave money on the table and end up in the wrong seat.
San Francisco DevOps engineer snapshot, May 2026
| Metric | SF Market (May 2026) |
|---|---|
| Active DevOps engineer postings (LinkedIn, SF) | 328 (Source: LinkedIn) |
| Senior DevOps engineer postings (LinkedIn Bay Area) | 798 (Source: LinkedIn Bay Area) |
| All DevOps postings on LinkedIn (SF, broader title) | 1,000+ (Source: LinkedIn) |
| Glassdoor postings count, SF | 87 (Source: Glassdoor Jobs) |
| Average salary, Glassdoor SF | $183,092 (Source: Glassdoor Salaries) |
| Pay band, Glassdoor 25th–75th percentile | $148,404 – $228,811 |
| Average salary, ZipRecruiter SF | $148,342 (Source: ZipRecruiter Salaries) |
| Pay band, ZipRecruiter 25th–75th percentile | $124,300 – $170,200, top 10% at $193,809 |
| Built In SF total comp average | $196,890 ($174,390 base + $22,500 cash) (Source: Built In SF) |
| Senior DevOps engineer average | $208,089 (Glassdoor) / $174,561 (ZipRecruiter) |
| Junior DevOps engineer average (ZipRecruiter) | $84,592 |
We built Standout because the application-driven search is broken for senior tech professionals, and the DevOps search is one of the worst examples of it. Three different roles share one job title, the salary anchors disagree by $35K on the same metro, and the boards do nothing to help a candidate tell them apart. Here is how to read the SF market in 2026, and where the actual openings sit.
What "DevOps engineer" actually means in 2026 (and why it stopped being one job)
The original DevOps role, circa 2012–2018, was the engineer who bridged the gap between writing code and running it in production. CI/CD pipelines, deploy tooling, on-call infrastructure, configuration management. One person, one job, one title.
That role has split.
The split has been pushed by three forces: cloud-native infrastructure made traditional sysadmin work obsolete, the SRE movement formalized reliability engineering as its own discipline, and the platform engineering movement made internal developer platforms a product domain. By 2026, what used to be one "DevOps engineer" requisition now shows up under three different titles, often inside the same company, with different comp bands and different hiring managers.
The hot take: a candidate searching only "DevOps engineer" in San Francisco is missing roughly half the real openings. The job they want may be under "Platform Engineer," "Site Reliability Engineer," or "Infrastructure Engineer." Same skillset. Different title. Sometimes +$30K base depending on which label the company picked.
The three jobs hiding inside "DevOps engineer jobs san francisco"
The 328 LinkedIn listings are not 328 of the same job. They are three structurally different roles sharing one search query.
| Track | What they actually own | Comp band signal | What the JD looks like |
|---|---|---|---|
| Pure DevOps / build-and-deploy | CI/CD pipelines, deployment tooling, release engineering, build infra, IaC for individual product teams | $130K–$180K base, total comp $150K–$220K | JD heavy on Jenkins, GitHub Actions, Terraform, Helm, Kubernetes. Reports into engineering or a shared infra group. |
| Platform engineering / SRE | Internal developer platform, reliability SLOs, observability stack, capacity planning, paging on production incidents | $180K–$260K base, total comp $250K–$400K | JD names SLOs, error budgets, observability platforms (Datadog, Grafana, Honeycomb), on-call rotation. Reports into platform/infrastructure. |
| Cloud infrastructure / staff infra | Multi-region architecture, networking, security, cost optimization at scale, custom orchestration | $220K–$300K base, total comp $400K–$700K at the staff/principal level | JD names AWS/GCP/Azure at multi-region scale, kernel, networking, custom orchestrators. Reports into platform leadership or directly into CTO at smaller orgs. |
The hot take: at most companies above Series C, the title "DevOps engineer" has been retired for the senior and staff seats, replaced by Platform Engineer, SRE, or Infrastructure Engineer. The "DevOps engineer" requisitions that remain are usually mid-level pipeline work or are sitting at companies that have not updated their org chart. Either is fine. Just be aware which one you are walking into before the comp conversation.
The 2026 SF market by the numbers
LinkedIn shows 328 DevOps engineer postings in San Francisco, with a broader 1,000+ when the search expands beyond the exact title (Source: LinkedIn Jobs). The Bay Area count for senior DevOps roles alone is 798 (Source: LinkedIn Bay Area). Glassdoor shows a more conservative 87 (Source: Glassdoor Jobs). The gap between aggregators is the title fragmentation problem we just described.
On compensation, the data sources disagree by enough to matter in a negotiation. Glassdoor reports SF average at $183,092 with a 25th–75th band of $148,404–$228,811 (Source: Glassdoor Salaries). ZipRecruiter reports a SF average of $148,342 with a $124,300–$170,200 25th-to-75th band and a 90th percentile at $193,809 (Source: ZipRecruiter). Built In SF lands at $174,390 base plus $22,500 in additional cash, total comp $196,890 (Source: Built In SF). PayScale shows $146,355 (Source: PayScale_Engineer/Salary/d0dd6700/San-Francisco-CA)).
That spread, $146K to $228K depending on the source, is not random. It tracks the title fragmentation almost exactly. ZipRecruiter pulls heavily from job aggregator listings, where the "DevOps engineer" title skews toward mid-level pipeline work. Glassdoor pulls more from employee-submitted salaries, which over-index on senior platform engineering roles still labeled DevOps in the comp database. Built In SF sits in the middle because it samples Bay Area tech-company listings specifically.
Anchoring at the Glassdoor 75th percentile ($228K base) is right at a platform engineering team at a Series C scaleup. Anchoring there at a Series A startup looking for a DevOps generalist will end the conversation. The right anchor depends on tier.
Where the real DevOps and platform teams sit in San Francisco
The SF DevOps market splits cleanly along stage and company maturity:
- Hyperscaler / public tech (Meta, Google, LinkedIn, Salesforce, Cloudflare SF): Almost no "DevOps engineer" titles remain at the senior level. The work is split between SRE, Platform Engineering, and Production Engineering, with deep specialization. Total comp at the staff and principal levels lands at $400K–$700K depending on company and level. This is where DevOps-origin engineers who specialized into reliability or platform end up.
- Scaleups, Series C through pre-IPO (Stripe, Databricks, Notion, Linear, Ramp, Vercel, Figma, Perplexity, Anthropic SF): Active DevOps and platform hiring. Stripe shows roughly 110 open SF roles across engineering, Databricks shows roughly 152 open SF roles (Source: BuiltInSF Top Companies). Most senior infra titles here are "Infrastructure Engineer" or "Platform Engineer," but the underlying work is what most candidates mean when they say DevOps. Total comp clusters at $250K–$400K with equity that frequently turns liquid.
- Series A and B startups under $50M ARR: "DevOps engineer" titles are most common here, often as the first or second infra hire. The work is broad: CI/CD plus IaC plus on-call plus cost optimization plus security hardening, all on one person's plate. Base lands $140K–$190K with meaningful but illiquid equity. Worth taking if the company is on a credible growth trajectory and the candidate wants end-to-end ownership of the production stack.
- Seed-stage YC and pre-seed: Mostly contract or fractional DevOps work, often via consultants billed at $300/hour-plus through firms like Robert Half. Full-time DevOps hires this early are rare and usually a sign of premature scaling.
The hot take: the credible SF DevOps and platform engineering market is roughly 25 to 35 real teams, plus a long tail of "DevOps engineer = first infra hire" titles at sub-$50M-ARR startups. The aggregator counts compress all four tiers into one number. The candidate's job is to split them back apart before applying.
Five filters that strip the noise from any SF DevOps listing
Five signals, used in order, cut 328 listings down to the maybe 30 worth a serious conversation:
- 1Posted more than 60 days ago, no edits, no new applicants visible. Stale or ghost listing. Skip.
- 2The JD is a tool list, not a problem statement. Real platform engineering JDs describe what is broken about the current production stack and what the role will fix. JDs that read like a Kubernetes ecosystem TOC ("AWS, GCP, Terraform, Pulumi, Helm, ArgoCD, FluxCD, Crossplane, Backstage, Istio, Linkerd...") usually mean the team does not know what they want, or wants a sysadmin titled DevOps.
- 3Cloud spend not mentioned anywhere. At any company over $20M ARR, cloud spend is a material line item, and platform engineering owns a slice of it. A JD that does not mention cost, scale, or efficiency is selling a build-and-deploy job at a senior comp band. Mismatch.
- 4No SLO, error budget, or on-call structure mentioned in JD or interview loop. A senior platform or SRE role without a stated reliability framework is a junior pipeline role wearing a senior title.
- 5Compensation anchor below the ZipRecruiter floor ($124K). Below this in SF, the role is junior, remote-arbitraged, or mislabeled. Stop scrolling.
The candidates who close the most platform engineering offers in 2026 do not scroll job boards. They identify the 25 to 35 real platform teams in SF, hit each careers page directly, and supplement with one matched-introduction service that compresses the timeline from weeks to days.
What top-of-band DevOps and platform compensation actually looks like in SF
Senior DevOps engineer base salary in San Francisco averages $174,561 on ZipRecruiter and $208,089 on Glassdoor (Source: Glassdoor Senior). Re-titled as Platform Engineer or SRE at the same level, base climbs another $20K–$40K. Total comp for senior platform engineers at SF scaleups reaches $300K–$400K with equity. At the hyperscaler tier, staff-level platform engineering total comp reaches $400K–$700K, concentrated at Google, Meta, Stripe, Cloudflare, and the larger AI infrastructure orgs.
Below the Glassdoor 25th percentile ($148K base), expect roles that are either junior, fully remote with SF anchoring, or sitting at a company where DevOps is treated as an operations cost line rather than an engineering investment. None of these are bad jobs. They are different jobs from what the senior platform engineering market pays.
Junior DevOps engineers in SF average $84,592 (Source: ZipRecruiter Junior). The honest framing for an early-career candidate: target the broader infrastructure track (SRE, platform, infra) at a scaleup over a "DevOps engineer" title at a Series A. The ceiling is higher, the discipline progression is clearer, and the comp curve is steeper.
How to find the right DevOps or platform engineering job in San Francisco
Three paths, ranked by efficiency.
1. Direct to careers pages of the credible team list. The scaleup tier (Stripe, Databricks, Notion, Linear, Ramp, Vercel, Figma, Perplexity, Anthropic SF, Cloudflare) plus the hyperscalers with SF infra hiring (Google, Meta, Salesforce, LinkedIn). Bookmark the pages, filter by Platform Engineer, SRE, Infrastructure Engineer, and DevOps simultaneously, set alerts.
2. Reverse-search the engineering blogs. Real platform and SRE teams publish: incident retrospectives, internal platform postmortems, cost optimization writeups, multi-region migration stories. A 30-minute scan identifies the 25 to 35 SF teams worth applying to and surfaces the specific managers and ICs to reach out to.
3. Get matched directly to the hiring teams. Standout exists because the application funnel is broken for senior tech talent, and DevOps and platform engineering is where the title fragmentation makes board searching especially noisy. Standout candidates report first matches arriving within hours of profile completion, with direct intros to the founder or hiring lead at the matched company. No cold applications. No keyword games against an ATS that does not know whether your last role was DevOps, platform, or SRE.
Three things to know about how Standout works for SF DevOps and platform candidates:
- Free for candidates. Placement-fee model on the company side only.
- All tech roles, seed through Series D. DevOps, platform, SRE, and infrastructure engineers are a meaningful slice of the candidates we represent, and the same matching mechanism runs across product, design, data, ML/AI, engineering, marketing, sales, ops, customer success, and business development.
- First matches in hours, not days. Profile to first matched company is hours, not weeks.
From the matches Standout has run with hiring companies across US tech, the modal SF platform engineering requisition closes from a list of three to seven pre-vetted candidates, most of whom were not running an active job search when the role landed in front of them. The hiring managers we work with describe it as "the inverse of LinkedIn," a single intro from a vetted source beats fifty inbound applications they will never read.
Learn how Standout matches candidates to companies. For the broader market view, see San Francisco roles on Standout.
FAQ
How much do DevOps engineers make in San Francisco?
Glassdoor reports an average of $183,092 with a 25th–75th percentile band of $148,404–$228,811 (Source: Glassdoor). ZipRecruiter shows an average of $148,342 with a 90th percentile at $193,809 (Source: ZipRecruiter). Built In SF lands at $196,890 total comp (Source: Built In SF). The spread reflects three different roles sharing one job title.
What's the difference between DevOps, SRE, and Platform Engineering?
DevOps as originally defined was the engineer who bridged code and production: CI/CD, deploys, on-call. SRE formalized reliability as its own discipline with SLOs, error budgets, and explicit reliability targets. Platform engineering treats the internal developer platform as a product, with engineers as customers. In 2026 the comp bands rank Platform Engineering and SRE above pure DevOps, even when the day-to-day work overlaps significantly.
How many DevOps engineer jobs are open in San Francisco right now?
LinkedIn shows 328 DevOps engineer postings in SF and 1,000+ across all related infrastructure titles in the metro (Source: LinkedIn). Senior DevOps engineer postings in the Bay Area total 798 (Source: LinkedIn Bay Area). Glassdoor shows a more conservative 87 (Source: Glassdoor).
Which San Francisco companies are actively hiring DevOps and platform engineers?
The scaleup tier with active SF infra hiring includes Stripe (roughly 110 open SF roles), Databricks (roughly 152 open SF roles), Notion, Linear, Ramp, Vercel, Figma, Perplexity, Cloudflare, and Anthropic. Hyperscaler infra hiring concentrates at Google, Meta, LinkedIn, and Salesforce. The credible team count in the metro is roughly 25 to 35 (Source: Built In SF).
Should I take a "DevOps engineer" title at a Series A startup, or wait for a Platform Engineer title at a scaleup?
Depends on what the candidate is optimizing for. The Series A DevOps role offers end-to-end ownership of the production stack, broader scope, and meaningful but illiquid equity. The scaleup platform engineering role offers higher comp, clearer discipline progression, and equity that more often turns liquid. Career compounding in infrastructure tends to favor specialization, which favors the scaleup track over the long run.
Find the SF DevOps or platform engineering job worth taking. [Build your Standout profile](https://standout.work) and we will match you to the right infrastructure teams across US tech. First matches in hours. Free for candidates. No applications.