Companies think they need a "data scientist" but they actually want a "software engineer with enough stats/data background to implement data science algorithms in production."
The result is that a lot of "data scientist" jobs are mostly data engineering or ML engineering and that is reflected in the list of requirements. It makes finding a good job extremely difficult, and it's for the better that the "data scientist" title is being eroded, because it makes it easier to tell when a "data scientist" job is actually data science as opposed to something else.
Not that "data science" is a good name anyway, but that's another story.
Missing is the Data Analyst component, and (as is normally typical in the discussion) the statistical experimenter (A/B, MAB, etc.)
Took me for a bit of a spin because when I was first interviewing this year, I'd apply for DS roles and only get interviews that were very stats heavy with a leetcode easy, but started getting further when I basically stopped applying for DS roles and went straight for MLE roles.
[1] https://medium.com/@rchang/my-two-year-journey-as-a-data-sci...
I'm already struggling to parse the first paragraph -- is this a typo? Or do they mean a role that is both ML Engineer and Data Scientist?