Which roles ask for Service Mesh at tech companies · 113 roles · 90 days to Nov 21, 2026
Updated
113 roles counted that list Service Mesh, one per company, title and level; 208 postings in the window.
In short
Service Mesh: listed in 113 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 48 and preferred in 65. The largest group is platform engineer roles: 29 of 113 (26%).
- Required
- 48 of 113 (42%)
- Of the roles that list Service Mesh
- Preferred
- 65 of 113 (58%)
- Of the roles that list Service Mesh
- Largest group
- 29 of 113 (26%)
- Platform engineer
Roles that ask for Service Mesh
Roles listing Service Mesh, 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 |
|---|---|---|
| Platform engineer | 29 | 29 of 454 (6%) |
| Software engineer | 25 | 25 of 4,983 (1%) |
| Site reliability engineer | 22 | 22 of 351 (6%) |
| DevOps engineer | 19 | 19 of 478 (4%) |
| Software architect | 9 | 9 of 207 (4%) |
| Security engineer | 5 | 5 of 801 (1%) |
| Forward deployed engineer | 2 | 2 of 340 (1%) |
| Machine learning engineer | 1 | 1 of 538 (0%) |
| QA engineer | 1 | 1 of 494 (0%) |
Companies that ask for it most
- Kong5 roles
- Veeam Software3 roles
- BeyondTrust2 roles
- Hims & Hers2 roles
- JumpCloud2 roles
- Persona2 roles
- SAMC SitusAMC Holdings Corp2 roles
- Saviynt2 roles
- Tango2 roles
- wex2 roles
Asked alongside
Out of the 113 Service Mesh roles whose requirements we read: the other skills they ask for. At most 10 per list, those asked for most.
| Skill | Roles asking |
|---|---|
| Kubernetes | 80 of 113 (71%) |
| Terraform | 71 of 113 (63%) |
| AWS | 70 of 113 (62%) |
| Infrastructure as Code | 67 of 113 (59%) |
| CI/CD | 62 of 113 (55%) |
| Python | 61 of 113 (54%) |
| Go | 51 of 113 (45%) |
| Observability | 45 of 113 (40%) |
| Distributed Systems | 41 of 113 (36%) |
| GCP | 39 of 113 (35%) |
| Skill | Roles asking |
|---|---|
| GitOps | 18 of 113 (16%) |
| Observability | 18 of 113 (16%) |
| Prometheus | 16 of 113 (14%) |
| AWS | 15 of 113 (13%) |
| Datadog | 15 of 113 (13%) |
| GCP | 15 of 113 (13%) |
| Grafana | 15 of 113 (13%) |
| Kubernetes | 15 of 113 (13%) |
| Argo CD | 14 of 113 (12%) |
| Azure | 12 of 113 (11%) |
Experience
Asked most often: 5–7 years, 46 of 92 (50%).
Of the 92 roles that state years
- Under 1 year
- 0 of 92 (0%)
- 1 year
- 2 of 92 (2%)
- 2 years
- 1 of 92 (1%)
- 3–4 years
- 13 of 92 (14%)
- 5–7 years
- 46 of 92 (50%)
- 8–9 years
- 19 of 92 (21%)
- 10+ years
- 11 of 92 (12%)
Degree
11 of 111 (10%) require a degree, and 30 more accept experience instead.
Of the 111 roles we could read for it
- Required
- 11 of 111 (10%)
- Required, or experience instead
- 30 of 111 (27%)
- Preferred
- 5 of 111 (5%)
- Not mentioned
- 65 of 111 (59%)
Pay and remote work
Of the 113 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $176.5k a year
- Roles stating pay
- 58 of 113 (51%)
- Remote roles
- 84 of 113 (74%)
How we count: 113 roles from 98 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?