5 ms·
So I've been interviewing for data analyst/science positions since leaving Apple in April. I may do a postmortem on my search later, but speaking from my exper
by minimaxir 9y ago
So I've been interviewing for data analyst/science positions since leaving Apple in April.
I may do a postmortem on my search later, but speaking from my experience with many, many interviews over the past couple months, the TL;DR is that the conventional interview wisdom on Hacker News/the cscareerquestions subreddit/this article is wrong and out of date. Interviews for such positions require a different set of skills than just reading Cracking the Code Interview (and ones that you can't get at a data bootcamp).
- cbcoutinho 9y agoIf you had to summarize into three points?
- minimaxir 9y agoI have one notable observation: On Hacker News, every time an interview thread pops up, there is a discussion decrying the use of technical screenings before an onsite, and often suggest practical work experience instead using a homework assignment (which this article does not discuss). Most of the companies I've talked with for data analyst/science roles have given me both a homework assignment and a technical screen before the onsite. And often a prescreen test before both of them. There have been a number of occasions where I easily passed the homework screen but failed the technical screen (without any feedback as to why). And it's beginning to get annoying.
- FlyingLawnmower 9y agoDid you find another job yet? If not, what type of opportunity are you looking for? Data science is also a wide, somewhat poorly defined domain.
- minimaxir 9y agoStill looking. Mostly for any role with a data analyst/data scientist title (i.e. I am not applying for the machine learning/NLP roles which require a PhD and the authorship of several papers since there is no point).
- alexchantavy 9y agoWhat kinds of technical questions do they ask in a data science interview?
- minimaxir 9y agoOn the stats side, often higher-level theory questions, such as "How does the k-means algorithm work?", "How do you select the best k for k-means?", "What is the curse of dimensionality?" which again would not be things covered at a data boot camp or data science thought pieces on Medium. On the technical side, there is often more-advanced SQL (nested JOINs + PostgreSQL window functions). On the big data side, there is often discussion of distributed systems (e.g. Spark clusters) and practical algorithmic complexity at scale (i.e. instant fail if you suggest anything loglinear or slower).
- moab 9y agoI overheard some colleagues talking about a recent interview where a candidate with "stellar industry experience", i.e. Kaggle wins and previous ML experience at a valley company, who couldn't explain Bayes rule to them, let alone rederive Naive Bayes. While books like the one below are extremely theoretical, anyone interviewing for these kind of roles should spend at least a week or two just looking through this to see what kind of algorithms and properties are studied in theory. Foundations of Data Science (Blum, Hopcroft, Kannan) https://www.cs.cornell.edu/jeh/book2016June9.pdf https://www.cs.cornell.edu/jeh/book2016June9.pdf
- reader5000 9y agoThis is like not hiring a [big name coding competition] winner because he didn't know radix sort.
- mmierz 9y agoI think it's more like not hiring a big name coding competition winner because they never bothered to learn how to use version control, or any coding best practice, or any language other than C. Trying to do data science with zero knowledge of the fundamentals of probability is dangerous. Bayes rule isn't some kind of deep magic, it's covered within the first few lectures of an undergraduate probability course and it's absolutely necessary to understand the output of any machine learning model.
- AlexCoventry 9y agoHi, minimaxir. If confidentiality doesn't prohibit it, I'd be curious to know what the most interesting roles you interviewed for were.