Firstly, I had a phone interview with a recruiter and was told that there was a lead position in the company and they would like to have a technical interview with me. After a week, I had the interview via Skype with two people from Spotify.

However, based on the questions they asked, I believe the interview was intended for a junior developer who had just graduated from university with fresh knowledge of all Unix commands and technical terms. Some questions involved Unix commands to find unique lines in a file and pipes. I had never needed these commands and therefore could not answer. I also encountered a technical term I had never heard of ('memoization'). While I couldn't answer that specific question, I was able to answer most of the others.

According to the feedback I received from the recruiter, these were deal-breakers, and they did not recommend me for further discussions. I believe Google was invented for a reason, so we don't have to memorize things we rarely need.

Therefore, I believe the interview did not measure deep knowledge, technical skills, or personal skills. I appreciate their tough decision-making, but I find it difficult to believe it's a realistic goal to know all Unix commands and technical terms unrelated to one's field.

These kinds of questions are easily found if one knows what to look for. Instead of testing memory, they should try to ascertain how people actually solve real problems.

For the reasons I've mentioned, I cannot recommend the company, as I believe it would be a waste of time.

Fibonacci coding, Unix commands, Big-O notation related stuff.

Most of the questions are actually copied from a book called "Cracking the Coding Interview".