![]() Each team would become responsible for one piece of our Search stack - meaning one team would be responsible for getting data into Search, another team would be responsible for the quality of personalized Search results, another team would be responsible for our Search APIs, another team for insights, and finally, a team would be focused on our company bet, podcast Search. We decided to take a different approach to organizing our teams. This meant that we were creating new teams all the time (well, not all the time, but almost every quarter).Ģ020 was the year for us to try something new. But we quickly learned that problems come and go, new problems arise, and priorities can change unexpectedly. ![]() Given the increasing number of user issues we were trying to solve at the time, we decided to organize ourselves around these problems. In the beginning of 2019, we already had a handful of teams working across the Search infrastructure, as well as the machine learning and backend systems. This post details the challenges that emerged as teams began to scale. Spotify continued to grow, reaching 345 million users in December 2020, and Search grew with it. Earlier on, only a small group of people were responsible for the end-to-end experience that encompassed the infrastructure that held Search together, the backend system that powered the personalized results, and the desktop and mobile interface that delighted our users. Since Spotify’s launch in 2008, Search has been a core piece of the user journey, and it’s where we’ve increased our investment and focus over time. Spotify Search is no exception, helping a vast majority of users find joy through search, regardless of the language or method used to search, both typed and spoken. When users come to any kind of search, they already have something in mind, whether they come looking for one thing in particular or are open to becoming inspired. ![]() ![]() ![]() Search is a well-established functionality across different industries, devices, and applications. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |