Which roles ask for Container Orchestration at tech companies · 193 roles · 90 days to Nov 21, 2026
Updated
193 roles counted that list Container Orchestration, one per company, title and level; 416 postings in the window.
In short
Container Orchestration: listed in 193 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 135 and preferred in 58. The largest group is software engineer roles: 69 of 193 (36%).
- Required
- 135 of 193 (70%)
- Of the roles that list Container Orchestration
- Preferred
- 58 of 193 (30%)
- Of the roles that list Container Orchestration
- Largest group
- 69 of 193 (36%)
- Software engineer
Roles that ask for Container Orchestration
Roles listing Container Orchestration, 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 | 69 | 69 of 4,983 (1%) |
| DevOps engineer | 32 | 32 of 478 (7%) |
| Site reliability engineer | 30 | 30 of 351 (9%) |
| Platform engineer | 29 | 29 of 454 (6%) |
| Machine learning engineer | 10 | 10 of 538 (2%) |
| AI engineer | 5 | 5 of 507 (1%) |
| Forward deployed engineer | 4 | 4 of 340 (1%) |
| Data engineer | 3 | 3 of 867 (0%) |
| Security engineer | 3 | 3 of 801 (0%) |
| Software architect | 3 | 3 of 207 (1%) |
Companies that ask for it most
- Logistics Management Institute3 roles
- Palantir3 roles
- Replit3 roles
- ClickHouse2 roles
- Crusoe2 roles
- Formlabs2 roles
- Pigment2 roles
- Render2 roles
- SentinelOne2 roles
- Terzo2 roles
Asked alongside
Out of the 193 Container Orchestration roles whose requirements we read: the other skills they ask for. At most 10 per list, those asked for most.
| Skill | Roles asking |
|---|---|
| Kubernetes | 120 of 193 (62%) |
| Python | 111 of 193 (58%) |
| AWS | 96 of 193 (50%) |
| CI/CD | 94 of 193 (49%) |
| Terraform | 88 of 193 (46%) |
| Infrastructure as Code | 85 of 193 (44%) |
| Docker | 80 of 193 (41%) |
| Go | 69 of 193 (36%) |
| Observability | 53 of 193 (27%) |
| Azure | 51 of 193 (26%) |
| Skill | Roles asking |
|---|---|
| Kubernetes | 42 of 193 (22%) |
| CI/CD | 28 of 193 (15%) |
| Observability | 26 of 193 (13%) |
| AWS | 22 of 193 (11%) |
| Infrastructure as Code | 22 of 193 (11%) |
| Grafana | 20 of 193 (10%) |
| Terraform | 20 of 193 (10%) |
| Docker | 19 of 193 (10%) |
| Prometheus | 18 of 193 (9%) |
| Cybersecurity | 17 of 193 (9%) |
Experience
Asked most often: 5–7 years, 79 of 146 (54%).
Of the 146 roles that state years
- Under 1 year
- 1 of 146 (1%)
- 1 year
- 0 of 146 (0%)
- 2 years
- 5 of 146 (3%)
- 3–4 years
- 25 of 146 (17%)
- 5–7 years
- 79 of 146 (54%)
- 8–9 years
- 22 of 146 (15%)
- 10+ years
- 14 of 146 (10%)
Degree
19 of 189 (10%) require a degree, and 50 more accept experience instead.
Of the 189 roles we could read for it
- Required
- 19 of 189 (10%)
- Required, or experience instead
- 50 of 189 (26%)
- Preferred
- 9 of 189 (5%)
- Not mentioned
- 111 of 189 (59%)
Pay and remote work
Of the 193 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $186.3k a year
- Roles stating pay
- 80 of 193 (41%)
- Remote roles
- 143 of 193 (74%)
How we count: 193 roles from 177 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?