Data & notes
| Company | Employed | Open | Employed per open role |
|---|---|---|---|
| Amazon | 62 | 2 | 31.0× |
| 1,748 | 0 | not captured | |
| Netflix | 55 | 0 | not captured |
| Meta | 36 | 0 | not captured |
| Datadog | 18 | 0 | not captured |
Read the multiple first
Name the destination wire you want covered when you ask for the list. The scope line is the whole request.
Key takeaway · How to cite
Is the deepest bench still Google at 1,748?
Start with who already employs the most, as of 2026-09-28 PT.
Data & notes
| Name | Value |
|---|---|
| 1,748 | |
| Amazon | 62 |
| Netflix | 55 |
| Meta | 36 |
| Datadog | 18 |
| Host | Employed | Open |
|---|---|---|
| Amazon | 62 | 2 (low open-role count — ratio is volatile) |
| 1,748 | not captured | |
| Netflix | 55 | not captured |
| Meta | 36 | not captured |
| Datadog | 18 | not captured |
Get the named Site Reliability Engineer list behind this table
A named list can follow this page once the scope is right. Keep the title family this page counted.
Does Amazon still lead employed-per-open at 31.0× (62/2)?
Multiple = employed ÷ captured open. Amazon 31.0× (62 employed / 2 open); Google 1,748 employed, open roles not captured; Netflix 55 employed, open roles not captured; Meta 36 employed, open roles not captured; Datadog 18 employed, open roles not captured. The ratio chart above ranks every host.
Does Amazon still post the most open SRE roles at 2?
Start with where demand sits, as of 2026-09-28 PT.
Data & notes
| Name | Value | Share |
|---|---|---|
| Amazon | 2 | 100.0% |
Does Amazon still lead the multiple while Google leads the bench?
The two rankings can diverge: bench volume and door density are different decisions.
Data & notes
| Category | Employed | Open roles |
|---|---|---|
| Amazon | 62 | 2 |
| 1,748 | 0 | |
| Netflix | 55 | 0 |
| Meta | 36 | 0 |
| Datadog | 18 | 0 |
What it means for Site Reliability Engineer employed vs open: what to do this week / how to use it
For door density this week: prefer the Amazon multiple at 31.0× (62 employed / 2 open).
- For bench volume: prefer the Google pool of 1,748 employed.
- For live reqs: prefer Amazon's 2 captured open roles.
- Amazon: low open-role count — ratio is volatile; do not brief off the multiple alone.
How to read hosts without captured open roles on the ratio?
Open roles were not captured at Google, Netflix, Meta, Datadog. Those hosts are listed in grey, with the employed count and no bar, and they are excluded from employed per open role. There is no five-host peer-pack ladder here: the comparison is employed per open role on one seat.
Data & notes
| Category | KEEP Site Reliability Engineer | KEEP Senior Site Reliability Engineer | OUT DevOps Engineer | OUT Platform Engineer | OUT Production Engineer |
|---|---|---|---|---|---|
| Amazon | 62 | 0 | 0 | 0 | 0 |
Data & notes
| Category | Freeze hook | Wave58 lock |
|---|---|---|
| Amazon Site Reliability Engineer | 62 | 62 |
Which LinkedIn titles collide into Site Reliability Engineer?
This ratio cut only keeps spelled-out Site Reliability Engineer. Wave58 freeze-locks adjacent titles.
- As of 2026-09-28 PT, anchor Amazon current SRE is 62/2 employed/open (31.0×) — page hook; same day Google is 1,748/0 (opens not captured).
- DevOps Engineer, Platform Engineer, and Production Engineer do not rewrite this page's 31.0× hook.
- Lists order against freeze Amazon 62/2 · 31.0×; OUT titles are not an SRE stand-in.
Where do SRE seats sit across the five hosts?
This page's primary hook is five-host employed/open multiples, not an address.country re-cut. Wave58 keeps a host ledger as the sourcing map.
- As of 2026-09-28 PT: Amazon 62/2 (31.0×), Google 1,748/0, Netflix 55/0, Meta 36/0, Datadog 18/0.
- Ratio lead Amazon 62/2; bench lead Google 1,748 — volume and door density are different decisions.
- Deepest bench vs busiest open board: Google 1,748 / Amazon 2 (1,748/2); lists order against the freeze ratio cut.
Is the anchor still stable? Wave58 lock on Amazon
Freeze anchor Amazon 62/2 · 31.0× (2026-09-28 PT). Wave58 same-cut lock is 62 — direction unchanged; page hook stays locked to freeze.
- Wave58 lock Amazon Site Reliability Engineer employed = 62 (freeze as-of 2026-09-28 PT).
- List buyers still order against freeze 62/2 · 31.0×; the lock is stability evidence only.
- If you need a today snapshot list, note the Wave58 as-of in the list ask.
As of 2026-09-28 PT · Source: Metix AI
Notes & method
Methodology
Employed counts Site Reliability Engineer on the company homepage record at 2026-09-28 PT. Open roles are active postings in the same title family. A 0 in the open cell means the open roles were not captured. It is not a demand of zero. Source: Metix AI.
FAQ
- Does an uncaptured Site Reliability Engineer host get a bar?
- Uncaptured open roles stay off the Site Reliability Engineer ratio and are listed without a bar. A 0 in the open cell means the postings were not captured.
- Is the Site Reliability Engineer page a peer-pack ladder?
- This Site Reliability Engineer page is employed divided by open roles, not a peer-pack rank. Hosts whose open roles were not captured stay off the ratio.
- Who leads the Site Reliability Engineer multiple?
- The top of the ratio list is Amazon 31.0× (62 employed / 2 open). The measurement date is 2026-09-28 PT.
- Where do the Site Reliability Engineer figures come from?
- 2026-09-28 PT dates both the employed cell and the open cell. Metix AI is the publisher.
Request the Site Reliability Engineer open-req list
Use this page's scope if you want the named list. The request should name the same employers.
Optional: try Mira