J'ai postulé en ligne. J'ai passé un entretien chez LinkedIn
Entretien
I applied online, got contacted for a 30-min HR screen call, then proceeded to a 1-hour Technical screen round. All the interviewers are very nice and professional. I did not pass the Technical round, because the role has much higher technical requirements than my skillsets. Technical screen includes 50% Python coding a Leetcode medium problem, 25% stats/experiment questions, 25% general ML questions. HR followed up with results in a personalized email and encouraged to reapply in the future.
Questions d'entretien [1]
Question 1
Experiment design question related to Simpson paradox
What are some ways to deal with class imbalance? pros and cons for each
J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez LinkedIn
Entretien
Applied through a referral. Shortly after, a recruiter responded to set up the first round of the interview process, which was a technical screen.
This was done in SQL and Python through a shared text editor (that is, both the interviewer and interviewee can see what each person is typing). The questions were quite easy and very straight forward. Made a few minor slip ups here and there (something that can easily be caught in a real-life situation when you'd be able to see outputs or error messages). Here's where I believe the assessment was unfair. There was no specification on which variant of SQL this interview would be conducted in. I coded up my SQL commands in PostgreSQL, but there are slight variations in some of the functions/syntax across different SQL languages. Despite that what I coded was 100% correct in PostgreSQL, because it didn't work with Presto, the interviewer deemed it incorrect.
The interviewer was also clearly copying the query I wrote into the editor to verify, so that's why she must have thought I was wrong. So despite writing a completely working query for each of the questions, because it did not conform with one specific variant of SQL, I did not make it to the next round. The number of changes needed to even get it to a working state were so minor too. At least 95% of the query was exactly as she expected it to be.
Honestly I was very surprised I didn't move forward... It seems she expected everything to run 100% correctly with no typos or errors despite me not being able to run the code to see the output. Absolutely unfair interview process.
Questions d'entretien [1]
Question 1
Basic SQL manipulation with joins and group bys.
Python pandas manipulation
J'ai passé un entretien chez LinkedIn (San Jose, CA)
Entretien
Very clear and straight forward, but maybe a bit too broad. Would be better to be more focused on the area of expertise. Coding questions don't really make much sense for data scientists anymore, basic level yes but not hard coding questions.
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez LinkedIn en mars 2022
Entretien
Phone screen + Onsite
Onsite has 5 rounds
HM
SQL + PYTHON
Data storytelling
Math
Case (Problem Solving + A/B testing)
The interview process going fluently and all interviewers show their professional. They are giving you positive feedbacks while your interviewing and encourage you to think more broadly. I feel they even want me to be in the company more than myself.
Didn't pass data storytelling round, all other rounds has a strong yes.
Questions d'entretien [1]
Question 1
Stats/Prob+Linear regression+data story telling+A/B Testing+SQL/Python+Problem Solving case