Which roles ask for Capacity Planning at tech companies · 169 roles · 90 days to Nov 21, 2026
Updated
169 roles counted that list Capacity Planning, one per company, title and level; 426 postings in the window.
In short
Capacity Planning: listed in 169 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 108 and preferred in 61. The largest group is site reliability engineer roles: 46 of 169 (27%).
- Required
- 108 of 169 (64%)
- Of the roles that list Capacity Planning
- Preferred
- 61 of 169 (36%)
- Of the roles that list Capacity Planning
- Largest group
- 46 of 169 (27%)
- Site reliability engineer
Roles that ask for Capacity Planning
Roles listing Capacity Planning, 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 |
|---|---|---|
| Site reliability engineer | 46 | 46 of 351 (13%) |
| Platform engineer | 38 | 38 of 454 (8%) |
| Software engineer | 35 | 35 of 4,983 (1%) |
| DevOps engineer | 14 | 14 of 478 (3%) |
| Data engineer | 8 | 8 of 867 (1%) |
| Data analyst | 7 | 7 of 552 (1%) |
| Software architect | 6 | 6 of 207 (3%) |
| AI engineer | 5 | 5 of 507 (1%) |
| Data scientist | 4 | 4 of 773 (1%) |
| Machine learning engineer | 4 | 4 of 538 (1%) |
Companies that ask for it most
- Cerebras Systems4 roles
- Okta3 roles
- uvation3 roles
- Extreme Networks2 roles
- Filevine2 roles
- GitLab2 roles
- Similarweb2 roles
- SpaceX2 roles
- Terzo2 roles
- Zscaler2 roles
Asked alongside
Out of the 169 Capacity Planning roles whose requirements we read: the other skills they ask for. At most 10 per list, those asked for most.
| Skill | Roles asking |
|---|---|
| Python | 92 of 169 (54%) |
| CI/CD | 81 of 169 (48%) |
| Kubernetes | 78 of 169 (46%) |
| Observability | 77 of 169 (46%) |
| Infrastructure as Code | 73 of 169 (43%) |
| Terraform | 70 of 169 (41%) |
| Incident Response | 69 of 169 (41%) |
| Go | 66 of 169 (39%) |
| AWS | 64 of 169 (38%) |
| Networking | 61 of 169 (36%) |
| Skill | Roles asking |
|---|---|
| Observability | 30 of 169 (18%) |
| Kubernetes | 24 of 169 (14%) |
| Prometheus | 22 of 169 (13%) |
| Terraform | 19 of 169 (11%) |
| Grafana | 18 of 169 (11%) |
| AWS | 17 of 169 (10%) |
| Incident Response | 15 of 169 (9%) |
| Ansible | 14 of 169 (8%) |
| Alerting | 13 of 169 (8%) |
| CI/CD | 13 of 169 (8%) |
Experience
Asked most often: 5–7 years, 55 of 122 (45%).
Of the 122 roles that state years
- Under 1 year
- 0 of 122 (0%)
- 1 year
- 1 of 122 (1%)
- 2 years
- 7 of 122 (6%)
- 3–4 years
- 16 of 122 (13%)
- 5–7 years
- 55 of 122 (45%)
- 8–9 years
- 26 of 122 (21%)
- 10+ years
- 17 of 122 (14%)
Degree
19 of 167 (11%) require a degree, and 36 more accept experience instead.
Of the 167 roles we could read for it
- Required
- 19 of 167 (11%)
- Required, or experience instead
- 36 of 167 (22%)
- Preferred
- 5 of 167 (3%)
- Not mentioned
- 107 of 167 (64%)
Pay and remote work
Of the 169 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $183.4k a year
- Roles stating pay
- 82 of 169 (49%)
- Remote roles
- 110 of 169 (65%)
How we count: 169 roles from 147 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?