If you want to hire an experienced, production and value adding _______ be prepared to pay.
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)
Anytime you choose cost over experience you end up paying more than you would in the first place by the end.
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.
One of my go-to stories when telling freelancers not to charge hourly :)
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.
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.
But yeah, where I've worked that's generally what we look for in candidates.
What is astonishing to me is how there seems to be 1) a dearth of candidates, period, and 2) candidates we can dig up miss scheduled calls, show up late for interviews, interview very poorly, turn in poor quality take home exercises (an exercise which essentially just covers the basics), have really crappy resumes (typos, horrible layout, inconsistencies with LinkedIn profile, etc...)--and these are folks with experience as statisticians or data scientists. Amazing.
We don't ask anything deep or complex either, yet we've had a really hard time finding people.
I think there's also an intersection with devops skills, maybe less important, but your hardcore statisticians usually put zero thought into operational considerations. Really the last bastion of "works on my machine" thinkers in the computing world. I just finished the Coursera "Reproducible Research" course and I was really struck how many of those principles parallel good software engineering practices - use source control, document through code, separate your environment from your code, automate as much as you possibly can, etc. I've been a software engineer for 20+ years but I want to get into data science partly because I've always been a data head, just without the theoretical background to do really interesting work, but also because I think I can bring some of the software engineering skills to bear.
Also, with grading peer's work on Coursera, I really realize that a lot of these candidates need help with their English and presentation skills. Many of the students put no work at all into the presentation, I imagine that's going to serve them poorly in the working world.
It seems to me that's an awful lot to fit between one pair of ears.
I would be interested to find out if you are using the phrase, and what would happen to your search for candidates if you changed the title to something less "sexy", like "data analyst"?
Or be payed in "credits", that is the same thing.