djleroy
Re:Ask HN: What are your personal red flags when you're interviewing a...
on Thursday June 13, 2024 @02:58PM (#40673256)
Hear hear!
Re:Ask HN: What are your personal red flags when you're interviewing a...
on Thursday June 13, 2024 @02:55PM (#40673224)
I hear that. But I’ve been burnt by people who “coded live” real well and then couldn’t or wouldn’t do anything for months at work. IMO - any one who is going to be good will be good at coding. It’s not rocket science. Haha. Been around long enough to see language du jour change too. Python also isn’t the end all of languages (we’ve moved on to Julia where I work).
Can you think? Are you curious? Those are hard to distill in an interview and harder still in formulaic interviews.
Re:Ask HN: What are your personal red flags when you're interviewing a...
on Thursday June 13, 2024 @02:50PM (#40673151)
I’ve found standardized questions to be useless. I’ve found the best people by reading their cvs carefully. Then reading whatever published work they have. Then asking them to talk about that. If that goes well then I describe the work the team is doing and ask them their thoughts. If I really need validation I have a data problem I send them and ask them to send it back. (I don’t ask people to code in front of me - that’s ridiculous and tells me nothing) The standard problem Id ask was to figure out how to calculate something I describe only conceptually, and then give them a data set to do it on. Most mediocre so called data scientists will throw a bunch of Python libraries at the data and not even think about what was asked. This, sadly, is the state of my profession after 10 years of “boot camps “ and incursions from other disciplines.
Re:Ask HN: What are your personal red flags when you're interviewing a...
on Thursday June 13, 2024 @02:43PM (#40673093)
Lots of people without degrees in data science (or statistics, or even computer science) in supervisory positions. Silly interview questions like “define multivariate” or “write python code to find factors” or “write SQL code to join tables”
These are all signs of an immature data science function- which predicts working on ill posed problems and a problematic business justification. If the people already there are mediocre it’s not a great place to join. A strong sign of that is if the interviewers don’t know enough to construct thoughtful questions about real, non trivial, issues from their work. There are too many people in data science who, sadly, are at this level.