Which roles ask for Prometheus at tech companies · 544 roles · 90 days to Nov 21, 2026
Updated
544 roles counted that list Prometheus, one per company, title and level; 1,143 postings in the window.
In short
Prometheus: listed in 544 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 317 and preferred in 227. The largest group is software engineer roles: 144 of 544 (26%).
- Required
- 317 of 544 (58%)
- Of the roles that list Prometheus
- Preferred
- 227 of 544 (42%)
- Of the roles that list Prometheus
- Largest group
- 144 of 544 (26%)
- Software engineer
Roles that ask for Prometheus
Roles listing Prometheus, by title family. Where the role has a page, the count is also out of that role's roles whose requirements we read.
| Role | Roles | Of the role's roles we read |
|---|---|---|
| Software engineer | 144 | 144 of 4,983 (3%) |
| DevOps engineer | 128 | 128 of 478 (27%) |
| Site reliability engineer | 113 | 113 of 351 (32%) |
| Platform engineer | 96 | 96 of 454 (21%) |
| Machine learning engineer | 14 | 14 of 538 (3%) |
| Data engineer | 12 | 12 of 867 (1%) |
| QA engineer | 10 | 10 of 494 (2%) |
| Security engineer | 9 | 9 of 801 (1%) |
| Software architect | 8 | 8 of 207 (4%) |
| Forward deployed engineer | 6 | 6 of 340 (2%) |
Companies that ask for it most
- Zscaler5 roles
- Cerebras Systems4 roles
- CoreWeave4 roles
- Sezzle4 roles
- Wayve4 roles
- Bixal3 roles
- Planet3 roles
- SOFTSWISS3 roles
- Sporty Group3 roles
- Vultr3 roles
Asked alongside
Out of the 544 Prometheus roles whose requirements we read: the other skills they ask for. At most 10 per list, those asked for most.
| Skill | Roles asking |
|---|---|
| Kubernetes | 362 of 544 (67%) |
| Python | 329 of 544 (60%) |
| CI/CD | 303 of 544 (56%) |
| AWS | 289 of 544 (53%) |
| Terraform | 289 of 544 (53%) |
| Grafana | 278 of 544 (51%) |
| Infrastructure as Code | 245 of 544 (45%) |
| Docker | 244 of 544 (45%) |
| Observability | 222 of 544 (41%) |
| Go | 216 of 544 (40%) |
| Skill | Roles asking |
|---|---|
| Grafana | 190 of 544 (35%) |
| Observability | 120 of 544 (22%) |
| Kubernetes | 84 of 544 (15%) |
| Terraform | 79 of 544 (15%) |
| OpenTelemetry | 70 of 544 (13%) |
| AWS | 69 of 544 (13%) |
| GCP | 65 of 544 (12%) |
| Monitoring | 62 of 544 (11%) |
| Infrastructure as Code | 61 of 544 (11%) |
| Argo CD | 59 of 544 (11%) |
Experience
Asked most often: 5–7 years, 214 of 412 (52%).
Of the 412 roles that state years
- Under 1 year
- 2 of 412 (0%)
- 1 year
- 6 of 412 (1%)
- 2 years
- 27 of 412 (7%)
- 3–4 years
- 72 of 412 (17%)
- 5–7 years
- 214 of 412 (52%)
- 8–9 years
- 54 of 412 (13%)
- 10+ years
- 37 of 412 (9%)
Degree
64 of 535 (12%) require a degree, and 99 more accept experience instead.
Of the 535 roles we could read for it
- Required
- 64 of 535 (12%)
- Required, or experience instead
- 99 of 535 (19%)
- Preferred
- 24 of 535 (4%)
- Not mentioned
- 348 of 535 (65%)
Pay and remote work
Of the 544 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $165.5k a year
- Roles stating pay
- 220 of 544 (40%)
- Remote roles
- 418 of 544 (77%)
How we count: 544 roles from 428 employers in the 90 days to Nov 21, 2026, each role counted once however many boards post it. Skills are counted out of the roles whose requirements we read. Roles are not filtered by country. Methodology
Something wrong here?