Overview

Spotify Javascript Coding challenges

• You need to solve at least one challenge in order to win a Spotify prize. Each problem has different difficulty, so feel free to start with the problem you prefer or that is more relevant for you.

• Disclaimer: You need to be at the conference where we present the challenge, in order to pick up the prize.

• You don’t need to complete the 4 points, or even have a perfect solutions, we will enjoy to discuss with you your solutions, so come to talk with us. Also, .. we are hiring ;), if you enjoyed to implement those challenges, check with us what are our open positions.

How to send the results

1. Work locally in a custom branch git checkout -b my-solutions

2. When you are ready with the code, you have several options:

   • Option 1: Send us the code via e-mail: lxjs2013@spotify.com
     • First generate a patch: git diff --no-prefix master > solution.patch
     • Send the generated patch to
     • Use the subject [Challenge]
     • Alternative: just send us the link to a secret gist (gists.github.com)
     • We will review and reply you, including details about when you can come to the stand.
   • Option 2: Just come to the Spotify stand, to show us the code and talk with us.
   • Option 3: In case that you don't even have a computer at the conference, you can discuss potential solutions with us. Just go to the stand or find a Spotify engineer.

Challenge

• Custom DOM wrapper - 3 Points
• Communication between tabs - 3 Points
• Unit testing and refactoring - 2 Points
• Cross-browser code - 2 Points
• Secure enough - 2 Points
• Mouse issue - 1 Point
• Risky search - 1 Point
• Good CSS compatibility - 1 Point
• Static files nightmare - 1 Point
• Mathematically wrong - 1 Point
• Top 50 tracks - 4 Points