In Product Gym, we have encountered many people that have been either students or have been teachers at our courses that have dealt with noteworthy companies like Spotify. The music streaming giant has been heavily pursued as a great place to work at by Product Managers and non-Product Managers alike. However, when it comes to applying for a Product Manager position at Spotify, it becomes very hard to get in, as they are obviously selective with any position. It’s therefore very important to gain any advantages you may have the opportunity to have.
Thankfully, we here at Product Gym have had experience dealing with the application process at Spotify. We have written some basic questions that we believe will be asked by any of their recruiters or hiring staff at any stage of the interview process after applying. These questions primarily focus on the technical side, with an emphasis on app design and engineering. As a digital app available to download worldwide by millions of consumers, Spotify will have an eye on prospective hires having a solid technical background with strong app design and coding skills. We here at Product Gym have provided access to those questions and broke them down into three simple categories: candidate background, usability, and development. People wanting to work at Spotify, but worried about being unprepared will have a leg up on their competition and answer these questions with heavy preparation.
- What kind of information did people get from the product you built and how did they use it?
- What are you looking to gain?
- How do you see the role of Product Manager? In a new role for you, what things are you excited to learn, grow and develop?
- How technical did you get working with engineering? Did you help engineers handle tickets and plan sprints, or did you hand off what you needed and leave it to them?
What are 3 productivity apps that you really like using and 3 you thought were poor but had potential?
- If you were in charge of a product, what are 3 new features you would propose, and why?
- Let’s say you’re on the team for this product and they think these features are interesting – how would you prioritize which feature gets worked on?
- How would you quantify impact or success?
- What are your thoughts about alignment with business and organizational goals – if the top-line goal is growing the upper funnel, does that change anything in how you prioritize?
- How familiar are you with Google Analytics?
- Imagine you’re working at Google in 2008 and you have an idea for a free web product that lets anyone who owns a domain get an understanding of the kinds of users they have and traffic they’re getting. How do you explain the technical components needed to create an MVP to the engineering lead? What are the technical components you’ll need to get the product off the ground?
- On the information collection side, what are the key identifiers and data you need to collect to power the analytics?
- How would you collect the audience and behavioral data?
- What technical components are needed to enable the end-user’s dashboard view – how does the backend look?
- Clarify how statistical significance factors into your data model.
- What are the smaller components of tech that need to be built out in the dashboard view of the web application?
- Clarify how you would handle data exports. Let’s say it turns out everyone is using the export feature in your MPV instead of the dash – do you see that as standard usage or an opportunity to improve the dashboard? How do you think about that?