There's plenty of non ML software engineering to be done. Anecdotally a large proportion of interns want an "ML project", but only a small percentage of teams looking for interns are offering one.
Too many people going into ML could skew the supply/demand into making it a worse job option (more work, less pay), like game programming or academia.
There aren’t that many engineers with 10+ years of ML experience ATM, but there will be tons in 5 or so years. Chasing tomorrow’s trend is always more productive than chasing today’s, but of course the former requires predicting the future.
Comments
There's plenty of non ML software engineering to be done. Anecdotally a large proportion of interns want an "ML project", but only a small percentage of teams looking for interns are offering one.
Too many people going into ML could skew the supply/demand into making it a worse job option (more work, less pay), like game programming or academia.
There aren’t that many engineers with 10+ years of ML experience ATM, but there will be tons in 5 or so years. Chasing tomorrow’s trend is always more productive than chasing today’s, but of course the former requires predicting the future.
The question is this: 10 years from now when the top job requirements list ML - are you going to be ready or out of the game?
Alternatively the market is flooded with ML people and the value of ML on your CV is 0.