As Jordan Tigani observes, there are not that many really big data situations[1].
Thus data science proficiency might be in support of business initiatives in a particular application domain and not a means to an end in itself.
It really doesn't.
1. data engineering - dealing with etl pipelines, data warehouses, data lakes, databases
2. data science - ai/ml, models etc
#1 preps things so #2 can do their jobs
And I'm not seeing anything getting automated.
IMO, the emergence of specializations is a good thing because a) it means the data field (and the tools it uses) are maturing and b) you can have a more focused career trajectory instead of feeling the pressure to learn EVERYTHING
- Some of the stuff becomes diffused and common. Anyone can do it.
- Some of the stuff becomes data engineering.
- Some of the stuff becomes fitting a model -- anyone can do it.
- Some of the stuff ends up subsumed in a cloud providers offering and mostly automated.
- Some of the stuff becomes a SaaS (e.g. A/B testing).
Death by factorisation.
Specialisation is another sort of death, where X doesn't need a "Data scientist" any more, they need a "X data scientist". A bit like how "scientific computing" is just programming, except you wouldn't hire "just" programmers to do it -- you hire programmers who specialise in scientific computing.