I feel like this could be universal.<p>If you want to hire an experienced, production and value adding _______ be prepared to pay.<p>It's like the phrase "You don't pay a plumber to bang on your pipes, you pay them to know where to bang." (yes, that's from Suits)<p>Anytime you choose cost over experience you end up paying more than you would in the first place by the end.<p>Obviously there's exceptions to that, but if you're going to be cheap on a component or person that you need you will definitely regret it later.
I have met many people who call themselves a data scientists. it is very easy to call yourself a data scientist, and justify the label.<p>if the vocabulary of your community doesn't support your needs, then you need to modify your vocabulary. Swear words like 'data scientist', invite the idea of casting a wide net with a large set of poorly defined skills to arbitrarily select from.<p>I appreciate the communities' use of the term 'data engineer' to quarantine out some of these skills. For those writing a job description, or vetting candidates, these words really matter. when you muddy the soup, by expanding definitions, time gets wasted.
If you want to be tagged as an experienced data scientist be prepared to work for free for several years.<p>Or be payed in "credits", that is the same thing.