Which roles ask for FinOps at tech companies · 106 roles · 90 days to Nov 21, 2026
Updated
106 roles counted that list FinOps, one per company, title and level; 172 postings in the window.
In short
FinOps: listed in 106 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 37 and preferred in 69. The largest group is platform engineer roles: 29 of 106 (27%).
- Required
- 37 of 106 (35%)
- Of the roles that list FinOps
- Preferred
- 69 of 106 (65%)
- Of the roles that list FinOps
- Largest group
- 29 of 106 (27%)
- Platform engineer
Roles that ask for FinOps
Roles listing FinOps, 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%) |
| DevOps engineer | 17 | 17 of 478 (4%) |
| Site reliability engineer | 14 | 14 of 351 (4%) |
| Software architect | 10 | 10 of 207 (5%) |
| Software engineer | 10 | 10 of 4,983 (0%) |
| AI engineer | 5 | 5 of 507 (1%) |
| Data architect | 5 | 5 of 126 (4%) |
| Analytics engineer | 4 | 4 of 251 (2%) |
| Data engineer | 4 | 4 of 867 (0%) |
| Security engineer | 4 | 4 of 801 (0%) |
Companies that ask for it most
- Bright Vision Technologies3 roles
- Fortive2 roles
- Future Processing2 roles
- JumpCloud2 roles
- LUZA Group2 roles
- NASCO2 roles
- GoFasti1 role
- Moneycorp1 role
- Smartsheet1 role
- Tango1 role
Asked alongside
Out of the 106 FinOps roles whose requirements we read: the other skills they ask for. At most 10 per list, those asked for most.
| Skill | Roles asking |
|---|---|
| AWS | 71 of 106 (67%) |
| Infrastructure as Code | 71 of 106 (67%) |
| Terraform | 68 of 106 (64%) |
| Python | 63 of 106 (59%) |
| CI/CD | 58 of 106 (55%) |
| Identity and Access Management | 49 of 106 (46%) |
| Kubernetes | 48 of 106 (45%) |
| Observability | 48 of 106 (45%) |
| Azure | 37 of 106 (35%) |
| Networking | 36 of 106 (34%) |
| Skill | Roles asking |
|---|---|
| Cost Optimization | 25 of 106 (24%) |
| Kubernetes | 16 of 106 (15%) |
| AI | 15 of 106 (14%) |
| Observability | 14 of 106 (13%) |
| SOC 2 | 12 of 106 (11%) |
| CI/CD | 11 of 106 (10%) |
| Grafana | 11 of 106 (10%) |
| GCP | 10 of 106 (9%) |
| Prometheus | 10 of 106 (9%) |
| AWS | 9 of 106 (8%) |
Experience
Asked most often: 5–7 years, 38 of 83 (46%).
Of the 83 roles that state years
- Under 1 year
- 0 of 83 (0%)
- 1 year
- 3 of 83 (4%)
- 2 years
- 2 of 83 (2%)
- 3–4 years
- 11 of 83 (13%)
- 5–7 years
- 38 of 83 (46%)
- 8–9 years
- 12 of 83 (14%)
- 10+ years
- 17 of 83 (20%)
Degree
9 of 105 (9%) require a degree, and 26 more accept experience instead.
Of the 105 roles we could read for it
- Required
- 9 of 105 (9%)
- Required, or experience instead
- 26 of 105 (25%)
- Preferred
- 4 of 105 (4%)
- Not mentioned
- 66 of 105 (63%)
Pay and remote work
Of the 106 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $180k a year
- Roles stating pay
- 51 of 106 (48%)
- Remote roles
- 89 of 106 (84%)
How we count: 106 roles from 99 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?