Looks very interesting. But when would I want to use OmniSciDB and OmniSci charts? I am not a working data scientist so my understanding here is limited.
How does FollowUp decide which question is important to me? (if at all)
I'm concerned about the level of access required for this app before I try it out (I am a Product Manager). Sounds like you'd be reading through all my emails and PMs. Is that correct?
Thank you ska. This is pretty insightful, and actually makes sense. We will try to incorporate your suggestions as we create more challenges. We are also looking for more data scientists and developers in general to help us built these solutions, review them and share honest feedback. Would you like to work us on the same? I would love to hear your thoughts on the new features we are building for more Data Science roles. If yes, let me know how to reach out to you.
We had to reduce the time limit on the test to handle the traffic. The intended test duration is 90-120mins. I have updated the test duration to 90mins now.
There is indeed some feature engineering involved. The challenge in the test can indeed be solved in the most obvious way possible, as well as in the most creative fashion. We believe how a Data Scientist goes about solving the problem was more important than a fixed outcome.
If you are interested, we are looking for data scientists and developers in general from the community to help us built these solutions and provide us with honest feedback. We are also looking at building support for other Data Science roles like a Data Engineer. I would be more than happy to show you what we have and hear your thoughts on the same. Let me know if you'd like to be a part of it and how can I reach out.
Do you think candidates looking for Data Science jobs would be open to performing a half a day exercise?
We optimized these challenges to allow candidates to show as much of their skills they can show in a timed window, without killing their creativity. I'd be curious to know what do think is a good way to interview data scientists.
- We are not automatically grading it. We have learned that in the past that trying to automatically grade candidates on such challenges biases their approach, which breaks the point of a good data science challenge.
- that's good to know. we are not really focusing on the final outcome but how creatively a candidate can go about the problem. the dataset allows for some good amount of creativity.
- Ah. can you elaborate what you mean by overly limited? We do support R.
Agreed. Data Science is a very broad term. The challenge is designed for Data Scientists. We are trying to target all experience levels as of now through a screening/take-home test that should take about 60-90mins at a stretch. Do you think the timed challenge should be different for senior vs junior data scientists?
What skills would you consider important for senior vs junior Data Scientist?
ska, our aim with the challenge was to allow candidates to not be biased by a fixed outcome and try to solve the problem as they would solve any real data science problem.
This meant we couldn't automatically score/rank a candidate's solution. We do provide them with an evaluation metric in the problem description (Mean Absolute Error).
Here is scoring rubric we provide to the interviewers when they review the submission - https://d.pr/i/hNYY0u
Would love to hear more opinions on our scoring rubric
That is correct. We had to reduce the time duration to be able to handle the traffic. We recommend 90mins for this challenge. What do you think would the right amount of time for this problem?
@soVeryTired, the challenge showcased in the test does involve a lot of wrangling, handling missing data points, spotting bias and identifying the right features for the regression model. The challenge is designed to allow for a candidate's creativity.
Do you think the data set we have used doesn't do it to the extent you'd expect from a data scientists?