Taro Logo

Data Engineer Interview Experience - Italy

June 1, 2022
Negative ExperienceNo Offer

Process

A very messy process concerning communication, steps, and expectations, specifically:

  • Tech call with HR.
  • One hour: Code interview and basic CS questions.
  • Four one-hour sessions: Data concepts, system design, break, code interview, behavioral interview.

Questions

  • Inner vs. outer joins
  • Data formats (e.g., Avro, Parquet)
  • Counts of listeners/listened songs by country and similar metrics
  • Simple data interview questions on joins and windowing functions, such as ROW_COUNT
  • Common song listening sequences (e.g., triples)
  • Trivial system design questions, like "Where would you put your data?" without accurate context. This felt ambiguous, and I was unsure of the interviewer's true intent.
  • Smashed the coding interview, finishing early and leaving ample time for questions. The people seemed nice.
  • Vague behavioral interview questions of the "Tell me about a time when..." variety, such as when you disliked something or had to convince someone to do something.

Was this helpful?

Interview Statistics

The following metrics were computed from 3 interview experiences for the Spotify Data Engineer role in Italy.

Success Rate

0%
Pass Rate

Spotify's interview process for their Data Engineer roles in Italy is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral33%
Negative67%

Candidates reported having very negative feelings for Spotify's Data Engineer interview process in Italy.

Spotify Work Experiences