Landing an APM Role

A brief, up-to-date guide on how to land an APM role, including information on

applying to PM jobs, the interview processes at different companies, and how
to ace the interview.

We know recruiting can be stressful, anxiety-inducing, and exhilarating at the

same time. We hope this guide helps you make the most of it.
- Claudia, Aveneel, and Jake

LinkedIn | Medium

Getting an Interview 2
Finding PM Jobs 2
Applying to PM Jobs 3
Resume 3
Skill Set 4
Referrals & Coffee Chats 5

APM Interview Processes 6

Coinbase’s APM Interview Process by Jamal Ahmed 6
Microsoft New Grad PM Interview Experience by Aveneel Waadhwa 10
Zynga's RPM Interview Process by Ishita Kumar 13
Duolingo APM Interview Process by Osman Mansur 17
Uber APM Interview Process by Levi Lian 19
Twitter APM Interview Process by Lily Li 22

Acing the Interview 24

Books and Resources 24
How to Answer Product Execution Questions 25
 How to Answer Product Design/Sense Questions 26
How to Answer Behavioral Questions 29
Asking Your Interviewer The Right Questions 30

Getting an Interview

Finding PM Jobs

The majority of APM roles are posted in August and September. Because of the high demand
for PM roles, many job applications are only open for 1-4 weeks. It’s important to be aware that
deadlines can be as early as August (i.e Uber APM, Lyft APM, Coinbase APM). Facebook’s
RPM program closed as of July 30.

For finding PM roles, websites to continuously check are LinkedIn, your school’s job posting
website, and Canvas (formerly Jumpstart). Additionally, there are a handful of other sites that
conveniently collate several open roles. Check them out below.

Resources
● https://apmlist.com/ collates all of the major APM/PM roles along with the number of
spots available at each company.
● https://alanz.me/apm also has an updated list of available PM internships and new grad
roles.
○ It is worthwhile to look through the list, decide which companies interest you, and
subscribe to their emails (usually found on their University page) or check their
careers website periodically for updates
● https://www.linkedin.com/ Set notifications for when jobs titled “product manager”,
“associate product manager” are posted and apply on their website, not through
LinkedIn.
● https://www.canvas.com/ A forum to discuss tech jobs and internships, many jobs, and
info sessions are posted here. This is also a good way to find out if people have received
phone screens/first-round interviews yet for certain roles.
● Hackathons, Career Fairs, Conferences Attending events like these are a great way to
discover new companies, meet recruiters, and interview for roles during the event.
Participating in hackathons is also looked favorably upon by recruiters and a fun way to
gain some tech experience.
○ Grace Hopper
○ Tapia
○ Rewriting the Code
○ PennApps
○ HackMIT
○ TreeHacks
○ CalHacks
○ MHacks
Applying to PM Jobs

Resume
Have your resume reviewed by several people, whether they be friends, family, or people in
your school’s career center. Even better, have your resume reviewed by people who are product
managers or recruiters for technology roles. Your resume should not have typos and it should
highlight your most relevant and impressive experiences.

One common mistake people make is neglecting to quantify their accomplishments. Use metrics
to demonstrate the impact you had in your role, i.e “grew club membership by 60%”, “reduced
crashes by 10%”. Quantifying can be difficult, so think creatively or even ask your previous
managers for advice on how to describe the work you did in internships.

Coursework: If you’ve taken courses in computer science, business strategy, marketing,

entrepreneurship, data analytics, psychology, or design, definitely include those in your
coursework. Ideally include a breadth of courses - don’t list only computer science courses -
since PMs are generalists and need knowledge in a variety of areas.

Skills and Experience: For PM roles, closely read the job description and make sure your
resume touches on those preferences or requirements. Some preferred skills, experience, or
qualities may include:

General Skills
- Stakeholder Management (working to help people with different backgrounds and goals
come to compromise)
- Project Management
- Public Speaking
- Team Leadership
Qualities
- “Scrappiness”
- Analytical
- Creative
- Strategic
- Collaborative
Experience
- Entrepreneurship
- Product Design
- Software Engineering
- Analytics
- Business Strategy
- Marketing
- User Research/Psychology
Skill Set
If you have experience in the aforementioned areas, definitely include them in your resume. If
you don’t, there are short-term ways to demonstrate interest and basic proficiency in these
areas.

Here are some ideas to help you build relevant experience:

Non-Technical
● Write an article on a topic of your choice. Post it to LinkedIn and/or Medium. Especially
impactful articles often bring a new perspective to an important topic, clearly explain a
complex idea, or can curate resources on a specific area
● Take a Coursera course on a related PM topic you are less familiar with, such as design,
psychology, marketing, project management, etc.
○ Human-Centered Design
○ Digital Product Management
○ Agile with Atlassian Jira
● Lead a project for an organization you’re in (i.e a website redesign, planning an event) or
start a new organization on campus!
● Do case studies and post them on a personal website or Medium. Examples could be
running through your process to better monetize Spotify or your proposal for a new
feature on Venmo to convert more users to Venmo debit cardholders. Here are a couple
of example mini-projects from Bin Pande, an incoming APM at Coinbase:
○ Campus Project for Twitter
○ Facebook Mini-Project
● Start answering questions on Quora and link your Quora to your website
● Do some design work for an idea you have (could be designing running clothing, an app,
etc.). You can use Sketch, or Figma, both fairly easy-to-learn design tools. Post it
somewhere and explain your thought process.
Technical
● Design and build your website. There are a ton of great personal websites out there to
get inspiration from! This is a win-win: you can also share it with potential employers
● Build an ML model to solve a problem that you are interested in. If you want to have the
best bracket in your March Madness Tournament, you can build a model to help predict
upsets!
● Code a simple game or app and post it on GitHub or your website.

Referrals & Coffee Chats

Take advantage of referrals if you can! Companies receive thousands of applications for APM
roles and getting a referral means your application is looked at earlier, a huge advantage.*
While there are plenty of examples of applicants with referrals failing to receive an interview,
they can’t hurt, and we feel that are especially important for programs like Google and Lyft.
Use LinkedIn to see what connections you may have to employees at specific companies, and
then reach out to them for a quick chat about their experience. Make sure to ask questions that
show you have done your research - these should be open-ended. Find time to discuss your
interests and experiences and demonstrate that you are a great candidate for the company. This
type of conversation is key. A Coinbase recruiter recently shared with us that the quality of a
referral (how well the employee knows you and can vouch for your background) is key! Simply
sharing that you two went to the same school doesn’t hold much weight.

After the call, you can ask for a referral or they may even offer (employees usually receive
compensation for referrals who become full-time hires). It helps to find people with whom you
have mutual connections or share commonalities, such as the same college or high school.

*Facebook stopped accepting referrals for their RPM program this year to provide a more even
playing field for all applicants.
APM Interview Processes

Coinbase’s APM Interview Process by Jamal Ahmed

This past Fall, I accepted an opportunity to join Coinbase’s first cohort of APMs. I came into the
interview process with no background in crypto or fintech, but was excited by what I’d read
about the company and program, and decided to apply! Here’s a breakdown of the interview
process, and some quick tips to help navigate it.

Interview Round 1: Google Hangouts Screen (30 minutes)

The first round of the interview process was a video call with my recruiter. It was relaxed — we
were able to get to know each other a bit before diving into my background and interest in
Coinbase. I was pretty honest about my lack of crypto knowledge, but was clear about my
eagerness to learn, and talked in-depth about facets of the company culture I’d learned about
that appealed to me.

After a few behavioral questions about my prior experiences, we talked about the high-level
structure and goals of the newly formed APM program. The interviewer wrapped up by asking
me to explain something I’d been learning about for the last month or so, definitely looking to
highlight the Continuous Learning value that Coinbase spotlights in the workplace.

Shortly after the interview, I was informed that I’d moved on to the next round and was sent
some prep materials and example questions.

Interview Round 2: Product Vision & Execution (30 minutes each)

The next round was made up of two half-hour sessions, each dedicated to one of two types of
PM questions:

Product Vision: Also known as Product Design questions, these test a candidate’s ability to think
methodically through a product’s gaps and goals, and look for the candidate to demonstrate
structured thinking and a strong sense of user empathy. You’ve probably come across these
questions before — popular ones include being asked to design a product, improve a product,
or discuss your favorite product.

Product Execution: These questions test a candidate’s decision-making skills, understanding of

metrics, prioritization, and ability to break down a problem into its causes. Once again, applying
structured, methodical thinking is super important, even as the problems may seem completely
open-ended. These questions often ask how you would measure success for a specific product,
or how you would investigate a sudden drop in a certain metric for a given feature.
Product Vision
In my first interview, my interviewer and I introduced ourselves and spoke casually for a bit
(which was good for the nerves), and then dove right into the product vision questions. These
centered around my favorite product — I chose MyFitnessPal, a fitness tracking app that I use
to monitor my food intake and exercise levels. After being asked to name some key metrics for
the product, I was asked to select one as the most important, and come up with some
improvement ideas based on this metric. I cycled through a few ideas using the CIRCLES
framework and ended up proposing a coaching feature that would guide users through specific
nutrition and activity recommendations.

At the end of the interview, the interviewer asked what the product could look like in 30 years at
its absolute peak, and encouraged me to think big. It was a really interesting question that
forced me to think creatively about all of the facets of life this technology could expand to
inhabit.

Product Execution
In my second interview, after some quick intros, I was given a scenario in which I was a PM at
Instagram. In this scenario, usage metrics for Stories were down, and I was asked to figure out
the cause and resolve the issue.

This interview was more conversational than the previous one. I was constantly asking my
interviewer questions to clarify different aspects of the problem, establish the right frame, and
whittle down potential causes. With the insights I got, I was able to single out a few specific
actions that had led to the drop in usage. We spent the rest of our time discussing the
interviewer’s role and experience at Coinbase, which was informative for me.

These interviews took place on a Thursday. The following Monday, I got an update that I’d
moved onto the final round of interviews, scheduled for later that week.

Final Round: Product Vision & Execution (45 minutes each)

The final round of interviews followed the same model as the second round — two interviews,
each focused on Product Vision and Execution questions. The extra length allowed the
interviewers time to ask in-depth questions about my background, which we’d skipped in the last
round, and gave us room to go deeper into the product questions.

A few days before the interviews, I had a prep call with my recruiter, where we walked through
the types of questions that would be asked again and advice to best prepare.

Product Vision
This interview started with a deep dive into my prior experiences. My interviewer asked me to
flesh out my role in prior projects and to talk about the responsibilities and ownership I took on.
After that, I was asked another product vision question, this time asking how I would improve
UberEats.
Once again, I used the CIRCLES framework to structure my answer, asking clarifying questions
and then digging into potential user personas. I spent most of the interview fleshing out these
personas — I felt like the goals and needs of the user were the most important aspect of the
problem, and that my interviewer was pushing me to dig deeper. By the time we moved on to
actual improvement ideas, we were almost out of time!

It’s worth noting here that although you may expect to form a fully fleshed-out proposal in
response to an interview question, you should be prepared to follow the interviewer’s lead and
dive deeper into some of the more important decisions along the way.

Product Execution
This was my last interview in the process, and again, it kicked off with questions about my
previous experiences and their relevance to the PM role at Coinbase. Then we moved into our
execution question — I was asked to determine the key success metric for the Venmo debit
card.

This was a tricky one for me as I didn’t know anything about the Venmo debit card, and didn’t
understand the business model right off the bat. To work around my lack of knowledge, I asked
a lot of clarifying questions and was able to flesh out a few key groups of users of the product
and understand how and why they used it. From there, I listed each group’s key interactions
with the product, and then sorted and prioritized the metrics that came from these interactions
based on what they told us about the product’s success.

After both of my interviews had wrapped up, I had one last sit-down with my recruiter just to go
over logistics. By this point, we had become well acquainted, and I was able to relax and talk
honestly with her about how I felt things had gone. The next day, I received a call with the news
that I’d been extended an offer! I was super excited and signed as soon as I got all of the
documents.

Tips and Prep Advice

Think of the user, first and foremost. At the end of my first product vision interview, I asked
my interviewer for feedback. One of the points he made was that while he didn’t dock me for it,
he would have prioritized user-focused metrics (like engagement with certain features, or user
retention) instead of focusing on business goals like profitability. In my next vision interview,
when discussing UberEats, my interviewer was more excited to do a deep dive into user
motivations than to go through my actual ideas to improve the product. Coinbase prioritizes the
user experience above everything else, and it shows throughout the interview process — be
mindful of that in your responses.

Think big, but stay structured. You should showcase your ability to think creatively and swing
for the fences with your ideas — but the most important thing you can do is demonstrate that
you can think through any problem in a way that’s linear and well-structured. Your interviewer
will look for you to break down the problem into discrete steps, move through them one by one,
and communicate clearly and constantly along the way. Once you understand the question, lay
out a framework for yourself to structure your thinking, and refer to it as you move through each
step.

Stay calm, and ask questions. Just like in any interview, you might hit roadblocks or get
questions that you struggle to break down into small pieces. That’s okay! Ask clarifying
questions to get your bearings, take time to yourself to jot down or think out your next steps, and
breathe — you got this!
Microsoft New Grad PM Interview Experience by Aveneel
Waadhwa

I received an offer from Microsoft for their New Grad PM class last November, so I figured that
I’d share my interview experience to help other people in the process since many people have
DMed me on LinkedIn for interview advice.

Interview Round 1: Phone call on Microsoft Teams (30 mins)

The first round was a mix of behavioral and technical questions. The interview was pretty
relaxed, it was surprisingly with a Software Engineer and not a PM, but you can have your first
round with either of those, so YMMV. He asked me a couple of questions regarding my resume
and past experiences, and then asked a coding question, specifically “How do you convert
Excel column names into numbers?” The first round screen usually revolves around the
interviewee’s resume so I was surprised to get a coding question, but I was able to answer it
convincingly.

A week after my first round, I got an email inviting me for the virtual second and final round
interview that took place two weeks later.

Final Round: Video Interviews on Microsoft Teams (45 x 4 mins)

The final round interview was a virtual interview on Microsoft Teams with check-in at 7:20 AM
Pacific Time (!!!) and my interviews were held from 8 AM to 11:45 AM. I missed a great
opportunity to visit the Microsoft campus in person in Redmond, Washington due to the
pandemic, but I had a great experience talking to all my interviewers, the recruiters, and seeing
other interviewees at the event.

Final Round: Interview #1

My first interview in the final round was with a PM lead who is now going to be my future
manager (!!!), and both of us instantly hit it off as we had common interests such as the same
music taste and both of us support Manchester United. He helped me calm my nerves and we
had a great initial chat since it was very early in the morning for both of us, and then he followed
up with some behavioral and product questions.

The behavioral questions were very insightful and forced me to reflect on previous internship
and project experiences. The product questions were similar to the usual favorites such as
“What is your favorite product, and how would you improve it?” I answered the product
questions by talking about Spotify and how I could improve it by implementing more social
features into the platform as I listed out my ideas, cut them through prioritization, and then finally
summarized them.

Final Round: Interview #2

My second interview was with the manager of my first interviewer, who was also a Manchester
United fan, which allowed me to form a connection with her. She proceeded to ask me a lot of
behavioral questions, including a lot from my past experiences, again forcing me to reflect
deeply on the lessons I learned through my college years and how I have changed since then.
She also explained the PM role at Microsoft to me very clearly and elaborated on what they
usually look for in PMs, which helped me better understand how to approach her questions and
the subsequent interviews.

Final Round: Interview #3

My third interview started similarly to the first two interviews, with introductions and behavioral
questions to help me ease into the interview. The interviewer then asked me one product design
question and then one scenario-based question. The product design question asked me to
create a COVID tracing app specifically for buses (so that we only focus on a narrow target
audience to simplify things). I answered the question with the CIRCLES framework and laid out
my thought process step-by-step by identifying the customers (bus passengers and their
different personas, and bus drivers) and their needs, and ending with a list of features that were
the most important for the MVP.

The scenario-based question put me in a position where I was the PM at an e-commerce

platform where bots had accounted for 40% of purchases made on a certain Black Friday that
caused some servers to fail. My job was to identify the problem and suggest solutions, which I
answered by prioritizing the identification of the problem according to the location of the servers,
then addressing the security system to make it harder for bots to make purchases, and
eventually to increase server space as a last resort.

P.S: CIRCLES = Comprehend the situation; identify the customer; report the customer’s needs;
cut, through prioritization; list solutions; evaluate tradeoffs, and summarize your
recommendation.

Final Round: Interview #4

The fourth and final interview is called an as-appropriate interview and only given to the
interviewee if 2 of the first 3 interviewers liked the candidate. The final interview is always with a
senior member of the team, and mine was with a Principal PM who had worked at Microsoft for
25 years. The final interviewer also tends to have veto power over your candidacy, so I
approached the final interview as a boss battle at the end of a lengthy video game.

The interviewer asked me a few behavioral questions based on my past experiences, and then
we spent the remainder of the interview going through a product design question where I had to
design an internal tool to monitor the supply chain of products inside Microsoft. Again, I utilized
the CIRCLES framework and laid out the ideas that I had regarding how the product should
look, and the interviewer seemed to like my response. At the end of the interview, I asked the
interviewer a few insightful questions to pick his brain about his time at Microsoft and the
products he worked on.
Final Thoughts

After my final round of interviews, I emailed the recruiters and thanked them for helping me
throughout the process as I patiently waited for them to reach out to me. I finally heard back 9
days later with the amazing news that the team had decided to extend an offer to me. I was also
provided the opportunity to talk to my future manager who fully convinced me to join the team
and I signed my offer a few days later.

I am looking forward to finally visiting the Microsoft campus in person when I move to Seattle
later this year

The resources I used to prepare for the interview process consisted of the books Cracking the
PM Interview, Decode and Conquer, and the interview preparation platform Exponent and their
YouTube channel. Additionally, mock interviews helped me a lot to get honest feedback and
improve my interviewing skills. I also utilized Glassdoor, and articles such as this one to
understand the interview process at Microsoft. These different resources helped me understand
different approaches and frameworks for PM interviews and eventually helped me land a dream
role.

Microsoft’s mission is to empower people around the world and hence, they look for product
managers who can empathize with the customer and identify their needs before jumping to a
solution. This mission is one of the biggest reasons why I decided to join Microsoft as I want to
learn how to develop products for people around the world, who have various needs and use
cases. Microsoft also invented the product manager role, so I couldn’t think of a better place to
start my product management career than the place that started it all.

I cannot wait to get started at Microsoft and work on products that millions of people will use!
Zynga's RPM Interview Process by Ishita Kumar
Hi, my name is Ishita, and this year I received an offer to join Zynga’s RPM class. Since I know
how hard PM recruiting can be, I wanted to use this article to demystify a part of the process.
Here’s a little more about my personal experience, and how I navigated recruiting with Zynga.

Applying to Zynga

My interview process with Zynga began with applying (obviously). I applied a little late to the
program, but with a referral. I know some people who applied early and moved to the first round.
In general, I highly recommend applying with a referral if possible - it can only help your
application. I heard back from the recruiter for the position that I was invited to do a first-round
phone screen a month after I submitted my application.

First Round - Phone Screen

My phone screen was with a lead product manager at Zynga. After some quick intros, we dove
into a couple of behavioral and a few product sense questions. For this round of interviews, the
product in question was a social media app, so you didn’t need to be a gaming expert to get
through the product questions. However, Zynga is still looking for people who are interested in
mobile gaming, even at this round, so make sure you can communicate your interest and
experience with gaming.

Second Round - Take-Home Assignment

Two weeks after my phone screen, I was invited to complete Zynga’s take-home assignment,
the next stage of the interview process. We were given a week to complete it. The assignment
consisted of four questions covering a variety of topics, including the key design process of
free-to-play mobile games, the mechanisms mobile games use to successfully scale and
monetize, and the analysis and modeling of hypothetical business scenarios. I felt most of my
success in this round of the process was due to the amount of time I spent playing Zynga
games and researching the mobile free-to-play industry.

I was notified that I would progress to the final round a week after the take-home assignment
was due, but because of the holiday season, our final round took place 3 weeks after this
update.

Final Round - Superday

My final round with Zynga consisted of 4, 45-minute interviews and a 45-minute slot to present
my take-home assignment. This was spread out over two days - with my 4 interviews taking
place on my first day of interviews, and my presentation taking place on the second day.
Day one consisted of the following interviews: design, analytics, fit, and blend, with a 45-minute
lunch break in between my first and second rounds. All of these interviews were with different
product managers/leaders in the company.

Product Design Round

The design round of my interview was pretty straightforward and was similar to a classic “design
x to achieve y goal” type of question. For this question, my interviewer based my question
around my favorite Zynga game (which they asked me about at the beginning of the interview). I
had done a good number of product design mock interviews before this round as part of general
recruiting preparation, so this question did not throw me off too much.

Analytics Round

The analytics round was much more up in the air. The questions were not in a format that I had
specifically practiced ahead of time. Zynga as a company is very metrics/data/analytics oriented,
so in this round, my interviewer focused on gauging my ability to define and understand metrics.
Essentially, what metrics would be useful for measuring different aspects of success in games,
and how to unpack certain numbers and trends when collecting data. Compared to the design
interview round, the analytics round of the interview was much more conversational and
consisted of a lot more bouncing ideas off the interviewer. Metrics and numbers are always
more complicated than they seem at the surface level, and my interviewer wanted to make sure
I could identify where data could potentially fail to tell a complete story and could understand
how to fill in the gaps if and when necessary.

An example question I got asked during this round was around a key gaming metric - average
revenue per daily active user (ARPDAU). Given that ARPDAU was down, and our number of
daily active users was stagnant, what could be some reasons behind this declining metric?
Because there are two components to ARPDAU, and we were holding one constant, it was easy
to identify the core issue was around revenue and lifetime value. From there, my interviewer
and I collaborated on how we would launch a feature to combat this issue and evaluated
hypothetical worst and best-case scenarios for the feature. When we “figured out” (aka decided)
that the proposed feature was not successful, my interviewer asked me what iterations of the
feature we could roll out to avoid common issues. Here, I leaned into what I knew about game
design and the monetization of free-to-play games.

In a question series like this, the thing that helped me stay on track with the answer was thinking
of the big picture. It’s easy to get lost in the nitty-gritty when it comes to analyzing a specific
metric, or evaluating success for a feature launch. Thinking of the bigger game at hand in these
scenarios, and understanding the demographic makeup of user groups (and the related
behaviors of these groups) was key in this round. I would not have been nearly as successful in
this round if I didn’t have a good understanding of the mobile free-to-play gaming industry, so
don’t undervalue industry research when preparing for interviews (especially the final round).
Fit Round

My fit interview consisted of behavioral questions but was still very much focused on product
management skills. I was asked about how I knew product management was the path I wanted
to pursue, and I was asked to share specific experiences of mine that helped me build the skills
to work with diverse teams with constantly evolving needs. This round of interviews was
relatively short (only a few questions), so I focused on talking about the depth of the
experiences I had versus the breadth.

Blend Round

The final interview I had on day 1 was a “blend” interview. This meant the questions I got were
really up to the interviewer. As a result, I got a unique mix of questions about how to understand
the target demographic of games I was not familiar with, and how to best measure and gauge
interest with these groups. Because these questions were more out of the box, this interview
had a little more back and forth with the interviewer than some of the other rounds.

Take-Home Assignment Presentation

On day 2 of the final round, I presented my take-home assignment to a panel of three product
managers. I did get some very detailed questions during my presentation, so knowing key
concepts about free-to-play mobile games and the Zynga game I conducted my case study on
was really important.

At the end of each interview round, I had 5-10 minutes to ask the interviewers questions. By the
end of the presentation of my take-home assignment, I had gotten the chance to learn a lot
about product teams at Zynga. One of my favorite things about the interview process with Zynga
was that I got a lot of feedback at every stage of the interview - including after my phone screen
and take-home assignment. Getting quality feedback like that was rare throughout my recruiting
experience, so definitely take advantage of it if you end up interviewing with them.

General Conclusions and Advice

Overall, I enjoyed interviewing with Zynga. By the time I was in the pipeline for Zynga’s RPM
program, I had applied to and gotten rejected from a few other programs. Here are a few of my
main takeaways leading up to my Zynga interviews that I believe helped me be successful.

Know your story: A classic interview question I got was “tell me about yourself.” A lot of people
use this question as an opportunity to list off their past work experiences. I started to be
successful at interviews when I used this question as an opportunity to lean into my untraditional
background and explain why my path to PM made sense for me.

Know the industry and product well: A lot of people spend time leading up to their interview
practicing CIRCLES and generic product design questions. Though both of these skills are very
important, a great way to differentiate yourself in the interview is by having a clear interest in the
company, its product, and the relevant industry. In my experience with Zynga, that included
playing dozens of mobile games for hours on end, researching and learning about free-to-play
mobile games, and chatting with friends about industry trends.

Don’t be afraid to be prepared: I turned up to my interviews with a prepared list of questions

printed out. At the time, I was a little embarrassed by having a list all typed up and ready to go,
but I’m so glad I did. Showing you care enough about the company and the interviewers that
you prepared ahead of time is great and works in your favor.

Remember to be human: A lot of people (myself included for a while) think that interviews are
these high-pressure environments where you have to be perfect and in “impress” mode all the
time. While you want to leave a good impression on your interviewers, remember that the
person on the other side of the table (or zoom call) is also human! Some of the best moments I
have had in interviews were while talking about shared interests and laughing through
work-from-home mishaps.

Don’t be afraid to mess up: Good PMs can acknowledge their mistakes and change course
when necessary. I ended up doing this during my interview a couple of times - when I felt I was
going down the wrong path I paused, took a step back, and redirected as necessary. Previously,
I had interviewed with a company where I felt myself going down the wrong path with an answer
and tried to force it to make sense. I got rejected pretty soon after that round. Don’t force
yourself to be perfect when answering these questions, it doesn’t help anyone.

I am so thankful to be part of this year’s Zynga RPM class, and I hope my experience can help
others trying to break into PM! If you have any more questions about Zynga, I would
recommend checking this google doc written by some former Zynga RPMs. If you’re feeling lost
about how to even start product management recruiting, I wrote this article a couple of months
ago that might be helpful. Good luck to everyone on the PM job hunt!
Duolingo APM Interview Process by Osman Mansur
We reached out to Osman Mansur, a graduate of UC Berkeley and APM at Duolingo about his
interview experience. A few of the remaining articles are done in a similar interview style!
Osman also has contributed a great article on the Aspiring PM blog on the Art of Navigating
Tradeoffs, so be sure to check that out!

1. Do you feel that you did anything special to ensure a first-round interview at Duolingo
(referral, your background, connection to the product, etc.)?

Duolingo appreciates candidates who demonstrate personal interest in the product and mission.
The application features a section where you can explain why you’re interested in the company.
I described how the mission resonated with me both as someone who grew up in a multilingual
home and as someone deeply interested in the intersection of business and social impact.

2. What was your interview process like? (How many rounds, what type of questions, etc.).
The more specific the better here! This is what people are really curious to understand.

This is what my interview process for the APM Internship looked like in Fall 2019

1) Phone screen
2) Take-home assignment (write a spec for a new Duolingo feature)*
3) Video call presentation of take-home assignment*
4) Onsite with 5 portions (Strategy, Design, Product, Analytics, Behavioral)**
a) The Strategy round followed a case interview style with questions related to
market sizing, go-to-market strategy, etc.
b) The Design round involved wireframing a UX flow on a whiteboard, with
questions related to your design choices and thinking
c) The Product round was similar to the classic PM interview question format of
taking an app and working through how to improve it.
d) The Analytics round tested your data thinking skills by asking you to look at a set
of user metrics, interpreting results, and identifying product solutions
e) The Behavioral round was quite on par for the course; questions were about
topics like your experience collaborating with teams, overcoming challenges on
projects, etc.

*The take-home assignment + presentation rounds have since been removed

**During the 2020 recruiting cycle, the onsite portions were split into two separate rounds over
Zoom.

3. Did Duolingo do anything in their interview process that stood out to you as unique, or
different from other companies?
As a very user-focused mobile company, I found that uniquely Duolingo cares a lot about two
things during the PM interview process: 1) user empathy and 2) metrics sense. Being able to
identify and prioritize the learner’s needs is a key trait for all Duolingo PMs. The company’s
product development process is also very oriented around A/B testing, so being comfortable
thinking about data and metrics is essential.

4. Anything else you’d like to add that would help aspiring PMs prepare and stand out in
the interview process!

I would recommend 1) using Duolingo regularly before and during the interview process and 2)
reading through some posts on the company blog. While there won’t be questions that
specifically test your knowledge about Duolingo, understanding the product and how people
think and make decisions at the company will help you get into the mindset of a Duolingo PM
during your interviews.
Uber APM Interview Process by Levi Lian

In fall 2020, during my final year of college, I got into Stanford’s coterminal master's program
(“coterm”) in Computer Science. At that point, I thought I had my future figured out. Besides
conferring my undergrad degree (and navigating a tumultuous pandemic year of schooling), I
would graduate with a master’s degree in 2022. However, something was gnawing at me: what
was the real reason that I wanted to do more school? One part of me knew that I wanted to gain
back some lost time due to the pandemic, especially time on the Stanford campus with friends.
Yet another part prodded me to think deeper.

At the time I had just completed my product management internship at Intuit, tried hard to make
my startup work, but eventually failed, and knew deep down that my early career passion was in
the product. In that sense, waiting for another year of school before going through the intense
recruiting cycle didn’t appeal to me. So I decided to give PM full-time recruiting a try at the end
of August.

There began my APM recruiting cycle, which ended up with me accepting the full-time APM
offer at Uber.

1. Do you feel that you did anything special to ensure a first-round interview at Uber
(referral, your background, connection to the product, etc.)?

Although I agree with the general sentiment that it’s better to have a referral than not, out of the
four companies to which I applied in my recruiting cycle (Uber, Lyft, Coinbase, and Google), I
heard back from two places I cold-applied (Uber and Lyft) and only one of the two places I had a
referral (Coinbase). This is not to say that you shouldn’t try to get a referral; after all, my sample
size is just one and there are so many confounding factors in this causal chain of events (For
example, the sheer size of Google APM applicants means that they have to reject the majority
of those even with referrals). Rather, I hope that you take away something positive from my
slightly unusual experience.

That is if you can’t find a referral and the application deadline is looming, prioritize applying
early. It’s not the end of the world if you don’t have a referral, but it is if your application is
reviewed later than an equally compelling candidate. In APM recruiting, one thing I’ve learned is
that being on the right timeline means 80% of success. Once, I had my final round interview
rescheduled to a week later, and the company decided to pause my final round after they gave
an offer to another candidate who did the final round a week before me.

Acknowledge that unless you network early or already have connections at the company (which
I don’t), it does take a while to find a referral while the clock is ticking. Time is the most valuable
resource in an extremely time-sensitive PM recruiting timeline. Instead of LinkedIn cold emailing
people for connections, I chose to spend my time and energy on fine-tuning my resume and
crafting a story that appeals to each company.
 2. What was your interview process like? (How many rounds, what type of questions,
etc.). The more specific the better here! This is what people are really curious to
understand.

My Uber APM interview process included the following

1) Take-home challenge
2) Zoom Interview 1
3) Zoom Interview 2
4) Onsite superday that spans product, design, technical and behavioral

Here are a few things that worked well for me when prepping for the interviews.

First, I started from the first principles and tried to answer these questions myself. Given the
mission and vision, why did Uber choose to launch Uber Eats? Why did Uber Freight make
sense as a business? Then, I read up on company blog posts, earnings call transcripts, and
media coverage (e.g., Verge), watched recordings of major conferences where senior
leadership spoke, and jotted down notes. The assumption is that large companies sometimes
talk about long-term strategy truthfully in public as a positive signal to analysts and hedge fund
managers alike, so one should be able to extract valuable information and align oneself with the
leadership by researching public information.

With all the notes in hand, I identified industry trends that both align with the core strategy and
can lead to non-intuitive, breakthrough insights. For example, I saw the rise of embedded
finance (e.g., Uber creating a credit card for drivers) and Uber’s doubling down on Eats
business as a new Delivery segment. Although Uber paled back on fintech initiatives seemingly
out of a necessity due to the pandemic, the thesis on supply-side innovation to attract and
maintain the best SMB partners still holds water. This way, I have a couple of talking points
during the interview given my understanding of Uber’s business and potential opportunities.

Finally, I found it super helpful to look up resources and guides written by others. A quick
Google search would link you to a few Medium articles on the Uber APM interview process. In
particular, I want to highlight this guide written by Adi Raju (Uber APM class of 2020) where he
covered the structure of the program in detail along with interview tips.

3. Did Uber do anything in their interview process that stood out to you as unique, or
different from other companies?

Three things about Uber stood out to me.

First, Uber interviewers thoroughly impressed me with thoughtful interview questions and
follow-up. From the very first interview, I was asked questions unlike any I found in interview
prep books by people at least with the title of Senior Product Manager or above. Once I had a
second-round APM interview with a company that sent out a recently graduated APM as the
sole interviewer, so how much Uber cares about its APM program quality from the very
beginning genuinely touched me.

Second, Uber interviews were more interactive and conversational than what I saw in PM mock
interview YouTube channels. Since Uber operates in between the physical and the digital,
go-to-market strategies (e.g., how one would launch a product) are more tangible and important
than at a fully digital company (think a gaming or social media company). How much the
interview simulates the real job of figuring out, say, how to deploy a fleet of autonomous
vehicles, makes me feel excited as a mere interviewee.

Finally, Uber was awesome in terms of communicating each step of the interview before and
after. The whole process took me about two months from submitting the take-home challenge to
getting the offer.

Overall, the PM interview is being increasingly taught as an in-depth consulting case interview
with an almost formulaic methodology. On that front, Uber interview questions are refreshingly
practical and down-to-earth. More often than not, what you’re asked is what the interviewer has
dealt with or tackled at some point in their Uber career.

4. Anything else you’d like to add that would help aspiring PMs prepare and stand
out in the interview process!

My advice is to start from Uber’s mission and vision, the entire product suite, and read up on
recent product launches (usually posted on the official website). If you want to do extra
homework, look at Uber’s earnings call transcripts or any major conferences that senior
leadership attends to understand the strategy and how Uber hopes to realize it.

Be prepared to connect dots with your prior design / PM / technical work when discussing your
passion for Uber. The behavioral aspect of the interview cannot be ignored for Uber. Company
values mean nothing if there are no specific practices that reflect those values.

Each company is unique so be sure to understand what makes Uber PMs special (and
respectable within the tech industry). There are tons of tweets and blog posts on good vs great
PMs at work. Knowing the difference between a strong and an outstanding PM candidate would
increase the slim odds of getting that offer.

I also offer PM interview prep (and MBA application consulting) on the side. Please reach out
and I’d love to help figure out a package that works for you.
Twitter APM Interview Process by Lily Li

1. Do you feel that you did anything special to ensure a first-round interview at
Twitter (referral, your background, connection to the product, etc.)?

I was a Product Management Intern at Twitter (Summer 2020). After interning at Twitter, I
wanted to come back as an APM full-time. Here, I will speak about how I got my first round
interview for Twitter’s PM internship.

Context: When I was applying to Twitter’s internship, I did have a referral; however, many of my
peers who got the PM internships and APM full-time positions at Twitter did not have referrals!
Different from most tech companies, Twitter seems to be a place where a referral is not
required. I have talked to APMs in my class and the previous class -- the majority of the APMs
applied without referrals at Twitter.

Here are the steps that I took to put my best foot forward to get a first-round interview:
- I reflected on why I wanted to join Twitter. There’s a section where we could write a short
paragraph to the hiring manager and the recruiting team (like a cover letter) in the
application. I put my story there.
- Before sending my application, I polished my resume and tailored it to the PM internship
position at Twitter.
- I have been a Twitter user. I played around with the Twitter app to think about what
features would I bring to the team, as well as some product strategies that I want to
suggest even before I receive the first round of interviews.
- I reached out to Tweeps (employees at Twitter) to learn more about the company
beforehand. It’s not about referrals, but more to genuinely learn about the culture,
values, product, and teams at Twitter.

My background:
- I studied Data Science and minored in Education at UC Berkeley.
- I came from a PM background. Before becoming a product management intern at
Twitter, I had 3 PM internships (NETGEAR, Kohl’s, and a tech real estate company) and
2 marketing internships (a virtual reality start-up and an NGO).
- Very active on-campus at different student organizations. Big on student leadership.

2. What was your interview process like? (How many rounds, what type of questions,
etc.).

APM full-time interviews:

- Stage 1: First round of interviews: 2 back-to-back product interviews
- Product design interview with product manager * 1
 - Product analytics with product manager * 1
- Stage 2: APM writing assignment (product proposal) before the final round of interviews
- Stage 3: Final round of interviews:
- Product design interview with product manager * 1
- Product analytics interview with product manager * 1
- Behavioral / Group interview * 1
- Technical round with an engineering manager * 1 (high-level systematic design,
not coding)

3. Did Twitter do anything in their interview process that stood out to you as unique,
or different from other companies?

Three things that Twitter have stood out for me:

- First, I feel that I was being treated as a human being during the interview process. At
some other companies, I have experienced being asked to jump right into the product
design interview process, without even being able to introduce my name. During my
interview process at Twitter, the process is intellectually challenging but also caring,
authentic, and genuine.
- Second, I appreciate Twitter’s quick turnaround time. My PM internship offer’s
turnaround time was quick once the interview process started. I heard from my APM
full-time peers that they received congratulations calls and offers within a week after their
final round of interviews. Once the interview process starts, you should hear about the
result within 3 weeks (from the first round to the APM offer).
- Third, I think the interview process is comprehensive. The interview process consists of
product design (2 interviews), product analytics (2 interviews), behavioral/group interview
(1 interview), writing assignment (1 assignment), and a high-level technical round (1
interview). I think my interview experiences at Twitter for both the PM internship
interviews and the APM full-time final rounds of interviews were really fun and positive.
My interviewers were great listeners, could bounce ideas with me during the interview
process, and they challenged me to let me learn and grow even during the interview
process.

4. Anything else you’d like to add that would help aspiring PMs prepare and stand
out in the interview process!

- Mock interviews helped me a lot. Simulating the APM interview environment made me
become more confident and allowed the product thinking mindset to come naturally.
- As a PM intern who has worked at Twitter in Summer 2020, I wholeheartedly
recommend this company. Very diverse team, dedicated and talented manager and
mentors, large scopes that you could own as a PM, friendly and energetic working
environment, fantastic company culture, and challenging + interesting user problems.
 Here’s a podcast that you can listen to learn more about my PM internship experience at
Twitter: https://open.spotify.com/episode/1kpjgrCIfbgVS7bnjKBGy9
- “Tech Twitter” is a great resource! Tech twitter refers to tweets on Twitter that are either
written by people who work in tech, or communities on Twitter that help and support one
another. Many product leaders like sharing their thoughts on Twitter, and I learned a lot
about product management & tech by using Twitter and following those thought leaders.
If you want to reach out to Tweeps (Twitter employees), Twitter DM is an amazing
channel -- you may have more success to grab an informational chat with a Tweep than
reaching out on LinkedIn. I wished that I knew about it earlier!

Acing the Interview

Books and Resources

We’ve listed some books that are must-reads for PM interviews and others that are
recommended, interesting reads.

Books: Must Reads

● Cracking the Product Management Interview (FREE PDF)
○ You MUST read this book, honestly even before submitting applications. This is
the most comprehensive book on what being a PM means, what the interviews
are like, and how to be successful. It is a useful read even for current PMs!
● Inspired: How to Create Tech Products Customers Love (FREE PDF)
○ This book is extremely comprehensive about being a product manager and how
to ship great products - highly recommend it.
● Decode and Conquer
○ Aveneel’s favorite - presents a lot of useful frameworks to answer different types
of interview questions (product design/sense, execution), and gives sample
questions and answers. A very useful book to go through right before an
interview to get yourself in the right mindset!
● The Product Manager Interview
○ This book mainly focuses on interview prep with Q&A. We recommend taking
some of these questions and doing mock interviews with friends first before
reading the answers!

Books: Recommended Reads

● Swipe to Unlock
○ Good for understanding business strategy in technology companies and an
entertaining read - more beginning-friendly.
● How to Build a Billion Dollar App
○ This is Jake’s favorite. It’s not focused on interviewing or recruiting, but more of a
high-level view of building a successful, consumer-facing application (in this case
the example is a former Uber competitor, Hailo) and scaling it.
 ● Hooked: How to Build Habit-Forming Products (FREE PDF)
○ Claudia’s favorite - goes in-depth on how successful products retain their
customers, especially application-based products and games.
● Zero to One: Notes on Startups
○ Peter Thiel explains how we can create new companies and products in this
book. Super useful for an aspiring entrepreneur and a product manager learning
about product innovation.
● The Lean Startup (FREE PDF)
○ A very useful book for anyone interested in PM or entrepreneurship.
● Case In Point
○ This book is a must-read for consulting recruiting, but can still be helpful for PM
because it emphasizes thinking analytically and giving structured answers.
Capital One’s PM interview includes a business case, so this book would prepare
you for that.

Articles: Must Reads

● How to Land a PM Role in 21 Days
● Making it Happen: A 6 Month Plan to Landing a PM Role
● Choosing Your North Star Metric

Articles: Recommended Reads

● Cracking the Google Associate Product Management Interview

How to Answer Product Execution Questions

Product execution questions often fall into these categories:
● Evaluate why a metric has dropped and the process of investigating its root cause
● Evaluating the success of a new or existing feature
● Evaluating trade-offs between building certain features

While we aren’t going to include a sample answer for a product execution question here, please
check out some of the videos linked in this article on our favorite interview videos for some great
examples.

Evaluating Metric Changes

● Sample Answer Structure

○ Define the metric and restate the goal of the product or feature
○ Get context with clarifying questions
■ Is this change specific to a geographical region?
■ Is this a gradual or sudden change?
■ Are we seeing this change across iOS, Android, web?
■ Was there a holiday or natural disaster recently?
■ Has there been any relevant news coverage of the company recently?
 ○ Take a second to organize your thoughts/hypotheses and come up with a
framework.
○ Framework:
■ Users and user journey for this metric
■ Hypothesize causes of the problem
■ Identify useful data that could help solve the problem
■ Name ways to resolve or mitigate the problem
Prioritization Questions

You may be asked how you would prioritize projects with limited resources. These questions
normally won’t take the whole interview time compared to Product Design and Product
Execution. For these questions, it is good to approach them with a framework. There are many
you can use, but here are examples:

Value vs. Effort

Value: revenue, user benefit, impact/reach, alignment with company goals, ROI, the likelihood of
success
Effort: cost, time, risk, complexity, engineers/designers needed

Other Frameworks: Impact X Confidence X Ease // Feasibility X Usability X Validity

Question Bank
● You are the PM for UberEats; cancellations on orders are up 15%. What do you do?
● How would you measure the success of YouTube stories?
● How would you measure the success of Coinbase Earn?
● You are the PM for Zynga; ARPDAU (average revenue per daily active user) is down,
and your user count has been stagnant over the past week. What could be responsible
for this change?
● You are the PM for Lyft, and ride cancellations are up by 10% over the past week.
Investigate this increase in cancellations and what could be causing it.

How to Answer Product Design/Sense Questions

Product Sense questions usually ask you to evaluate a current product and improve it or
design a new future for a specific use case.

Product Design questions often come in the form: Design X for Y.

These questions are a great exercise in applying structured thinking to a problem. Interviewers
are typically looking to see a clear, logical thought process in understanding what makes great
products and the ability to design user-focused products -- and a little creativity never hurts
either! Using frameworks is key to having well-structured, impressive answers.

Product Sense Example:

 ● What is your favorite product and why? How would you improve it?
○ This question will come up in some shape or form from nearly every company
you will interview with. A good strategy is to come up with three software
products you know well, and potentially one hardware/physical product. In the
past, I have picked Strava because I use it nearly every day and it also shows
that I have a unique interest in triathlons, which I thought was something that
added some depth to my persona. I have also used Quora since I used to often
write on the platform and so got to mention that hobby while discussing a product
I was very familiar with.
■ This is a loose framework you can use:
● The product’s value proposition/purpose
● What’s unique about it?
● Who are its competitors - how does it stand out?
● What is its business model?
● Who are the users?
● What is the north star metric for the product?

Question Bank
● You are a PM at Zillow. How would you design a new feature to increase app usage by
first-time homebuyers?
● Design a tool or application to help people buy cheese (this is a real question that was
asked at Facebook).
● You are the PM for Shopify, a platform aimed at enabling small businesses to market
themselves, sell products, and collect payment. What tool do you build next to help our
customers (merchants) succeed?
● Why do you think Zillow has two apps: Zillow (for buying homes and condos), and Zillow
Rentals? This is a less traditional design question, but a good thought exercise
nonetheless.
● How would you go about designing a productivity tool for college students?
● How would you improve the DMV experience?

Here’s a shortened version of what an answer to a product sense question could look like:

You are a PM at Zillow. How would you design a new feature to increase app usage by
first-time homebuyers?

My general framework for going about a product design question like this would be:
1. Ask clarifying questions, and validate assumptions
2. Outline my process for discovering a solution (and signpost along the way)
3. Brainstorm pain points of the customer segment and prioritize them
4. Brainstorm solutions to pain points
 5. Prioritize solutions (take into account how well they are currently solved by the product,
how big of a problem they are solving, how much effort the solution would take)
6. Explain tradeoffs and risks of solutions
7. Propose feature and method of measuring success by choosing a north star metric

After outlining my process for going about discovering a solution, I would dive into
understanding the customer segment. Looking at the target customer segment, first-time
homebuyers are likely younger than the typical homeowner, perhaps in their late 20s and 30s.
Most are probably couples and may have children. They are likely at least a few years into their
career, although this may vary depending on the cost of living in different parts of the U.S. I
would bet that they experience a few main pain points, which needs are met by Zillow’s current
app in several ways:

● They wonder how much they actually can afford (this element is stressful), and want to
have clarity from a financial perspective → the current app says what the average
monthly payment should be with a 20% down payment. This is super helpful, and could
potentially be expanded to cover those that can’t afford a 20% down payment (a portion
of the first-time homebuyer market)
● Millennials don’t seem to be as excited about buying a house because of the high cost of
mortgage payment and lack of flexibility (as opposed to working remotely and moving
every few months). → Zillow is largely focused on people researching the possibility of
buying and those already decided on buying a home. Perhaps Zillow can do more to
educate millennials about the value of buying a home.
● In today’s competitive market, it can be easy to get discouraged after being outbid and
not getting the house you want → Zillow posts a “Zestimate,” estimating what the house
is worth, regardless of the listing price. However, nowadays in some hot markets houses
are going for a lot over the Zestimate. I also know that every offer on a home is a little
different, so maybe some things could be tweaked about someone’s application to make
it more likely to be accepted. There could be work to be done here. Zillow also currently
connects you with local real estate agents who know the area well, which is a plus for
customers looking for someone with local knowledge.
● It can be tough to find a home within the right price range, area, etc. within the first week
that it is listed without spending a ton of time on it→ Zillow does a pretty good job of
letting you filter based on basic characteristics here and does send emails and push
notifications alerting you of new homes that are listed

Now, I can prioritize building a solution to the above pain points based off of:
1. How pressing the problem is
2. How well Zillow currently addresses the problem
3. How much effort it takes to build the desired solution

Remember to keep the overall goal of increasing usage by first-time homebuyers in mind. The
first two problems deal with helping first-time homebuyers understand if buying is feasible and
makes financial sense, which are early activities in the overall user journey of buying a home
(you can also think about this as the activation step in the AARM funnel). I’d end up choosing
the second problem above to focus on (helping millennials see the merit of buying a home)
because it helps us add more customers at the early end of the funnel, and is a problem that
Zillow hasn’t yet applied a solution to.

Next, I’d brainstorm a few solutions to the problem, and similarly prioritize them, making sure to
mention tradeoffs to each. Finally, I’d conclude with my proposed feature, how it would address
the overall goal, and how to measure success by picking a north star metric.

How to Answer Behavioral Questions

These questions are the low-hanging fruit, so don’t skip preparation for them. You will get asked
these, and there is no excuse for not having a well-thought-out answer.
1. Why this company?
a. Peruse the company’s website and pay close attention to its values, mission
statement, culture, and product portfolio. If anything sticks out to you and
resonates with your values or experiences, then it is a good point to mention if
asked this question. Always give anecdotes - don’t only say “I love how your
value is continuous learning” - give an example of how you have exemplified that
value before. Another recommendation is to coffee chat with people who work at
the company - either people you know who have worked there or people you
have mutual connections with on LinkedIn. They can give you more specifics
about what it’s like to work there and what’s unique about the company.
2. Why are you interested in product management? What would make you a good
PM?
a. We would stray away from answers that are too general here such as “I like
working in a team,” “I would love to build things that people use,” etc. You want to
share something memorable and specific. Especially if you come from a
non-technical background (studied political science, business, architecture,
music, English, etc.), nailing your story here is key! Here’s a good example
answer: “I came to UC Berkeley intent on becoming a doctor, but eventually felt I
needed to explore other options before committing to such a long path of
education. I was glad that I took that time to explore! I soon joined a consulting
club and found that I excelled at condensing user feedback into high-level
recommendations for additional features and marketing strategies. While working
on a project for Venmo, I discovered something that surprised me through a
series of focus groups -- college students highly valued the aesthetic nature and
color of the card, even more so than its other features! This interest in
understanding and empathizing with customers has led me to want to work in
product management, driving forward a product with a clear focus on user needs
and filling those.
3. Tell me about a time you led a team.
4. Tell me about a time you failed.
5. Tell me about a time you dealt with conflicting stakeholder priorities.
 6. How would you prioritize resources when you have two important things to do but
can’t do them both? (Asked by both Google and Salesforce)
7. What aspects of Product Management do you find the most exciting?

Asking Your Interviewer The Right Questions

1. What’s the most challenging part of being a PM here?

2. What’s your favorite part about working here?
3. What is unique about your company’s culture?
4. Where do you see the company going in five years?
5. What has been the most challenging product/launch you worked on?
6. What product are you currently working on?
7. Could you compare and contrast your experience at this company to your
previous company?
8. Is your company product-led, engineering-led, or somewhere in the middle?

That’s it! Best of luck with recruiting - if you want to see any
specific content or have questions please reach out to us on our
LinkedIn profiles below.

Aveneel | Claudia | Jake