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.
http://www.smithsonianmag.com/history/charles-proteus-steinm...
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.
Or be payed in "credits", that is the same thing.
