This topic is in my wheelhouse I recall a conversation i had last year with a CEO of one of the larger companies in auto. They tell me how committed they are to machine learning in their products because they just hired a data scientist. Oh boy... I see these roles in a lot of companies now. Most of these companies flat out aren't ready, and these people will leave as soon as they find out the truth. What is missed by these companies is that 95% of the work in machine learning is in how the data is architected. The value is extracted and compounded after this prerequisite. Database architecture and the development efforts behind it are literally the most valuable part of the infrastructure required to even start considering deploying machine learning. We are talking 1000s of hours here, not a couple months. The machine learning part actually takes a very small amount of time. Data flow and design is also not sexy, requires insane discipline and gets pushed to the wayside by product teams trying to hit marketing ready user stories. To 99.9% of humans it is boring and impossible to understand. Full disclosure I love database design, it is truly art, I think it is amazing what can be done to refine raw material into a polished gem. However, I venture to guess most people in senior leadership out there don't and have no desire to learn it. Which is fine, except they dont listen to the engineers that know how to do it right. Product teams (no offense) are just fancy sales people, they have no business jamming machine learning into a product deliverable. So to that CEO, instead hire a software architect and a database architect. Support them, give them time, learn from them.