Glassdoor users rated their interview experience at Kaggle as 100% positive with a difficulty rating score of 3.5 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Software Engineer and Data Scientist rated their interviews as the hardest, whereas interviews for Software Engineer and Data Scientist roles were rated as the easiest.
The hiring process at Kaggle takes an average of 14 days when considering 2 user submitted interviews across all job titles. Candidates applying for Software Engineer had the quickest hiring process (on average 14 days), whereas Software Engineer roles had the slowest hiring process (on average 14 days).
Easy going a good interviewer a with polite questions. And mostly a based on a technical a expertise of data science and a engineering. Three rounds with technical team and hr team.
I applied through other source. The process took 2 months. I interviewed at Kaggle in Jun 2020
Interview
Getting 10 notebooks with silver badge on Kaggle notebooks using python or r and making them public kernals. Kaggle is a domain where software developers can collaborate with each other........
I applied online. The process took 2 weeks. I interviewed at Kaggle in Sep 2016
Interview
They gave me a programming Task with 4 hours allotted. 2 weeks later, I got to meet with their CTO(?) about the Task on Google Hangouts with a silent third witness, and also got some ASP.NET MVC questions, some .net question code review questions and some really devil-in-the-details debugging questions related to 3 tier app.
Interview questions [1]
Question 1
I had other interviews and was not 100% prepared for reviewing my task, but pay attention to performance and encoding issues. I also got Async / await internals related question. Overall, I did ok. I know ASP.NET MVC to some degree. But it seemed like they were looking for someone who knew web-apps and .NET at expert level, not someone smart who can learn which may speak to the problems they need solving. Interesting experience, respectful, a bit long. The debugging questions were in the form: Foo is happening when run from this machine, but not locally or files can't be accessed on IIS server, what do you think is the problem and you can ask questions etc. They were real issues they encountered but weird edge cases, for which the answer is probably not so important as the steps you'd take (for MS-SQL issue for example)
In summary, looking for ASP.NET MVC / SQL / .NET expert.
They politely told me that they didn't want to move to next level. It was a fun, challenging experience but if they had stated they were looking for expert level, I'd probably told them I wasn't an expert and asked them if they want to proceed at the beginning.
Also, the gap between stages was kind of long (2 weeks)??