Live data from Hacker News

Some Reflections on Being Turned Down for a Lot of Data Science Jobs

tdhopper.com

31–40 of 175 posts

Re: Some Reflections on Being Turned Down for a Lot of Data Science Jobs

#31
post #29

At least you have been told the reasons, even if they are true or not. I recently had many tech/behavioral interview with team and passed, but after a review with VP of X, saying we decided not to move forward is way worse than this. I still keeep wondering 'What is wrong with me?' even after years of interviews. I have some suspicions, but never a promising answer. If I oneday found a company, first company policy w…

How about talking to a therapist / counsellor / coach that specialises in professionals?

Even one or two sessions can help you a lot - they are trained in pinpointing "soft" issues.

Re: Some Reflections on Being Turned Down for a Lot of Data Science Jobs

#32

Many recommend setting up an online portfolio for these types of positions. But I've applied to a number of Data Analyst/Scientist jobs recently and I am immediately rejected almost every time despite highlighting my blog/portfolio ( http://minimaxir.com ) and my GitHub with open-source code/Notebooks for each and every post ( https://github.com/minimaxir ), both of which have topped HN on occasion. Internal recruite…

The first job is the hardest to get. Keep trying, lower your expectations: Take anything you can and don't expect to be paid much.

Contrary to what the reddit folks would have you think. The ONLY thing that consistently get someone through the door is demonstrable real work experience, on real projects, in the industry (read: not academia). Side projects are not a substitute and the lack of degree is a barrier.

Re: Some Reflections on Being Turned Down for a Lot of Data Science Jobs

#33

Many recommend setting up an online portfolio for these types of positions. But I've applied to a number of Data Analyst/Scientist jobs recently and I am immediately rejected almost every time despite highlighting my blog/portfolio ( http://minimaxir.com ) and my GitHub with open-source code/Notebooks for each and every post ( https://github.com/minimaxir ), both of which have topped HN on occasion. Internal recruite…

I recruited for one data science job. The hiring manager was super focused on getting someone with a PhD. Is that the norm for a position like that?

Re: Some Reflections on Being Turned Down for a Lot of Data Science Jobs

#34

Earlier quoted context omitted.

I've probably interviewed about 70-100 such people in the past year and a half. Exactly 1 such person was qualified (I hired him). The issue in my view is the following: people who know both statistics and computer science are extremely rare. People who actually understand statistics are rare. I can probably weed out 1/3 to 1/2 of candidates simply by asking what a p-value is, or what precision/recall are (this inclu…

Ignoring what a p-value is does not mean that you don't know statistics. p-tests are not some inherent statistical property, they're just a useful model for significance. People coming from a CS background most likely didn't have to deal with p-values, but they can still be good at linear algebra or bayesian statistics. (not sure I can defend somebody that does not know what precision/recall are)

Regarding precision/recall, I've a background in financial econometrics and this is the first time I encounter the terms.

Re: Some Reflections on Being Turned Down for a Lot of Data Science Jobs

#35
I manage a data science team and revamped the hiring process pretty substantially about a year ago, to good results. Nothing in here is particularly original, but here's what we do:

1. Break down "data science" into several different roles–in our case, Analyst (business-oriented), Scientist (stats-heavy), Engineer (software-heavy). Turns out that what we mostly want are Engineers-Analysts, so our process screens heavily for those.

2. Figure out which types of people can be trained to be good at those roles, given the team's current skillset. I opted to look primarily for people with strong analysis skills and some engineering.

3. Design interview tasks/questions that screen for those abilities. In my case, the main thing I did was make sure that the interviews depended very little on pre-existing knowledge, and a lot on resourcefulness/creativity/etc. E.g. the (2-hour) takehome is explicitly designed to be heavily googleable.

4. Develop phone screens that are very good at filtering people quickly, so that we don't waste candidates' time. By the time someone gets to an onsite interview on our team there's something like a 50% chance they'll get an offer.

On the candidate side, when I'm applying I try to figure out first and foremost what a company means by "data scientist", usually by networking & talking to someone who already works there. This filters out maybe 90% of jobs with that title, and then I put more serious effort into the rest.

Re: Some Reflections on Being Turned Down for a Lot of Data Science Jobs

#37
> "Quite honestly given your questions [about vacation policy] and the fact that you are considering other options, [we] may not be the best choice for you."

I had a very similar experience. Job offer was basically on the table and then they balked because I mentioned that I had another offer (at a larger company, which they seemed shocked/annoyed with) and I had a question about parking at their new offices. The current offices had free parking, so I had simply asked if the new ones would too. The response was very cold (must have a been the source of internal strife, I guess?). An hour later I got a call saying they were no longer interested.

Re: Some Reflections on Being Turned Down for a Lot of Data Science Jobs

#39

Many recommend setting up an online portfolio for these types of positions. But I've applied to a number of Data Analyst/Scientist jobs recently and I am immediately rejected almost every time despite highlighting my blog/portfolio ( http://minimaxir.com ) and my GitHub with open-source code/Notebooks for each and every post ( https://github.com/minimaxir ), both of which have topped HN on occasion. Internal recruite…

I recruited for one data science job. The hiring manager was super focused on getting someone with a PhD. Is that the norm for a position like that?

Some companies know what skills they need, others don't. For those who don't know, but want a typical statistical modeler, a PhD in statistics is the safest choice, then a PhD in machine learning or MS in stats, after that, you need to look for the presence of specific skills... like deep learning for image recognition or the Hadoop stack.

Re: Some Reflections on Being Turned Down for a Lot of Data Science Jobs

#40

> "Quite honestly given your questions [about vacation policy] and the fact that you are considering other options, [we] may not be the best choice for you." I had a very similar experience. Job offer was basically on the table and then they balked because I mentioned that I had another offer (at a larger company, which they seemed shocked/annoyed with) and I had a question about parking at their new offices. The cur…

Wow!
Post reply on HN