Workshops & Webinars in Mountain View

All   |   Workshops   |   Webinars

Intro to Machine Learning with Google

We already know about online sites that have recommendation engines. Those are one form of personalization tools that use Artificial Intelligence. Another one is voice activated intelligence assistants like Siri but what exactly is machine learning and what can it be used for?

Melody Ivory, a product manager at Google Home, works with Machine Learning every day blending it with hardware and software. In a recent event, she gave us an introduction to Machine Learning.

 

 

Intro to Machine Learning with Google PMMelody Ivory

Product Manager on the Hardware Goods team at Google Home. Before Google, she worked at GE Power’s digital transformation team as a PM for software to control power plants. She has experience in other fields than PM because she has also held PM, UX, and software developer roles at Microsoft, NetRaker, and the Internet Factory and served as a UW professor. Holds a Ph.D./MS in computer science, BS in CS/Math, and MBA.

 

 

Distinguishing Machine Learning from other fields

Machine learning, deep learning, A.I… So many different but oh so similar terms. How are they different from each other? Machine learning & algorithms can be used, for example, to define whether a web design is good or for optimizing the way a gas turbine works in a power plant. It can also be used in content suggestion like in Google search. “Machine learning is all about how you teach a computer to learn.” It’s not the same thing as A.I., but it’s a part of it.

Before diving into Machine Learning let’s look at this list we put together to define what Machine Learning and the others really mean.

Computer Science: Theories, experiments, and engineering to inform computer design or use.
Data Science: Methods, processes, and systems to extract insights from data.
Analytics: Discovery of meaningful patterns in data.
Artificial Intelligence/A.I.: Intelligence exhibited by machines to mimic a human mind.
Machine Learning: Computers being able to learn without someone having to hand-code each step. Machine learning is a subset of A.I. that consists mainly of algorithms and data.
Deep Learning: Multi-layered algorithms for learning from data. Deep learning is a subset of machine learning, and it’s about doing things with a lot of data and A.I.

 

Intro to Machine Learning with Google PM

 

Machine Learning and Algorithms

Now let’s dig into it. The main thing in machine learning is that you have to ask good questions to get good answers. Before you can even start the process, you have to know what you want to know. After that, you think about the algorithms that you’re going to use as part of the process. “The algorithms dictate the type of data that you need to collect or how you need to prepare it to go into the algorithms.”

The algorithms determine what kind of output you get, so you also need to know the type of answers you want before you start doing anything. The algorithms have to be determined before collecting the data. The key is to use good data to get good data. After the process is finished, it’ll be repeated with an improved model.

 

Intro to Machine Learning with Google PM

 

Important questions used in Machine Learning

Like mentioned before the most important thing in Machine Learning is asking good questions. There are different questions in separate stages of the process that can help answer these various questions well.

The question what is to monitor. If we do this then what. Why diagnoses the situation. When we did this why did that happen? Why adds more value and more information that you can act on but both of these questions answer to something that has already happened in the past and therefore they only give you information.

Predicting question when can tell you what will happen and it adds even more value than why because it can give insight at the moment. The last stage is optimizing with questions like what if and how to. They can tell you in advance when something is going happen and give you a chance to do something about it. Questions can drive value to Machine Learning.

 

Machine Learning process

The process itself is divided into two phases; learning and predicting. Your goal is to get a model done by using algorithms. In the first phase you start by choosing the questions you want to ask and the algorithms you want to use. Next, you collect the data and clean it. This takes most of the time because it can take a while getting the good data and cleaning it up.

The next step you build and evaluate the models and algorithms, and lastly, you deploy the model. In the second phase, you put your new data into the deployed model to get the answers you’ve wanted all along, and the last step is adapting.

 

Intro to Machine Learning with Google PM

 

Questions from the audience

 

How did you get the algorithms to define whether your web design was good?

Keep in mind that I did that in 2001, but I used algorithms from IBM SPSS which is a statistics program. Today I would use R Project because it has all these algorithms for free. It also has different program environments to do, for example, commandment lines and batch stuff. The reality is that you don’t know exactly what parameters to use. Every algorithm has a different sense and a lot of the times you just have to try it over and over again to see the results.

 

Can you talk about a product that was supposed to be using machine learning that did not work?

I have not worked on a product that tried to use machine learning and didn’t work because if it doesn’t work you used the wrong algorithms or you got the wrong data. You just need to keep trying until it does. Sometimes you have to make different transformations to your data to get it to work.

When you step into the hat of “I’m building something in machine learning” you don’t stop until you’ve built something that works and you through everything at it. That’s how it works.

 

Intro to Machine Learning with Google PM

 

What are the opportunities working in this field part-time?

You can get experience and get paid through, for instance, Kaggle, a crowd source data mining company, where you do competitions building models. Whoever builds the best model wins prices. That’s one way to do it part-time and on your own time. You choose which things you want to compete in. If you win, you get money.

But if you say I want to get paid for this 30 hours that I worked I’d say consulting is a better opportunity. On Upwork the fastest growing category is machine learning, people with machine learning expertise. If you have that expertise, there are a lot of startups and a lot of larger companies looking to bring freelancers into the company, so there are easy ways to get into it.

 

Intro to Machine Learning with Google PM

 

Machine learning is on top of the world right now. It’s something that everybody’s talking about and that a lot of companies are investing in. It provides, even more, opportunities for Product Managers and more interesting things to gain knowledge about, and on top of everything, it’s fascinating! Get into it and build your skillset

 

Have any comments? Tweet us @ProductSchool

We teach product management courses in San Francisco, Santa Clara, Los Angeles, and New York. To learn more about our upcoming courses and how to apply click over to our course page.

How Your Background Can Help You Launch a Product Career

There truly is a market for Product Managers and we don’t mean just the big tech companies like Google, Facebook and Spotify that are always hiring. We’re talking about the huge amount of companies that may not fall into the tech category but that still build software and need Product Managers. So what kind of background and skillset do you need to launch a career in Product? Our Slack community sent out some questions to the Product Manager at Henry Schein to discuss this.

 

How Your Background Can Help You Launch a Product CareerDan Larsen

Product Manager at Henry Schein, previously a Product Analyst, Quality Assurance Engineer and Support Team Leader in the same company. Holds a Bachelor’s degree in Business Management.

 

 

 

How do you translate technology to an organization that focuses on dental equipment?

Henry Schein does distribute dental products, but we also build software and technology solutions for dentists, which is the division of Henry Schein that I work in and focus on.

 

What technical skills does a good product manager need to know?

I think it varies and no two PM’s are alike. Some are more technical, others are more business focused, others may be more customer/industry experienced. The best are strong in all three areas. It’s like baseball, you want to be able to hit, throw, run, catch — have a well rounded game. I wouldn’t focus on one skill, but more on dev processes than actual code or technology.

 

How different is it to be a Product Manager in a manufacturing industry to electronics/app based industry?

I’ve always been in software. I see PM as a partner to development and a leader of the cross functional operations team. If it has to do with the experience of the user, I usually want and have a seat at the table for those conversations.

 

Why should one become a product manager from an engineering background?

I think only you can answer that question, but for me, what I love about product is the diversity, I worked with a customer this morning, then worked on a partner contract agreement, and then worked with development on requirements for a feature. I love business and the competitive side and understanding what influences buyers to make purchase decisions.

 

How Your Background Can Help You Launch a Product Career

 

What skills and tools do you use on the job and how did you develop them?

I love Pendo and use it heavily. I also use Product Plan, Slack, and Asana a lot. The skills just come from experience and making tons of mistakes. I read as much as I can. Don’t be afraid to ask what might seem like a rookie question. My career path was support, then QA/dev, then business/product analysis, so I started in customer service and support then learned dev processes while going to school to study business. Just read as much as you can and continue being in groups like this.

 

I’ve been told that aspiring PM’s should learn everything from Java, Android/iOS, SQL, HTML to CSS. What do you think?

I’m weird, I kind of disagree on the need to understand SQL, JS, etc. I would focus more on the development process. If you’re starting in your career and want to get a good base, I think that’s a great idea, but I don’t think you need to have a CS degree. Get a job in support or do work on your own on the side to build a website. More technical skills are a good thing, but we have 12 PM’s on my team and none have a CS degree. This varies by company, but I don’t think its a must.

 

How do you balance Product-Market Fit (PMF) and metrics very early in a product?

We use NPS very heavily, and I think those concepts can be used before the product is shipped. I like the pragmatic concept that you’re trying to solve problems customers are willing to pay to have solved. Measure and understand the value of your solution, and make sure that your solution is a solution to their real problems. Paper prototypes, interviews, relentless search for understanding of the user.

 

How does someone break into a PM role and why is a PM not in charge of P&L?

For me, I just stuck with my company and as we grew, the opportunity came. I was annoying about it, and made sure the VP and directors at the time knew how badly I wanted to be in Product. I also looked for ways to help the product team before I was in the role officially so they knew I was a go-getter and was about the customer and solving problems.

Be an expert on your product and market. Learn your customer and know what they need to be successful with their business and you’ll bring a lot to the table. PM should be involved and understand the P&L and make decisions that positively affect financials.

 

How Your Background Can Help You Launch a Product Career

 

Could you elaborate on your product ideation & validation process, given your very unique customer set?

For me, it comes from spending a tremendous amount of time with customers and trying to understand their business as well as they do. When you do that, the ideas will be very obvious, and it will come down to determining priority and how to build.

I love the validation process because I like LSS and the data side to the PM job, so it’s fun to say, OK, how many people will benefit from this solution, which segments of the market can use it and what percentage will pay for it. What does the competition look like. Think about how you will market the product before you ever build it — what’s your unique value proposition?

 

Can you talk a little bit more about the advantages and challenges about working with SaaS products?

I’ve done both client server/license model and SaaS model. The SaaS advantage is the ease of deployment to everyone and how much you can learn quickly. The challenge is that if your solution is business critical for the user, it’s a huge responsibility to keep the app running and performing well. It’s a constant effort. Also, typically barriers to exit can be lower if they didn’t put down a huge chunk of money for an upfront license. There are lots more, but that’s what comes to mind for me.

 

Any tips for a brand new Product Manager just starting up?

This might sound simple, but make as many friends as you can. A good product manager needs to have strong relationships with his or her team.

 

How Your Background Can Help You Launch a Product Career

 

What has mentorship looked like in your career, especially when starting out in PM? Any advice?

My mentor is the reason I became a PM. I saw what he was doing and thought, wow, that looks like an awesome job, I want to do that. Being a good mentee would be asking for opportunities to help, in any capacity, ask for recommendations of good books. Most of my mentors have been inside my company, because there was a natural connection and introduction to those people, but it doesn’t have to be. I think it’s great to have an external mentor as well.

 

What’s the right time to become a PM? I’ve done SW engineering for 6+ yrs and been a Business IT Consultant for 6+ years.

I say go for it. I see three pillars to a good PM – technical, business, industry. You have at least one of those nailed. I say go for it now.

 

How do you communicate to your customers, if what they are expecting is unreasonable?

Such a tricky thing to do. It’s not easy. Users will very often gravitate towards offering the solution they think they need. Redirect that, and ask about the pain point. What is the problem they have. If the customer asks for a button, ask what pain the button will solve — that info is gold for you. If they always go back to the solution and it really is wrong, illegal, not important, then just say thanks for the feedback.

You can also use a tool like UserVoice — if no other users ask for it, then the crazy user will understand why its not being built — no one else wants this. If tons of people ask for the solution that sounds crazy, then you have some work to do to understand why.

 

How important it is to fail in a PM role to understand the real need of the customer for a product?

If you never fail, you’re probably playing it too safe. I think a failure in a PM role is spending tons of money on a product that no one wants or is willing to pay for. Now, if it’s buggy or something then it’s not all on you as a PM, but if the premise is wrong and you don’t check and validate that before spending on dev, that’s probably a PM failure. Miss small and often, don’t miss huge on a big bang release idea.

 

How Your Background Can Help You Launch a Product Career

 

Have you ever wondered why companies require their PM’s to be a PM elsewhere first?

Chicken and egg problem. How do you get experience if no one will give you an at-bat? I say just stick with it. Be relentless about your desire to be a PM. Honestly, it took me years longer to get a PM job than I thought it would. I don’t believe in luck, but I do believe in working hard and taking the opportunities when they come. Stick with it, you’ll get a chance.

 

Is UX /UI Design, primarily a PM responsibility or a required skill for a good PM ?

I don’t think it’s required, but it does help. I did UX\UI business analysis stuff for a year or two, and absolutely loved it, and feel it helped me bridge to a PM job. I don’t think you have to be a design expert to be a good PM, but it depends on your company and how strong your dev\design team is. Our team is quite strong, so I don’t spend a ton of time on design.

 

Do you think a role in the consumer goods industry can help or hinder an eventual transition into tech?

I don’t think it will hurt you. All of the experiences may not translate, but a huge key to a PM is understanding the reason buyers choose a particular product or service, and there can be tons of similarity regardless of it being consumer goods or technology.

 

Any final advice for aspiring product managers?

My last words of advice are to read as much as you can about business. I recommend books like Good to Great, The Lean Start-up, Blue Ocean Strategy, The Ultimate Question, etc. Spend as much time with your users as you possibly can, have empathy for them and it will benefit you. Stick with it, if you aren’t yet a PM, dig in, educate yourself, make as many friends as you can and make sure everyone knows that you want to be a PM and you’re willing to put in the work and help out to make it happen.

 

How Your Background Can Help You Launch a Product Career

 

Have any comments? Tweet us @ProductSchool

We teach product management courses in San Francisco, Santa Clara, Los Angeles, and New York. To learn more about our upcoming courses and how to apply click over to our course page.

Student Featured on Breaking Into Startups Podcast

Jessica Uelmen is the Product Manager at Fitbit and a Product School graduate with a major in electrical engineering. She was featured in a recent podcast by Breaking into Startups and we were excited to hear even more about her success through the interview. She talked about not only how she, a hardware engineer, became a product manager but also how taking the product management course helped her along the way. 

 

Student Featured on Breaking Into Startups Podcast

 

Getting into engineering

Growing up Jessica Uelmen was a self-confessed nerd. She loved reading, learning things and most of all she loved computers. She was fascinated by the easiness of sharing thoughts and ideas on the internet. At the age of 13 she built her own website, but in college, she was very interested in musical theater.

Even though she had a great interest in computers and technology, she didn’t think that engineering or programming was a job she could do. It wasn’t until her Sophomore year that she decided to major in electrical engineering.

 

First job after college

After college, she went on to work at Parallax in their education department designing boards and products and creating projects. There she moved on to be the Engineering manager for the whole company. After a couple of years at Parallax, she wanted to relocate to the Valley.

Because of her passion for education, she got a job as a program manager at Udacity. Udacity is an education company that offers free Nanodegree programs for technical and some non-technical programs. They’re designed to get people jobs by teaching them the skills they need to get the job they want. Jessica wanted to be close to education but also stay close to digital interaction.

 

Student Featured on Breaking Into Startups Podcast

 

Transitioning into product

At Udacity she got interested in Product Management. However, when she asked other people and product managers what the job included, she couldn’t get an undivided definition. Jessica wanted a more solid ground for the whole role. She heard about Product School from a friend and decided to attend it in order to be able to create her own definition to what product management actually was.

 

Product School

At Product School, the part that she liked the most was getting live feedback. She also enjoyed learning from someone who was experienced in product management and that is a product manager in real life.

After the course, Jessica applied for a job at Fitbit for the third time and got the job. She thinks that Product School gave her the confidence to be able to not only speak about product management as a role but to be able to connect all her past experiences to a product role.

 

Student Featured on Breaking Into Startups Podcast

 

Check out Jessica Uelmen in an article From Product School Student to Fitbit PM.

Have any comments? Tweet us @ProductSchool

We teach product management courses in San Francisco, Santa Clara, Los Angeles, and New York. To learn more about our upcoming courses and how to apply click over to our course page.

All the Ways That A/B Testing Sucks by Yammer PM

A/B testing can be Product Manager’s best friend. What is A/B testing and are the pros and cons of using it? It’s false thinking that A/B testing means creating a new experience, giving that to all of your users and then checking what happens afterward. This is not how it works. A/B testing is a diagnostic tool, it’s not a cure. It’s only as good as the questions you bring to it, and you don’t give it to all your users. But it’s not perfect, and at times it really sucks.

 

 

 

All the Ways That A/B Testing Sucks with Yammer PMAnna Marie Clifton

Product Manager at Yammer for about a year. Prior to Yammer worked as a PM at Asana. Before breaking into product she was a gallery manager in New York. Co-hosts Clearly Product Podcast that publishes new content once a month.

 

 

 

What is A/B testing?

A/B testing is something that is a big part of being a Product Manager. To put it simply it’s a statistically valid way to see how good your future ideas are. You take an experience, create a comparable experience and launch that to half of your users. By releasing two versions at the same time, you can measure what works better and what affects the users. Then you follow the metrics and choose the one that did better.

The reason behind launching the new feature only to 50% of your users lies in the fact that you can compare the results to the other 50% and see which one did better. You also have to have the both experiments running at the same time to be able to define what events e.g. holidays affected the results.

 

All the Ways That A/B Testing Sucks with Yammer PM

 

The rosy side of A/B testing

After spending so much time on your test, it feels great at the end when you can choose one and say that it did better. By A/B testing features you get lots of valuable data about what to do and what the users prefer. You can make your product better and your users happier.

 

Why A/B testing sucks from the engineering point of view

 

It can be tough for Product Managers to run A/B tests but they’re not the only ones it’s hard for. The engineers also might find it tough because writing code for the experiment takes longer than coding for shipping. They need to build an experience that works as well as a control experience, and that takes a lot longer than just building and shipping.

They also can’t make changes when the experiment is running. If a bug was found in the test in the worst case the experiment has to be stopped, the bug needs to be fixed, and then the test can be started again. In some cases, the bug may have to be left there and not interrupt the experiment, but sometimes the bug can cause a negative user experience.

 

Why A/B testing sucks for PM’s

As much as A/B testing brings joy to everyone in the team when it’s finished during the process, it can be a pain in the a**. It sucks for PM’s because it takes a lot of time. You want to find a retention to measure, but retention takes a lot of time to measure. You need a ton of users on both sides of the test, but that doesn’t happen in one day, so you have to wait for that. Users also don’t like change and sometimes they don’t act the way you’d want or expect them to, and so again you have to wait.

It’s also a lot of work beforehand. You need to define the questions you want answers to because A/B testing is not going to give you an answer to a question that you don’t ask. That can take a while. A lot of work is required after the experiment as well because the results tell you what but not why.

 

All the Ways That A/B Testing Sucks with Yammer PM

 

Questions from the audience

 

How do you get comfortable with the possibility of things going wrong?

 

It’s experience. It’s failing and watching yourself not get fired and repeating the same thing all over again. I talked about this to my boss’ boss and about three-four months after I started at Yammer. I said that I’m scared of being fired all the time and that I’m messing something up. He responded that it took him about a year to get over the fear of thinking that he will get fired every day.

As product managers, we have a tendency to be more risk tolerant and to deal with that. I’d encourage you to do two things. Think about the times that you failed and how bad it really was. It’s usually worse in your mind than it actually was in reality. Look for other people that have failed and how they’re still doing because no one is in jail for messing up an A/B test.

You will fail, and you need to own that. You have to come to terms with that, and that will help you figure it out. Mentors will help you as well.

 

All the Ways That A/B Testing Sucks with Yammer PM

 

Are there any other types of testing than hypothesis driven testing?

I’ve never worked in an environment that didn’t. I think people assume that you build an experiment and then you look at the data and then you learn something. There’s that pre-work of establishing what you plan to learn before you build the experiment and then you look at the data see did you learn it was it true or not.

It drives for really pure hypothesis and pure product development process and it helps you make really effective trade-offs around is this necessary in order to learn the thing we want to learn or not which is one of the most helpful things about it.

Some can be more intuition driven rather than hypothesis and testing driven but if you’re going to do an A/B test you’re really going to want to have a really solid hypothesis before you kick one off.

 

How does one land a job at Yammer?

There’s a lot written about this on Medium and other sources. My experience was that I came from Asana and the PM at Asana had worked with the PM at Yammer before, and we got a coffee, and it all turned into a beginning of that conversation.

We have a product homework, so it’s a very product exercise driven process. I’ve never once looked at a resume of someone that has applied at Yammer. Our recruiter will do that and a minor screening. Then we have a product challenge which is a home assignment about what people think about product, testing, and hypothesis and that’s the only thing we look at. That’s the resume to determine whether to interview someone or not.

 

All the Ways That A/B Testing Sucks with Yammer PM

 

After all the testing and time consumed in it the sad part is that you still don’t know for 100% certainty that the thing you saw happen happened because of what you did. You just have to trust the test and see where it takes you. A/B testing totally sucks but it’s still worth it.

 

Have any comments? Tweet us @ProductSchool

We teach Product Management, Coding for Managers and Data for Managers courses in San Francisco, Santa Clara, Los Angeles, and New York. To learn more about our upcoming courses and how to apply click over to our course page.

5 Reasons Why It’s Important to Understand Data

In Product Management, the most important things are to be able to work with your team and understand who you are building for and why. How do you get to know your customers? And how do you develop the ability to communicate with everyone? The key is building up your skillset as much as possible.

 

5 Reasons Why It's Important to Understand Data

 

We never stop learning in Product management, and in tech in general, so why not learn technical skills as a PM? Why learn data? Here we give you five good reasons:

 

Understand customer profiles

To be a good Product Manager you need to know what your customers want, what problems, habits and preferences they have. To figure this out you define the customer profiles. Putting together the profiles is one thing but you need to understand them as well. This is where you need data knowledge. Your customers’ behavior affects your decision making and understanding the customer profiles allows you to make good product decisions.

 

Make better product decisions

Learning data helps PM’s make better product decisions. One of Product Managers’ jobs is to find out if the product is successful and how different changes affect the product. For this you need feedback and data together. Understanding how to interpret the data will allow you to make better decisions about your product.

 

5 Reasons Why It's Important to Understand Data

 

Help you communicate with your data scientist

Because the teams work cross-functionally together knowing data and being able to talk about it with your data scientists is a great advantage. It’s like learning their language. You’ll be able understand them and you can better communicate your questions and ideas to them.

 

Time optimization – deciding to work on one thing means not working on another

Knowing data will help optimize your time by defining urgent things from other urgent things. This will require trade offs. You’ll have to be aware that if you work on one specific thing now it might affect another thing negatively somewhere else. However, knowing data should give you a pretty good idea what that change might be and what kind of effect it will have. Every time you choose to work on something it also means not working on something else. Make sure you choose the right one.

 

5 Reasons Why It's Important to Understand Data

 

Understand what your customers really think about your product

While feedback helps you find out what that group of customers that respond are thinking about the product data provides larger scale of answers to who exactly your customers are in all, what they use your product for and also more widely what they think about it.

 

Have any comments? Tweet us @ProductSchool

We teach Product Management, Coding for Managers and Data for Managers courses in San Francisco, Santa Clara, Los Angeles, and New York. To learn more about our upcoming courses and how to apply click over to our course page.

How to Get a Product Management Job at Spotify

Spotify needs no special introduction. Everybody knows that it’s a cool company that changed the way we listen to music. Originally from Sweden, they now have offices in 20 countries. Because it’s such an international company the culture within the company is very diverse and always changing. If you want to become one of the legendary Spotify PM’s, here’s how:

 

How to Get a Job at Spotify

 

Skills needed at Spotify

Previous experience: Besides being awesome the applicants need to have some previous experience in product beforehand. Depending on the role that they’re applying for they need to have previous experience either working in cross functional teams, know iterative development principles and practices or be experienced in managing and developing software products.

Technical background: In Spotify they’re agile. Technical background is not necessary if you can compensate it with other qualities. Understanding the importance of data as the most powerful tool in decision-making is required as well as some knowledge of agile methodologies. If you are knowledgeable and passionate about music they can overlook your lack of technical background. It’s required that you know one of the two.

Spotify user: To apply for Spotify make sure you know how to use their main product. Applicants are expected to be at least engaged Spotify users or understand the basics of the streaming music business.

Preferred characteristics: Spotify wants to hire people with different backgrounds and experiences because they bring diversity into the teams. They believe this will create a better environment for the employees which will result in a better product. They also want people to be curious, hardworking, passionate, compelling storyteller and possess good instincts, as well as a critical mind. They are always open for ideas and changes so you should have the ability and desire to truly impact Spotify.

 

You can check out all Spotify job openings here.

 

Interview questions at Spotify

Prepare to discuss these following topics in the interview:

  • Experience – Talk about the one role in your entire career that is most applicable to this role.
  • Spotify as a product – Give us real-world examples about our product.
  • The media space – Give us real-world examples about the digital media space.
  • The music industry – Give us real-world examples about the music industry.

 

How to Get a Job at Spotify

 

The interview process

Spotify receives thousands of resumes a year, and most people put lots of effort into their applications so if you don’t hear back from them in a few days it’s okay. They haven’t forgotten about you. Here’s what you can expect from the interview process:

  • It takes a couple of months (5+) so be prepared.
  • Send out an online application
  • HR screening(s) over the phone
  • Multiple video calls with hiring manager, service delivery lead, peer, and clients.

To help you crack the product management interview check out this video with Randy Edgar, the Product Manager at Uber and this article. 

 

How to Get a Job at Spotify

 

How to write a resume for Spotify

As much fun as it is to come up with creative and exciting ways to present your resume keep in mind the main rule: Keep it simple. Yes, you do want to make your resume stand out, but it’s better that you let the words speak for themselves. Make sure to check out these when putting the application together:

  • Don’t hide what you’re capable of and what your best achievements are. Get to the point and present it the way it is.
  • Make it easy to read. Maybe it’s not a bad idea to ask your friend read it through before sending it out.
  • Make it look good but put more effort into the words than the design.
  • Leave out the things that are not relevant to the position you’re applying for.

 

Where to search for jobs

 

Additional resources to prepare for an interview at Spotify

 

Have any comments? Tweet us @ProductSchool

We teach product management courses in San Francisco, Santa Clara, Los Angeles, and New York. To learn more about our upcoming courses and how to apply click over to our course page.

Apply Now
Prroduct School
Apply Now