Which roles ask for Batch Processing at tech companies · 136 roles · 90 days to Nov 21, 2026
Updated
136 roles counted that list Batch Processing, one per company, title and level; 420 postings in the window.
In short
Batch Processing: listed in 136 roles at tech companies whose requirements we read, in the 90 days to Nov 21, 2026. It was required in 98 and preferred in 38. The largest group is data engineer roles: 61 of 136 (45%).
- Required
- 98 of 136 (72%)
- Of the roles that list Batch Processing
- Preferred
- 38 of 136 (28%)
- Of the roles that list Batch Processing
- Largest group
- 61 of 136 (45%)
- Data engineer
Roles that ask for Batch Processing
Roles listing Batch Processing, 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 |
|---|---|---|
| Data engineer | 61 | 61 of 867 (7%) |
| Software engineer | 41 | 41 of 4,983 (1%) |
| Data architect | 10 | 10 of 126 (8%) |
| AI engineer | 4 | 4 of 507 (1%) |
| Machine learning engineer | 4 | 4 of 538 (1%) |
| Analytics engineer | 3 | 3 of 251 (1%) |
| Data scientist | 3 | 3 of 773 (0%) |
| Software architect | 3 | 3 of 207 (1%) |
| Platform engineer | 2 | 2 of 454 (0%) |
| Site reliability engineer | 2 | 2 of 351 (1%) |
Companies that ask for it most
- KIS Solutions3 roles
- Be | Shaping the Future2 roles
- CloudMasonry2 roles
- FanDuel2 roles
- Inizio Partners Corp2 roles
- NBCUniversal2 roles
- Roblox2 roles
- Wiley2 roles
- Zeta Global2 roles
- ZipRecruiter2 roles
Asked alongside
Out of the 136 Batch Processing 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 136 (68%) |
| SQL | 78 of 136 (57%) |
| Data Modeling | 59 of 136 (43%) |
| Spark | 53 of 136 (39%) |
| Stream Processing | 53 of 136 (39%) |
| CI/CD | 49 of 136 (36%) |
| AWS | 48 of 136 (35%) |
| Data Pipelines | 44 of 136 (32%) |
| Data Warehousing | 44 of 136 (32%) |
| Airflow | 41 of 136 (30%) |
| Skill | Roles asking |
|---|---|
| Docker | 18 of 136 (13%) |
| Kubernetes | 18 of 136 (13%) |
| AI | 17 of 136 (13%) |
| Machine Learning | 17 of 136 (13%) |
| Kafka | 16 of 136 (12%) |
| Infrastructure as Code | 15 of 136 (11%) |
| AWS | 14 of 136 (10%) |
| CI/CD | 14 of 136 (10%) |
| Terraform | 14 of 136 (10%) |
| Data Governance | 13 of 136 (10%) |
Experience
Asked most often: 5–7 years, 50 of 103 (49%).
Of the 103 roles that state years
- Under 1 year
- 1 of 103 (1%)
- 1 year
- 2 of 103 (2%)
- 2 years
- 3 of 103 (3%)
- 3–4 years
- 14 of 103 (14%)
- 5–7 years
- 50 of 103 (49%)
- 8–9 years
- 18 of 103 (17%)
- 10+ years
- 15 of 103 (15%)
Degree
23 of 135 (17%) require a degree, and 24 more accept experience instead.
Of the 135 roles we could read for it
- Required
- 23 of 135 (17%)
- Required, or experience instead
- 24 of 135 (18%)
- Preferred
- 4 of 135 (3%)
- Not mentioned
- 84 of 135 (62%)
Pay and remote work
Of the 136 roles we could read for it. Pay these roles state, not what the skill pays.
- Median stated pay
- $186k a year
- Roles stating pay
- 50 of 136 (37%)
- Remote roles
- 101 of 136 (74%)
How we count: 136 roles from 122 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?