We use technical cookies and Zorky's de-identified visit log. Yandex Metrica (data is stored on servers in Russia) runs only with your consent. We never sell data. More about cookies and statistics.
Zorky is in test mode — everything is free. Jobs and company pages are open to everyone; links to postings and your personal feed open after you sign up. Sign up →

SRE: market

Data as of November 19, 2026: 2,012 open SRE jobs, 29% remote among jobs that state a work format; median advertised salary $10,416/mo (from 246 postings that state a salary). Source: Zorky, updated daily.

Site Reliability Engineer (SRE) — premium role inside the DevOps direction, invented by Google in 2003. Focus: reliability + SLI / SLO / error budgets + incident response + automation to reduce toil. Programming-heavier than general DevOps (Go / Python for automation + custom tooling). Role family: SRE (mid — owns reliability of one service), Senior SRE (multi-service + on-call mastery + SLO architecture), Staff / Principal SRE (org-wide reliability strategy + production engineering culture leadership), SRE Tech Lead (team + reliability roadmap), Production Engineer (alternative title — Facebook / Meta term). Stack 2026: Linux+bash deep mastery (production debugging), Go (standard for SRE automation — Kubernetes + Prometheus + most SRE tooling in Go), Python (data analysis + scripting), Kubernetes mastery (production-scale), Prometheus+Grafana+Alertmanager+VictoriaMetrics+Mimir mastery (metrics deep), Loki+Tempo+OpenTelemetry (logs + traces), Datadog/New Relic/Dynatrace/Splunk (commercial APM), SLI / SLO management (Pyrra / OpenSLO / Sloth — modern SLO-as-code tools), incident response tooling (PagerDuty / Opsgenie / Squadcast / FireHydrant / Rootly / incident.io), chaos engineering (Chaos Monkey / Gremlin / LitmusChaos / Chaos Mesh — for resilience testing), load testing (k6 / Gatling / Locust / JMeter), Terraform/OpenTofu (IaC), ArgoCD/FluxCD (GitOps), service mesh (Istio / Linkerd / Cilium for resilience patterns), distributed systems theory (CAP / consistency models / consensus algorithms basics). Top stack: cloud, sre, python, site reliability, aws. Among jobs with a stated work format, 29% are remote.

Data as of:

Key numbers for the SRE market: open jobs, median salary, observed talent pool and remote share.

2,012
open jobs — by job title, reposts merged
$10,416
median $/mo
29%
remote

The SRE market currently has 2,012 open roles, 1,782 of them freshly observed. Median salary $10,416/mo.

Among jobs with a stated work format, 29% are remote. SRE work is cloud-based standard. Caveat: on-call rotation requires reliable home-office setup. Time zone overlap critical for distributed SRE teams. International tech companies — full-remote standard. Russian banks — hybrid/office compliance.

⚠ salary known for 246 of 2012 jobs; remote share from 1621 with a stated format; 1782 counted as fresh observations; trend and hiring difficulty are not shown

Timeline: postings and sources

How many SRE postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.

New postings per week

Chart data
New postings per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodNew postings per week
2026-06-0159
2026-06-0856
2026-06-1552
2026-06-22118
2026-06-29177
2026-07-06246
2026-07-13265
2026-07-20213
2026-07-27119
2026-08-03171
2026-08-10149
2026-08-17140
2026-08-24129
2026-08-31107
2026-09-07160
2026-09-14159
2026-09-21537
2026-09-28494
2026-10-05306
2026-10-12722
2026-10-19428
2026-10-26411
2026-11-02448
2026-11-09414

Active sources per week

Sources over the period: 191. ▲ — a week with a large batch of new sources.

Chart data
Active sources per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodActive sources
2026-06-0117
2026-06-0819
2026-06-1519
2026-06-2230
2026-06-2946
2026-07-0648
2026-07-1359
2026-07-2054
2026-07-2745
2026-08-0347
2026-08-1040
2026-08-1737
2026-08-2437
2026-08-3133
2026-09-0741
2026-09-1441
2026-09-2155
2026-09-2856
2026-10-0555
2026-10-1261
2026-10-1967
2026-10-2665
2026-11-0266
2026-11-0970
New sources connected: Jun 22 +16 · Jun 29 +24 · Jul 6 +20 · Jul 13 +18 · all weeks (23) in the table
WeekNew sourcesNew postings
Jun 8+856
Jun 15+752
Jun 22+16118
Jun 29+24177
Jul 6+20246
Jul 13+18265
Jul 20+11213
Jul 27+7119
Aug 3+7171
Aug 10+4149
Aug 17+3140
Aug 24+2129
Aug 31+3107
Sep 7+7160
Sep 14+2159
Sep 21+5537
Sep 28+1494
Oct 5+4306
Oct 12+3722
Oct 19+8428
Oct 26+3411
Nov 2+7448
Nov 9+4414

The current week is not over yet and is not shown: an incomplete week would look like a drop.

Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.

Chart data
Timeline: postings and sources — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekNew postings per weekActive sources
2026-06-015917
2026-06-085619
2026-06-155219
2026-06-2211830
2026-06-2917746
2026-07-0624648
2026-07-1326559
2026-07-2021354
2026-07-2711945
2026-08-0317147
2026-08-1014940
2026-08-1714037
2026-08-2412937
2026-08-3110733
2026-09-0716041
2026-09-1415941
2026-09-2153755
2026-09-2849456
2026-10-0530655
2026-10-1272261
2026-10-1942867
2026-10-2641165
2026-11-0244866
2026-11-0941470

Salaries over time

Median SRE salary per week, USD per month.

Median salary, USD per month

Chart data
Median salary, USD per month. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodMedianPostings with a salary per week (n)
2026-08-318,40613
2026-09-07—3
2026-09-148,51110
2026-09-219,50026
2026-09-288,40655
2026-10-058,61739
2026-10-128,68354
2026-10-1910,83377
2026-10-2610,24589
2026-11-029,93866
2026-11-0910,22978

The series starts on Aug 31: there is no data before that.

Postings with a salary per week (n)

Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.

Chart data
Salaries over time — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekMedian
2026-06-01—
2026-06-08—
2026-06-15—
2026-06-22—
2026-06-29—
2026-07-06—
2026-07-13—
2026-07-20—
2026-07-27—
2026-08-03—
2026-08-10—
2026-08-17—
2026-08-24—
2026-08-318,406
2026-09-07—
2026-09-148,511
2026-09-219,500
2026-09-288,406
2026-10-058,617
2026-10-128,683
2026-10-1910,833
2026-10-2610,245
2026-11-029,938
2026-11-0910,229

Remote work over time

Share of SRE postings offering fully remote work, per week.

Remote postings, %

Chart data
Remote postings, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodRemote
2026-06-0139.2
2026-06-0858.1
2026-06-1551.2
2026-06-2243.2
2026-06-2931.1
2026-07-0628.9
2026-07-1339.8
2026-07-2044.6
2026-07-2745.6
2026-08-0333.3
2026-08-1029.7
2026-08-1741.3
2026-08-2427.4
2026-08-3120.3
2026-09-0717.9
2026-09-1424.8
2026-09-2147.8
2026-09-2853.1
2026-10-0539.7
2026-10-1239.5
2026-10-1925.3
2026-10-2638.6
2026-11-0231.5
2026-11-0928.5

The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.

Chart data
Remote work over time — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekRemote
2026-06-0139.2
2026-06-0858.1
2026-06-1551.2
2026-06-2243.2
2026-06-2931.1
2026-07-0628.9
2026-07-1339.8
2026-07-2044.6
2026-07-2745.6
2026-08-0333.3
2026-08-1029.7
2026-08-1741.3
2026-08-2427.4
2026-08-3120.3
2026-09-0717.9
2026-09-1424.8
2026-09-2147.8
2026-09-2853.1
2026-10-0539.7
2026-10-1239.5
2026-10-1925.3
2026-10-2638.6
2026-11-0231.5
2026-11-0928.5

Technologies over time

How the share of SRE postings mentioning each of the top technologies changed.

Postings mentioning the technology, %

Chart data
Postings mentioning the technology, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
Periodsite reliabilitycloudsre
2026-08-1065.722.646
2026-08-177526.749.2
2026-08-2457.521.255.8
2026-08-31804040
2026-09-0775.731.243.1
2026-09-1468.828.447.5
2026-09-2158.731.952.4
2026-09-2857.533.356.3
2026-10-0573.247.149.3
2026-10-127443.847.4
2026-10-1970.250.850.3
2026-10-2669.452.751.6
2026-11-027154.849.8
2026-11-0970.440.244.2
Up to 5 on the chart:

Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.

Chart data
Technologies over time — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
Weeksite reliabilitycloudsreAWSKubernetes
2026-08-1065.722.64612.49.5
2026-08-177526.749.29.216.7
2026-08-2457.521.255.88.813.3
2026-08-3180404016.816.8
2026-09-0775.731.243.16.211.1
2026-09-1468.828.447.521.35.7
2026-09-2158.731.952.438.717.6
2026-09-2857.533.356.342.722.1
2026-10-0573.247.149.329.833.1
2026-10-127443.847.422.226.1
2026-10-1970.250.850.32532.7
2026-10-2669.452.751.631.732.8
2026-11-027154.849.828.838.3
2026-11-0970.440.244.225.329.1

Countries over time

How the share of SRE postings in each of the top countries changed, per week.

Postings in the country, %

Chart data
Postings in the country, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodUSAUKPoland
2026-06-0126.93.838.5
2026-06-0821.65.943.1
2026-06-1520.46.134.7
2026-06-2219.41.934.3
2026-06-2921.95.312.6
2026-07-0637.95.56.4
2026-07-1336.96.96
2026-07-2020.72521.3
2026-07-2718.424.326.2
2026-08-033123.29.2
2026-08-1016.925.44.6
2026-08-1732.431.43.8
2026-08-2422.2352.6
2026-08-3126.940.93.2
2026-09-0719.421.52.1
2026-09-1430.722.99.3
2026-09-2131.46.33.8
2026-09-2820.913.77.7
2026-10-0531.516.512.8
2026-10-1230.410.311.8
2026-10-1927.6136.2
2026-10-2634.311.26
2026-11-0229.414.38.4
2026-11-0928.717.34.9
Up to 5 on the chart:

Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.

Chart data
Countries over time — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekUSAUKPolandIndiaSingapore
2026-06-0126.93.838.55.80
2026-06-0821.65.943.13.92
2026-06-1520.46.134.710.20
2026-06-2219.41.934.33.719.4
2026-06-2921.95.312.611.915.2
2026-07-0637.95.56.49.63.7
2026-07-1336.96.965.16
2026-07-2020.72521.33.29.6
2026-07-2718.424.326.22.94.9
2026-08-033123.29.25.63.5
2026-08-1016.925.44.6104.6
2026-08-1732.431.43.81.92.9
2026-08-2422.2352.63.44.3
2026-08-3126.940.93.21.16.5
2026-09-0719.421.52.112.56.2
2026-09-1430.722.99.36.43.6
2026-09-2131.46.33.87.95.6
2026-09-2820.913.77.74.85.9
2026-10-0531.516.512.87.35.1
2026-10-1230.410.311.882.1
2026-10-1927.6136.29.56.8
2026-10-2634.311.2611.23.3
2026-11-0229.414.38.45.14.6
2026-11-0928.717.34.94.36.2

Clean market: hiring index

The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just SRE.

Hiring index, Oct 16 = 100

Chart data
Hiring index, Oct 16 = 100. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.

Chart data
Clean market: hiring index — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
DayHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

How many open SRE jobs there are and how many matching specialists Zorky observes.

Demand and observed supply

Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
Open demand2,012
Open demand2,012
Observed supply— not published

SRE — premium segment of DevOps with growing demand 2026 driven by: cloud-native production maturity (companies move beyond "deployed K8s" to "production-ready K8s"), microservices distributed-systems complexity, AI/ML infra reliability (LLM serving uptime), regulatory pressure on uptime (banking / fintech / healthcare). Russian — steady flow. EPAM SRE Practice — the largest outsource channel.

⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown

How salaries in SRE jobs are distributed, in US dollars per month.

Salary distribution

P25 $7,250 · P50 $10,416 · P75 $14,583
Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
<$1k2
$1–2k2
$2–3k5
$3–4k4
$4–5k9
$5–6k16
$6–7k18
$7–8k17
$8–9k17
$9–10k14
$10–12k46
$12–15k44
$15–20k43
$20k+9
Salary in postings: base 2,012
  • usable for the calculation: 246 (12.2%)
  • stated but not converted to USD/month: 307 (15.3%)
  • not stated: 1,459 (72.5%)

One in ten postings offers under $5,166, one in ten over $17,916. Half of the postings offer between $7,250 and $14,583. Sample: 246.

Chart data
Salary distribution — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricLower boundUpper boundCount
<$1k01,0002
$1–2k1,0002,0002
$2–3k2,0003,0005
$3–4k3,0004,0004
$4–5k4,0005,0009
$5–6k5,0006,00016
$6–7k6,0007,00018
$7–8k7,0008,00017
$8–9k8,0009,00017
$9–10k9,00010,00014
$10–12k10,00012,00046
$12–15k12,00015,00044
$15–20k15,00020,00043
$20k+20,000—9

Which countries have the most open SRE jobs.

Demand geography

countryjobsshare
United States65338.5%
India1488.7%
United Kingdom1368%
Poland1076.3%
Singapore985.8%
Germany543.2%
France523.1%
Canada452.7%
Australia331.9%
Brazil261.5%
Other countries34420.3%

The leader by SRE job count is the US (653 positions). Poland — SRE-friendly EU hub. Germany — Berlin / Munich tech cluster.

⚠ job counts only: salary by country is not published

Chart data
Demand geography — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
US653
IN148
GB136
PL107
SG98
DE54
FR52
CA45
AU33
BR26

Which technologies are most often required in the same job as SRE.

Used together with

site reliability
1,06052.7%
cloud
88844.1%
sre
61930.8%
aws
53926.8%
python
32716.3%
grafana
31615.7%
azure
30014.9%
go
27513.7%
gcp
25012.4%

Share — how many of the 2,012 jobs in the SRE market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).

Top SRE stack 2026: Linux + bash mastery (production debugging — perf / bpftrace / flamegraphs), Go (standard for SRE tooling — Kubernetes / Prometheus / etcd) or Python deep, Kubernetes mastery (production-scale), Prometheus + Grafana + Alertmanager + VictoriaMetrics + Mimir (metrics deep), Loki + Tempo + OpenTelemetry (logs + traces), Datadog / New Relic / Dynatrace / Splunk (commercial APM), SLO-as-code (Pyrra / OpenSLO / Sloth), incident response tooling (PagerDuty / Opsgenie / Squadcast / FireHydrant / Rootly / incident.io), chaos engineering (Chaos Monkey / Gremlin / LitmusChaos / Chaos Mesh), load testing (k6 / Gatling / Locust / JMeter), Terraform / OpenTofu, ArgoCD / FluxCD, service mesh (Istio / Linkerd / Cilium), distributed systems theory (CAP / consistency models / consensus algorithms).

Common pairs: Kubernetes + Prometheus + Grafana + Alertmanager, Go + Kubernetes operators + custom CRDs, Pyrra + Prometheus + Grafana (SLO-as-code), Chaos Mesh + k6 + Grafana (chaos + load testing), Istio + Prometheus + Tempo (service mesh observability), VictoriaMetrics + Mimir (long-term metrics storage). Learning roadmap: DevOps base → programming (Go / Python) → SRE book + workbook reading → SLO mastery → distributed systems theory (Kleppmann book) → chaos engineering → load testing → incident command → distributed tracing.

Chart data
Used together with — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
site reliability1,060
cloud888
sre619
aws539
kubernetes502
python327
grafana316
azure300
go275
gcp250
ansible230
docker214

How many SRE jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior688
principal208
lead134
middle67
junior53

Junior — rare (typical entry DevOps Middle / Backend Middle → SRE Junior). Career flow: DevOps Middle (2-3 years) → SRE Junior (1-2 years) → Middle (2-3 years) → Senior → either Staff / Principal SRE (deep), Engineering Manager (SRE), Backend Distributed Systems Senior pivot, or specialisation in Chaos Engineering / Performance Engineering.

⚠ demand side only: the grade of the observed pool is unknown for most of it

Chart data
Demand by grade — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior688
principal208
lead134
middle67
junior53

Who hires the most for SRE and how concentrated demand is among the largest companies.

Employers

Demand is spread across 1,212 employers. The largest accounts for 2.2%, the top ten for 8.8%; the remaining 91.1% is long tail.

largest 2.2%2nd–3rd 2.5%4th–10th 4.1%the rest 91.1%
sharevalue
top-12.2%
top-34.7%
top-108.8%
long tail91.1%

⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier

Which company sites and job boards Zorky collects SRE jobs from.

Where Zorky sees this market

Observed across 94 sources; the largest accounts for 22.2% — this market does not rest on a single channel.

Chart data
Where Zorky sees this market — SRE. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
atsATS и карьерные сайтыATS & career sites1,3740.6829
boardджоб-борды и агрегаторыjob boards & aggregators5530.2749
telegramTelegramTelegram790.0393
communityсообщества и публичные профилиcommunity & public profiles60.003

The newest SRE jobs from company career sites.

Recent openings

All jobs →

Latest open SRE jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.

How this is measured
Vacancy
an open job that cleared the quality gate and lists at least two technologies
Observed candidate
a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
Matchable candidate
not counted yet
Window
jobs open at the moment the snapshot was built

About the data

  • Some breakdowns are hidden: their data coverage is not yet sufficient.
  • Statistics are shown only where the sample clears a quality gate.
  • A missing block does not mean a value of zero.

Breakdowns currently hidden: 8.

Direction: DevOps / SRE

Related specializations

Inside SRE: SRE (mid — owns reliability of one service), Senior SRE (multi-service + on-call mastery + SLO architecture), Staff / Principal SRE (org-wide reliability strategy + production engineering culture), SRE Tech Lead (team + reliability roadmap), Production Engineer (Meta / Facebook equivalent title). Comparison with devops/cloud/kubernetes/devsecops/platform/infrastructure — in the bar below.

Cloud EngineerDevSecOpsInfrastructure EngineerKubernetes / ContainerPlatform Engineer

Frequently asked questions

Answers recompute automatically.

What does an SRE Junior, Middle, Senior, or Lead earn?

Junior SRE — rare (typical entry: DevOps Middle / Backend Middle + interest in reliability). The Junior → Middle jump — after the first production incident resolution + the first SLO setup for a service. Middle → Senior — multi-service SLO ownership + on-call mastery (Mean Time to Detect / Recovery metrics ownership) + automation programming at Backend Middle/Senior level. Senior → Staff / Principal — org-wide reliability strategy + production engineering culture leadership + technical mentorship. Career flow: DevOps Middle (2-3 years) → SRE Junior / Middle (1-2 years) → Senior → either Staff / Principal SRE, Engineering Manager (SRE), a move to Backend Distributed Systems Senior, or specialisation in Chaos Engineering or Performance Engineering.

SRE vs DevOps — what's the practical difference (Google distinction + 2026 reality)?

Google's original distinction (Site Reliability Engineering book): DevOps — a culture / philosophy ("break down silos between Dev and Ops"). SRE — a concrete implementation of the DevOps philosophy via specific practices: SLI / SLO / error budgets + toil reduction + automation-first + 50% time on engineering vs operational work + blameless post-mortems. SRE = "what happens when you ask a software engineer to design an operations team". Differences observable at product companies: 1) Programming depth — SRE writes more custom Go / Python tooling (autoscaling logic, deployment automation, capacity planning algorithms). DevOps Engineer more often configures existing tools. 2) SLI / SLO discipline — SRE owns SLO architecture (Pyrra / OpenSLO / Sloth), error budget policy enforcement, alerting tuned against SLO burn rates. DevOps often sets up monitoring without formal SLO. 3) On-call mastery — SRE on regular on-call rotation (24×7 for critical services), stronger in incident command + post-mortem facilitation. DevOps Engineer is usually on-call for own product only. 4) 50% engineering rule — Google policy: an SRE should not spend >50% time on operational work, the rest is engineering automation. DevOps Engineer has no such guard. 5) Distributed systems theory — SRE interviews often include CAP theorem / consensus algorithms / consistency models / failure mode analysis. DevOps interviews — more practical tooling. In startups this differentiation is often blurred (one person = both DevOps and SRE). Google SRE.

What is the SLI / SLO / error budget framework?

SLI (Service Level Indicator) — a measurable metric of service health (availability / latency / error rate / throughput). SLO (Service Level Objective) — a target value for an SLI (e.g. 99.9% availability over 30 days). SLA (Service Level Agreement) — a contractual commitment to customers (usually weaker than the SLO, e.g. 99.5% if SLO is 99.9%, to keep a safety margin). Error budget = 100% − SLO. For time-based availability, a 99.9% SLO over 30 days leaves a 0.1% budget, or 43.2 minutes. For request-based SLOs, the budget is expressed in requests, not automatically in minutes. Google SRE. When the error budget burns fast → freeze new feature deployments, focus the team on reliability work. When the error budget is healthy → ship features aggressively. Practical framework setup (12 steps): 1) Identify customer-facing critical user journeys (CUJs). 2) Pick SLIs for each CUJ (typically availability + latency for synchronous, throughput + freshness for async). 3) Choose the initial SLO target (rule: slightly below current performance). 4) Set up SLI measurement (Prometheus + Grafana or managed). 5) Configure burn-rate alerts (multi-window: fast burn 1h 14.4× rate, slow burn 6h 6× rate — Google formula). 6) Set up SLO-as-code (Pyrra / OpenSLO / Sloth) for version control. 7) Document the error budget policy (what happens at exhaustion — feature freeze? incident review?). 8) Quarterly SLO review (target adjustment based on actual performance + customer impact). 9) Toil tracking + reduction roadmap (target: <50% time on toil). 10) Post-mortem culture — blameless, focus on action items. 11) Chaos engineering integration (Gremlin / Chaos Mesh — pre-test SLO under failure). 12) Customer trust dashboard (public status page — Statuspage / Atlassian / Better Uptime). Google SRE.

What skills and tools does an SRE need?

Linux / systems deep: processes, namespaces, cgroups, networking (TCP/IP, DNS, load balancing), performance debugging (strace / perf / eBPF). Observability stack: Prometheus + Grafana (PromQL deep), distributed tracing (Tempo / Jaeger / OpenTelemetry), logs (Loki / ELK), managed APM (Datadog / Grafana Cloud / Honeycomb) — SRE "sees" the system through metrics. SLO practice: SLI / SLO / error budget (see separate question), burn-rate alerts, SLO-as-code. Incident response + on-call: PagerDuty / Opsgenie, runbooks, blameless post-mortems, severity assessment. Kubernetes: production operations (CKA level) — workloads, networking, troubleshooting. IaC + automation: Terraform / OpenTofu, Ansible; the key SRE skill is reducing toil (manual repeated work) via automation, target <50% of time on toil. CI/CD: safe deploys — canary, blue-green, progressive delivery, rollback. Programming: Python and / or Go at a level of writing maintainable automation tools, not "scripts". Distributed systems: failure modes, retry / timeout / circuit breaker, idempotency, consistency — the foundation for capacity planning and DR. Chaos engineering: Gremlin / Chaos Mesh — verify reliability before the incident. The main point: SRE treats reliability as a product — measures it (SLO), automates routine, and systematically removes causes of incidents instead of putting them out by hand. English is mandatory — the SRE literature (Google SRE book) and the community are English-speaking. Google SRE.

What share of jobs are remote?

Among jobs with a stated work format, 29% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.

How is Production Engineer (Facebook / Meta term) different from SRE?

Production Engineer (PE) — Facebook / Meta's term for SRE. Same discipline, almost identical responsibilities — focus reliability + automation + on-call + capacity planning + distributed systems. The difference is historically philosophical: Google SRE — "a software engineer who happens to do ops", Facebook PE — "an engineer embedded in a product team for reliability". In 2026 practice — almost fully overlapping. Other equivalent titles: Reliability Engineer (LinkedIn), Infrastructure Engineer (often overlaps with SRE), Production Operations Engineer (legacy term). How to read job postings 2026: look for signals in the JD — if it mentions "SLI/SLO", "error budgets", "toil reduction", "50% engineering time", "blameless post-mortems", "on-call rotation" — it's an SRE-style role regardless of title. If it mentions "CI/CD setup", "cloud migration", "infrastructure as code" but WITHOUT SLO mentions — it's general DevOps.

Where to start in SRE in 2026?

Roadmap: 1) DevOps base solid — Linux mastery + Docker + Kubernetes (CKA) + cloud platform deeply + IaC (Terraform). Without this base there's no point going into SRE. 2) Programming Backend Middle level — Go (standard for SRE — Kubernetes / Prometheus / most SRE tooling in Go) or Python deep (data analysis + scripting). Books: "The Go Programming Language" Donovan / Kernighan, "Fluent Python" Ramalho. 3) "Site Reliability Engineering" Google book (free PDF) — must-read, read twice. 4) "The Site Reliability Workbook" Google — practical complement (case studies + exercises). 5) SLI / SLO mastery — set up SLO-as-code (Sloth / Pyrra / OpenSLO) for a real service, configure burn-rate alerts (multi-window: fast 1h 14.4×, slow 6h 6×). 6) Distributed systems theory — CAP theorem, consistency models (linearizability / sequential / causal / eventual), consensus (Paxos / Raft basics), failure mode analysis. Books: "Designing Data-Intensive Applications" Martin Kleppmann (must-read 2026), "Database Internals" Petrov. 7) Chaos engineering — Chaos Mesh / Gremlin / LitmusChaos. Set up chaos experiments on own K8s cluster. Book: "Chaos Engineering" Nora Jones / Casey Rosenthal. 8) Load testing mastery — k6 (modern JS-based, rising) or Gatling (Scala DSL) or Locust (Python). Set up load tests integrated into CI. 9) Observability deep: Prometheus advanced (PromQL mastery + recording rules + federation), Grafana advanced (templating + alerting), Loki + Tempo + OpenTelemetry. Use case: distributed tracing across microservices. 10) Incident response training — incident command basics, blameless post-mortems framework, communication during incidents. Resources: "Incident Response & Computer Forensics" Luttgens / Pepe / Mandia, Google's incident management training. 11) Pet project: deploy a distributed app on K8s with full SLO setup + chaos experiments + on-call simulation. Document as a production-ready system. RU courses: Slurm SRE, Otus "SRE", Karpov.Courses SRE Track. International (EN): "Database Reliability Engineering" Campbell / Majors, USENIX SREcon talks (free YouTube), Google Cloud SRE Certification Path. DevOps Middle + interest → SRE Junior — 4-10 months (need to strengthen programming + distributed systems theory).

How many open jobs are in this sample?

The published sample contains 2012 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.

What skills does a Senior SRE need?

A Senior SRE owns the full reliability engineering cycle + technical leadership. Programming Backend Middle+ level: Go mastery (standard for SRE automation) or Python deep — at a level of "can write production-grade autoscaling logic / capacity planning algorithms / custom K8s operators". Kubernetes mastery deep: production-scale (nodes), Operators (Kubebuilder / Operator SDK), custom CRDs, multi-tenancy patterns. Distributed systems theory: deep CAP theorem understanding, consistency models (linearizability / sequential / causal / eventual), consensus algorithms (Paxos / Raft), failure mode taxonomy, network partition handling patterns. Observability mastery: Prometheus advanced (PromQL mastery + recording rules + federation + remote_write), Grafana advanced (templating + transformations + alerting), Loki + Tempo + OpenTelemetry integration mastery, distributed tracing across microservices. SLI / SLO architecture mastery: SLO-as-code (Pyrra / OpenSLO / Sloth), error budget policy design + enforcement automation, multi-window burn-rate alert tuning (avoid alert fatigue). Incident command mastery: lead incident response under stress, blameless post-mortem facilitation, contributing factors analysis (not root cause — modern thinking), action items prioritisation. Chaos engineering mastery: Chaos Mesh / Gremlin / LitmusChaos — design chaos experiments, GameDay facilitation. Capacity planning mastery: load testing methodology (k6 / Gatling / Locust), resource forecasting models, headroom analysis, peak-load handling. Performance engineering: profile-driven optimisation (perf / bpftrace / flamegraphs), memory leak diagnosis, GC tuning, network performance analysis. Service mesh deep: Istio / Linkerd / Cilium — traffic management, retry policies, circuit breakers, fault injection. System design for reliability: design multi-region multi-AZ HA on whiteboard, RPO / RTO planning, DR strategies, cell-based architecture for blast radius limitation. Soft: ADRs writing, incident communications (status page updates + stakeholder calls in crisis), on-call rotation discipline, cross-team collaboration (Backend / DevOps / Platform / Security teams), mentoring Middle SRE. English for Senior+ MUST — SRE is intensely cross-team + the community is English-speaking (USENIX SREcon, papers).

Leave a request

Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.

By submitting, you agree to the privacy policy.