The interview process consisted of 1 Phone Screen with the Recruiter, 1 Technical Screen with an Engineer (or two engineers), and 4 onsite interviews with two data engineers per round. I understand that Spotify usually moves slowly with their candidates due to the volume of applications and the company being on the smaller side. But still treating candidates that make it to the onsite interviews with extremely slow and unclear responses has to be another level of unprofessional. Phone Screen with Recruiter My recruiter joined my phone screen late by 20 minutes and the general feeling was that he was rushed and just wanting to get this over with - not even giving me time to ask questions about the process in the interview and how to best prepare. My recruiter was really slow in responses and not clear in his answers when he did respond, which I'll provide some more examples through this interview process. Technical Screen with an Engineer The actual interviews with the engineers was great, they were warm, responsive, and we had good conversations about the company. Questions related to general CS fundamentals and general Data Engineering questions related to tools like MapReduce. Ended with a simple easy leetcode question with a slightly harder follow up that we just talked through. Virtual Onsite My onsite was scheduled for 3 weeks after my technical screen. Which was not ideal at all for schedule - I was looking for hopefully wrapping this up in 2 weeks maximum. There were multiple miscommunications with my recruiter, from scheduling to just general questions. There was a scheduling error where he did not allocate enough interview spots so I had to re-provide my availability. He also mentioned a 30 minute call to best prep me for the interviews, which he never got around to scheduling. I had to ask a couple times for a study guide, and any questions I had followed up were met with non-answers and look at the study guide, and then ended with a passive-aggressive sounding "Please let me know if you have any questions". The recruiter experience was definitely abysmal since they are the first contact with a company and how their culture is reflected to external candidates. The job description even changed mid way from mid level to senior, which wasn't good. Other than this horrible experience, the engineers on the onsite were nice. It composed of a coding round, a system design round, a data round, and a behavioral round. Each round was about an hour long - there were a total of 4 rounds in the final onsite. Coding Round: A string parsing question that required counting the length of the shortest substring in a paragraph formatted string input. It was a bit tricky, but should be solvable in the time given. Systems Design Round: They ask you to design a system around a problem that the engineers likely had to solve themselves. This is done in Miro whiteboarding software, so I would familiarize yourself with it if you get a design round. Data Round: They ask about your experience in Data engineering and some SQL/Pandas questions. Other reviews mentioned windowing functions and they were right, you will have to utilize this for this round. Behavioral Round: A standard behavioral round where they ask about your experience and how you dealt with specific situations. This is done with a manager of one of the teams that are hiring. Note: Spotify (at least for my recruiter) does NOT fast track you at all if you have a competing offer. In fact they are not cognizant or transparent about their decision making within a time frame you give. I heard back about a week and a half after my onsite to a rejection. I was transparent with my recruiter the whole time, and met with underwhelming responses. It felt like they were dragging their feet on getting the process done, which is not great. It could be just my experience, but if you do decide to interview with this company. I wish you good luck on getting a favorable recruiter that does their job and has empathy for candidates.