Description:

The Personalization Team at Spotify aims to understand the audio world to provide personalized recommendations to users, enhancing their listening experience.
The team consists of technologists, product insight experts, designers, and product managers located in Boston, New York, Stockholm, and London.
Spotify is seeking a Backend Engineer to join the Search team, which focuses on helping users efficiently find and discover content.
The role involves designing, developing, and delivering robust and scalable backend systems and APIs.
Collaboration with engineers, product owners, and designers is essential to identify and solve challenging problems and build new product features.
The engineer will be responsible for writing clean, maintainable, and well-documented code while adhering to coding best practices.
Participation in the improvement of software development standards and practices is expected.
Staying updated with emerging backend technologies and best practices is crucial.

Requirements:

Candidates must have experience writing distributed, high-volume Java services and know how to deploy and maintain them in production.
Comfort in reading and writing Python code is required.
A good understanding of data structures and algorithms, with the ability to apply them to design pragmatic solutions, is necessary.
Excellent analytical and problem-solving skills are essential, along with the ability to communicate ideas to both technical and non-technical audiences.
A passion for working in an environment that encourages experimentation and quick iteration is important.
Candidates should believe in the power of data for informed decision-making.
A commitment to quality and an understanding of what it means to ship high-quality code are required.
Practical experience with Kubernetes is necessary.
Experience managing and operating scalable search engines like ElasticSearch or Vespa is also required.

Spotify offers flexibility in work location, allowing employees to work where they are most productive within the EMEA region, excluding France due to on-call restrictions.
The team operates within the Central Eastern time zone to facilitate collaboration.