Data Science Engineer Interview Experience - Seattle, Washington
Process
My interview experience was extremely negative, involving both HR and the interviewers.
Let's start with the HR representative. After I provided my availability, I received no confirmation for nearly a week. When I followed up, HR cited issues with the recruiting coordinator and asked me to resubmit my availability. Following the onsite interview, there was no communication regarding the results until I initiated contact via email. It was surprising to experience this with a company like LinkedIn.
Secondly, I question why a mid-level role required an interview by a staff-level person, with no senior-level interviewers present.
Thirdly, after I quickly solved the first coding question and spent more time than expected on the second, the interviewer concluded, "You may have encountered the first question before." This statement was infuriating.
Overall, the entire interview process was disappointing and unprofessional.
Questions
LeetCode Array/String/Sliding Window Questions
Statistic: Rolling the dice, get probability.
Behavior Questions:
The most challenging project. How do you work with a difficult person?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the LinkedIn Data Science Engineer role in Seattle, Washington.
Success Rate
LinkedIn's interview process for their Data Science Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for LinkedIn's Data Science Engineer interview process in Seattle, Washington.
LinkedIn Work Experiences
- 4.0Good Culture, Bad LeadershipSoftware Engineer • Current EmployeeSeattle, Washington, United StatesJuly 26, 2025Pros: Good culture, engineering, and talent.Cons: Quite a bit of tech debt, bad leadership.
- 1.0Low Effort, Bad ColleaguesStaff Software Engineer • Current EmployeeSeattle, Washington, United StatesJuly 10, 2024Pros: You don't need to be good at your job, or put in a lot of hours.Cons: You work with people who are bad at their job, under poor leadership, and with constant reorgs.
- 4.0Good Food, Long HoursSenoir Software Engineer • Current EmployeeSeattle, Washington, United StatesJuly 5, 2024Pros: Food is really good in the Bay Area. Two weeks company-wide shutdown.Cons: Working hours: Over 40 hours seem to be common in my team.
LinkedIn Interview Questions
