I don’t hire Junior data-scientists
medium.com
I don’t hire Junior data-scientists
1–10 of 29 posts
Re: I don’t hire Junior data-scientists
#2These all seem like things you can figure out during the hiring stage. You could be losing out on some really talented employees by simply distrusting all junior candidates due to some prior incidents.
I've worked with some absolutely top-notch candidates straight out of college, and some mediocre ones which plenty of experience.
Re: I don’t hire Junior data-scientists
#3What's wrong with chaining try/except?
Re: I don’t hire Junior data-scientists
#4If Julien Kervizic offers you a job, don't take it.
Noted.
Re: I don’t hire Junior data-scientists
#5These all seem like things you can figure out during the hiring stage. You could be losing out on some really talented employees by simply distrusting all junior candidates due to some prior incidents. I've worked with some absolutely top-notch candidates straight out of college, and some mediocre ones which plenty of experience.
There is always some exception to the rule. Frankly the issue is more the number of topics one needs to learn to actually add value as a data-scientist. Junior data scientists need a hell lot of supervision compared to analysts or data-engineers. Most of what it takes to be a data-scientist is acquired on the job rather than something learned in class. And yes some of that could be checked during the interview, but that would also mean a very low pass rate and a lot of time spent hiring on these roles. I would rather hire these people straight out of college in role where they would have much more chance to excel, and would need less supervision. If they are good enough then give them more modeling tasks.
Re: I don’t hire Junior data-scientists
#6If Julien Kervizic offers you a job, don't take it. Noted.
That's essentially the tone I for from the article. I'm not sure where he thinks his "seasoned" data scientists come from but you can either:
- Train them yourself and then pay them a fair market value (that means actually giving them a raise!), or - you hire them from elsewhere.
Saying that you don't put effort into training tells me there are worse underlying issues, and I certainly don't want to work for you.
I work for a company that puts a lot of effort in training and education into their workforce (they paid for my BS and paid my salary while I got my MS). For gripes that I have about working for them, they take care of their own, mentor their, and make sure they are fairly compensated (to include raises). I have been working for them for the past 8 years, and I intend on working for them for the foreseeable future. That doesn't even mention that they also give me a great work life balance, and want to see me work up the ranks internally.
Seeing articles that only reenforce that I have it pretty good where I work.
Re: I don’t hire Junior data-scientists
#7If Julien Kervizic offers you a job, don't take it. Noted.
That's essentially the tone I for from the article. I'm not sure where he thinks his "seasoned" data scientists come from but you can either: - Train them yourself and then pay them a fair market value (that means actually giving them a raise!), or - you hire them from elsewhere. Saying that you don't put effort into training tells me there are worse underlying issues, and I certainly don't want to work for you. I wo…
Hey - I am not saying not to hire or train junior people, rather hire them as analyst or data-engineer. There is much less of learning gap in these positions, and from there they should have a path forward to a data-scientist position. This rather than hiring them as junior data-scientist and essentially just paying for their education.
Re: I don’t hire Junior data-scientists
#8What's wrong with chaining try/except?
One or two try/except is usually fine, but when you are nesting 3+ more try/except with the same error, the code becomes quickly unreadable.
Often you would be better off having a first look at the input to figure out which case you should tackle, decompose the nested try/excepts into separate function or at the very least keep it to two nested levels.
Re: I don’t hire Junior data-scientists
#9Is this targeted at junior data scientists? Is the intent for them to know that their code is inefficient, unformatted, overly specific, weird ass, and wrong?
I don't disagree that large amounts of people graduating from computer science programs are under-equipped to enter the workforce, but maybe focus on the shortcomings of the educational system than the people coming out of it.
Re: I don’t hire Junior data-scientists
#10And I don't hire data scientists who can't be bothered to proofread a blog post.