My Journey to the Facebook Product Manager Offer
After 4 months of preparation, with 40+ mock interviews, countless solo practice sessions, and two rounds of interviews, I finally got my Facebook product manager offer.
It was a long journey with ups and downs. At some point my self doubt was so strong that I almost gave up. I am glad that I didn’t. In retrospect, there are many lessons learned along the way. I would like to document them for my own self reflection. I also hope that some of my lessons will be helpful to those of us who are still struggling with the Facebook interviews.
Facebook PM Interview — The Basics
Candidates typically go through two rounds of interviews before they can get the product manager offer from Facebook. It is not unusual for Facebook to schedule one more interview for you. It happens when they think you may qualify but they just haven’t got enough signals from the previous interviews.
In the first round, there will be at least one product sense interview and one execution interview. In the second round, there will be at least one product sense interview, one execution interview, and one leadership & drive interview (which is Facebook’s version of behavioral interview).
It appears that Facebook likes to insert one more interview in each round nowadays. I myself was given two execution interviews in the first round, and two leadership & drive interviews in the second round. I also know people who got two product sense interviews for the final round. Someone told me that the additional interview is for training purposes only, so it may not count. I am not sure if that’s true. Even if it’s true, it’s hard to tell which one is for training purposes only, so we should still treat all interviews as important, and give them our best shot.
The Facebook recruiters and interviewers like to remind us that the questions are inherently ambiguous. There is no right answer. What they want to understand is how we think. I believe what they say is true. I was not satisfied with my answer to the product sense question in the final round, but it was still a structured answer, which covered all the areas that Facebook wanted us to cover. I definitely did not provide any ideas that were out-of-the-box, but I guess the interviewer thought my thought process was still based on sound logic, and eventually he let me get away with it. So no need to over think and sweat yourself trying to come up with genius answers. Focus on the logic.
Based on what I learned from the Facebook recruiters, here are the signals they look for in your answer to each type of questions:
- Product rationale — Why is this product important? How does it tie to Facebook’s mission?
- Measure of impact — What metrics should we consider?
- Goals — What is the most important metric (the North Star)?
- Trade offs — What are the risks? What metrics should we consider to make sure we understand the risks?
- Mission & motivation — Why build this product?
- Target audience — Who will use the product? Who are the primary users?
- Problem identifications — What are the pain points for the primary user segment? Which pain point(s) should we prioritize?
- Solid and specific solution — Brainstorm a few ideas to address the prioritized pain point(s), and come up with the MVP.
Leadership & Drive
- Resilience & resourcefulness
- Self awareness
Don’t be surprised if the interviewer rush us through the interview. Sometimes it’s a good sign. They may have already got enough signals from our answer. I was cut short in almost all my answers in one of my leadership & drive interviews. In my first round execution interview, the interviewer also stopped me in the middle of my answer, because she wanted to ask a follow up question. So don’t panic. Just go with them.
There is one exception though. If you haven’t fully covered the key components in your framework and they stop you, you should stick to your gun. In one of her product sense interviews, a friend of mine was forced to go into solutions before she even examined the pain points of the target user segment. In retrospect, she realized the interviewer was trying to test how she handles pressure. If given another chance, she said, she would definitely push back on the interviewer’s demand.
Facebook PM Interview — The Deep Dive
In this section I will explain in details the type of questions you will get asked in Facebook interviews. Some are typical questions that appear again and again (sometimes with some variations).
There are four types of execution questions.
The First Type: Metrics
Two examples of the metrics questions are:
1) How do you define the high level goal for Instagram Stories?
2) How do you measure success for Facebook Events?
In my opinion, Metric questions are the easiest among all Facebook interview questions. I highly recommend you follow the framework from a Facebook PM called Dianna Yau -understand the product/feature, examine user segments, come up with metrics that measure value for each user segment, take the intersection as the North Star metric, break down the North Star into factors that can impact the North Star metric, and finally, define downstream metrics and counter metrics.
Dianna has produced many YouTube videos that talk about how to answer Facebook PM interview questions. I will include the link to her YouTube channel in the Resources I’ve Used section of this document. You should go over her videos. For me, they are the best free resource I can find for Facebook interview preparation.
Because metric questions are so straightforward, and because (I suspect) Facebook knows that a lot of their interview questions are already leaked, the interviewer will very likely throw in a follow-up question in the middle of the metrics interview.
Follow-up questions are usually hard to predict, but they usually come in the form of a debugging question, a trade off question, or an “X goes up and Y goes down” question (which is essentially a combination of debugging and trade off questions). You should be in a good shape if you understand the key to tackle debugging and trade off questions.
For examples of the follow-up questions, read on.
The Second Type: Debugging
Examples of the debugging questions include:
1) What would you do if you see the number of people who RSVP for events declined in the last 2 weeks? (This could be a follow-up question to the metric question “How do you measure success for Facebook Events”.)
2) The number of reactions left on News Feed posts has dropped 10% week-over-week. If you are the PM for this product, what would you do?
Many Facebook preparation videos on YouTube recommend we follow a scope-narrowing process by going through an exhaustive list to get to the root cause: Is the issue drastic or gradual? If gradual, how long have we been seeing it? Does it impact a specific user segment? Does it impact a certain Geo location? Does the issue only occur on a specific platform, e.g. the iPhone app? …
While this is a logical way to tackle the problem, the process won’t help you stand out. The interviewer is expecting insights from you, insights about what drive the metrics. You need to demonstrate your ability to formulate hypotheses before you dive deep into the scope-narrowing process.
You should think about what factors impact the metrics and come up with hypotheses. In the example question “What would you do if you see the number of people who RSVP for events declined in the last two weeks”, the metric that is having issue is the number of people who RSVP for events. Factors that impact this metric include:
On the supply side — number of events available, and number of event creators.
On the demand side — active user count on the Events page, and click through rate of those users on the events.
Then your hypotheses could be:
a) Fewer events are created than before, so fewer users RSVP.
b) Fewer people are creating events than before, so there is a drop in number of events, and as a result, there is a drop in number of users who RSVP.
c) Fewer users are visiting the Events page than before, so fewer users RSVP.
d) Fewer users are clicking on the events as before, so fewer users RSVP.
Three or four hypotheses should be good enough for a 45-minute interview. Then we can verify the hypotheses with the help of the interviewer, and move on to the scope-narrowing exercises. For example, if the interviewer tells us we do see the number of events dropped, then we can ask whether we see a bigger drop in offline events or online events. If the interviewer says that the drop was happening for offline events only, then you can hypothesize that maybe it’s because of the pandemic — people stop creating offline events.
Debugging questions are difficult to practice, as there are too many possibilities for the root cause, but you should at least get to the stage where you can come up with a list of hypotheses that may lead you to the root cause.
The Third Type: Trade Off
Example questions are:
1) Should we make Instagram Stories stay for 48 hours instead of 24 hours?
2) Should we put an ad or a People You May Know widget in News Feed? (This is actually a frequently asked question, and it has many variations , such as “Should we put a Live or a People You May Know widget in News Feed”. )
If you have practiced Facebook trade off questions for long enough, you probably know that the answer is “It depends”. Usually you need to run A/B test before you can come up with the answer, but before you jump into the details of the A/B test, you should identify the metric that you need to optimize for, and then examine the impact of different options on that metric. This will tell you what you need to measure in the A/B test, and this is the key to answering the trade off questions.
In the example question “Should we make Instagram Stories stay for 48 hours instead of 24 hours”, we probably want to optimize some metric that is related to engagement on stories, such as total amount of watch time, number of engagements, etc.
Let’s pick number of engagements for the purpose of this exercise. We can then call out that number of engagements are impacted by factors on the supply side and factors on the demand side.
On the supply side, the more stories created, the bigger the engagement number will be. When you make stories stay for 48 hours, would you see more or fewer stories created?
My guess is: we will see fewer stories created.
Because Instagram offers the Stories feature as a no-pressure way for users to create content. By making the stories appear only for 24 hours, Instagram removes (some of) the concerns that users might have when creating content — Is my content good enough? Will I be judged by my content? etc. Now if we increase the time to 48 hours, we are essentially adding (some of) the pressure back on those users. Some of them may choose to quit creating stories. So the number of stories will likely go down. As a result, the total number of engagement may go down.
On the demand side, the longer the stories live, the more time the viewers will have to engage with the stories. As a result, the total number of engagement will likely go up.
With one factor that may lead to a higher engagement, and another that may lead to a lower engagement, we will then need an A/B test to find out whether the net impact on engagement is positive or negative.
Another tip: you should always try to come up with one more variation for the A/B test. In this case, that variation will be: instead of letting Instagram decide whether it should be 48 hours or 24 hours, we can give the control to the story creators. That way we might mitigate the negative impact on the number of stories.
The Fourth Type: Metric X goes up, but metric Y goes down
Example questions are :
1) What would you do if you see the engagement goes up for Instagram Stories but goes down for the normal feed of Instagram? (This could be a follow-up question to the metric question “Define a high-level goal for Instagram Stories”.)
2) Suppose you launched a new matching algorithm on Facebook Dating to a small A/B test. The average number of messages sent per user decreased, but the number of people that the average user messaged actually increased. What do you think might be happening? Is this feature worth shipping to everyone?
For this type of questions, we usually need to go up one level to find a higher-level metric that matters. For the example question 1, since both Stories and the normal feed are sub-products of a higher level product, which is Instagram, we should mention that the most important metric is the Instagram-level metric, such as time on site, session count, or active user count. For the purpose of this exercise, let’s just pick time on site, i.e., total amount of time of all the users spend on Instagram in a given period, say, a week. Our first action should be to examine that metric and make sure nothing negative occurs there. If the Instagram-level metric is not suffering, then we might be OK, for now.
Regardless of whether the Instagram-level metric is OK or not, we still need to examine the metric that’s dropping, in this case, the engagement on normal feed. Here we can think about factors that impact the engagement on the normal feed. On the supply side, it could be the amount of content for the normal feed is dropping, which might be a result of a decline in the number of normal feed creators. On the demand side, it could be the active user count on the Instagram homepage is dropping, although this is less likely, because we still see the engagement going up on Stories. So we should prioritize the hypothesis on the supply side and dig deeper there.
Assume the interviewer tells us that there is actually a drop in the number of normal feed creators. Then we can ask: Is it because the normal feed creators are changing into Stories creators (since they see Stories are being featured on the prime location)? We can look into the data and easily verify this. If it’s really the case, then that would be a big problem for Instagram. A story only lives for 24 hours while a post on the normal feed lives forever, so the net impact on the amount of content is negative, which may lead to fewer engagements down the road.
What I mentioned above (and throughout this article) are mostly simplified approaches to solving the interview questions. Hopefully you get the idea. To summarize, in the Execution interview, we are expected to have a broader perspective and come up with insights on what’s moving the needle.
There are two types of product sense questions.
First Type: Product Design
Example questions are:
1) Design a travel experience for Facebook.
2) Design a digital vaccination passport.
3) Design a calendar app for Facebook.
4) Design an independent map app for Meta.
The biggest challenge of product sense questions is they are usually too ambiguous. We need to figure out a way to narrow them down to a manageable scope. To do that, I usually focus on a specific use case and/or a specific user segment, and try to leverage the strengths of Facebook.
For example, for the question “Design a calendar app for Facebook”, we can think of the calendar as a scheduling tool and convert the question into “design a scheduling app for small- and medium-sized businesses” . For the question “Design an independent map app for Meta”, we can think about Facebook’s strengths in social and user insights, and convert the question into “Design a social map app for Meta”.
The signals listed in the Facebook PM Interview — The Basics section should give us some ideas of a high-level framework. A few suggestions on some of the key components in the framework -
A lot of the features/products discussed in the Facebook product design questions are two- or multi-sided marketplaces, so it is common to use a supply vs. demand framework to segment the users, e.g. content creator vs. content consumer for Facebook posts, Live, and videos; admins vs. members for Facebook Groups; event organizers vs. participants for Facebook Events; doctors or medical providers vs. patients for a feature to help people find doctors; tutors vs. students for a feature to help people find tutors, etc.
Sometimes you may need to add in a third group of user, the facilitators, such as insurance companies for a feature to help users find doctors, parents for a feature related to K-12 education, and care takers for a feature related to disabled people.
Other segmentation criteria could be new users vs. existing users, power users vs. casual users, frequent user vs. infrequent users, professionals vs. amateurs, business users vs. personal users, education users vs. entertainment users, users who use the product while driving vs. users who use the product at home (e.g. for podcasts), etc.
Usually we should prioritize one segment over the others, using the following criteria:
Size — How big is the user segment?
Under-served — Are there existing solution for this group of users? Who cares the most? Who needs the product more urgently?
Frequency — How frequently does the user segment use the product?
Spend — How much are the users willing to spend?
I find the first two criteria good enough for most questions. Occasionally I will add other criteria in the prioritization exercise.
Once we pick the primary user segment, we will likely need to segment it further, because it may consist of different type of users with different needs. This is what I call “two-level segmentation”. For example, assume you’ve decided to focus on travelers for the question “Design a travel experience for Facebook”, there are different type of travelers: business travelers vs. leisure travelers, families traveling with kids vs. young people traveling with friends, travel junkies vs. inexperienced travelers, etc. and their needs are totally different. Compared to young people traveling with friends, families with kids will be more picky on accommodation. They need houses with more bedrooms, or hotel rooms with more beds.
To come up with the target segment, I will do one or both of the following:
1. Go at least 1 level deeper, then pick a sub-segments.
2. Use at least two dimension to segment the target user group further, then pick one of the sub-segments, or choose the intersection of the sub-segments.
Take the traveler group as an example. After the exercises mentioned above, the target segment I pick is young and inexperienced travelers who travel for leisure with friends.
Once we identify the target user segment, the next step is to examine their pain points. I usually think about the pain points along the user journey.
For example, assume you are asked to design a smart parking garage, and you’ve decided to pick drivers who plan to park in the downtown parking garages as the target segment, what pain points do they have?
First, think about their user journey:
Step 1. Find a garage.
Step 2. Find a parking spot.
Step 3. Park.
Step 4. Pay. For some garage, this happens when the driver leaves. Others require the driver to pre-pay.
Step 5. Come back, find the car and leave.
Then, list the pain points for each step.
Step 1. Find a garage.
a. I don’t know which garage has parking spots available.
b. I don’t know which garage is cheaper.
Step 2. Find a parking spot.
a. I can’t find a parking spot, either because there is none available, or because I just cannot find it even if there are spots available.
b. I think some spots may be available soon, but I just don’t know which are, and don’t know how long I should wait.
Step 3. Park.
a. There is a risk of the car being broken into.
Step 4. Pay.
a. I need to walk a long way to the pay station from where I park my car.
b. I have to pay in coins or cash, but I only have credit cards with me.
c. I need to prepay for a certain amount of time, but I am not sure how long I need to park my car for, and I may over pay or under pay. If I under pay, I will need to come back to add more money, which is very inconvenient for me.
d. Some garages require me to insert a card (or a piece of paper) into the payment machine before I can pay, but sometimes I will lose the card and cannot pay.
Step 5. Come back, find the car and leave.
a. I forget where I parked my car, and it takes a long time to find it.
I’ve seen other people come up with pain points by using other framework, such as the popular AAARRR (Awareness, Acquisition, Activation, Retention, Revenue, Referral). Personally I prefer a simpler version of the framework: Awareness, Motivation, Concerns, and Efforts. There’s no perfect framework. Just pick the one you feel the most comfortable with.
After we list the pain points, we should prioritize them. The prioritization criteria I use are:
Size — How many users are experiencing the pain?
Level of pain — How painful do the users feel?
Existing solution — Do good solutions exist?
From my experience, usually the first two criteria are good enough, but occasionally I will use the third.
I was once told that I should prioritize only one pain point, otherwise the interviewer may think I am unsure. Personally I find it very challenging to come up with enough solution ideas if I focus only on one pain point. I prioritized more than one pain points in my interviews. Looks like my interviewers thought it was OK.
If your pain points are specific enough, usually the solutions will present themselves.
When brainstorming ideas, I like to think about the following and see if there is anything I can leverage.
New content type/interaction: audio, video, live, and short-form video.
New way to get data: face recognition, QR scan, OCR, UGC, and crowd-sourcing.
New technology: AI, AR/VR, speech to text, machine translation, personalization, and autonomous driving.
Sometimes I borrow the best practice from other apps. For example, if the pain point is about matching efficiency, I often throw in the idea of Tinder for X. It can be used for the following questions -
Design a feature to help people find roommates.
How would you build a language learning product for Facebook?
Build a product that makes it easier for people to connect with friends and family members with the same interests.
In the case of finding roommates, people who are looking for roommates can fill in their requirements. Then Facebook recommends potential matches based on users’ requirements. Users can then tell the system whether they like the potential match or not by a simple swipe. When a match is found, Facebook will notify both users, who can then move on to later steps in the process.
After we come up with the list of product ideas, we need to prioritize them and decide which will be included in the MVP. I usually use two criteria: the impact on the goal, and the implementation effort. Sometimes I will also evaluate the ideas based on how unique they are.
We should not stop there. The Product Alliance course recommends we talk about how we go to market, and I was actually asked how I would go to market in my first round product sense interview. This may include consideration on how we enable discovery of the feature, how we build the viral loop, etc. For example, for the question “Design a travel experience for Facebook”, I have picked my target segment as young and inexperienced travelers who travel for leisure with friends, so the go-to-market strategy could be promoting the feature to college students right before spring break.
Example questions are:
1)Pitch a few ideas to improve WhatsApp?
2) What’s your least favorite product or feature by Meta? How would you improve it?
3) How would you improve Instagram Reels to differentiate it from TikTok?
I don’t have a very good framework for Product Improvement questions, but I try to keep the following in mind when answering those questions.
Make sure I understand how the product works, and align my understanding with the interviewer.
Make sure I understand the North Star metric for the product. Most likely this is the metric I need to optimize for, unless the interviewer tells me otherwise. Obviously, if I can come up with the right North Start metric, I’ve already known the users of the product and how they derive value from the product.
Identify improvement opportunities along the following dimensions –
- User segments
For example, in some part of the world females are not supposed to show their faces in front of a camera. So they might be the segment, for which there are improvement areas when it comes to the video chat feature of the Messenger app. Maybe we can enable realistic avatars there?
2. Use cases
For example, Google Maps might be improved for the use case of finding restaurants, since many users are searching for restaurants on Yelp, 4Square or DoorDash instead of Google Maps.
3. Certain steps in the user journey
For example, for the event organizers, the step to get more RSVPs may be an improvement area. For grocery shoppers, the step of payment may have improvement opportunities as they sometimes need to wait in a long line.
My Preparation Timeline
I had a phone screen with the recruiter. It was a 30 minute call, during which he asked about my past experiences. No tricky questions. I think it would be extremely hard to fail the phone screen. Unless you have serious red flags, they will let you pass.
I then set up the first round for October, giving myself a month to prepare. During the month, I mainly used the site Product Management Exercises for Facebook interview questions and answers, and practiced on my own. I will list the resources I used for preparation, as well as my opinions of them, in the Resources I’ve Used section below for your reference.
I had my first round and passed. Right before my first round execution interviews, I discovered Dianna Yau’s YouTube videos about Facebook PM Interview tactics. Those videos really helped me a lot.
After I set up my second round for December, I found another great resource Product Alliance, and subscribed to it. They offered insights into Facebook product strategy, tips and examples about Facebook interviews, and a regularly updated list of Facebook interview questions. All of a sudden I had a lot of content to review. So I pushed my second round (twice, and yes, they allow that) to January just to give myself more time.
November 2021 — January 2021
I started to time myself in my solo practices, making sure I get all the key points in my answer within 20 minutes. For questions that I was not so sure, I googled to find answers/thoughts from other people. I also started mock interviews with partners I found from the Slack groups of Product School and Lewis Lin. Eventually I finished about 40+ mock interviews before my second round.
My second round was in late January. I did well for the execution interview and the two leadership & drive interviews that they set up for me, but I was not satisfied with my performance in the product sense interview. After the interview I thought the best I could hope for would be a 2nd chance for the product sense interview. The result, however, was a pass, so I guess maybe the interviewer was still able to get enough signals from my answer.
Resources I’ve Used
Best Free Resource
So far she has published nearly 20 videos that talks about how to answer different type of Facebook interview questions with examples. I would highly recommend you watch all those videos. I find her approach intuitive. You should try her frameworks in your practice. If you are comfortable with her approach, by all means, use it in your interview. I could not have passed the first round execution interviews without watching her videos. Thank you so much, Dianna!
The only downside — the channel is not frequently updated, but I guess I cannot ask for too much.
Best Paid Resource
As mentioned, they offer a lot of content, actually more than I could consume in two months. There are a few things I like about them.
First, they have several videos about Facebook product strategy, and I find them really insightful. For me, who haven’t been a heavy user of Facebook products, those videos offer a framework to grasp the essence of Facebook’s products. I was able to weave some of those insights into my answer to the Facebook interview questions, which was an added benefit.
Second, they also have videos that talk about tips, as well as common mistakes candidates make, for each type of Facebook interviews. Without watching those videos, I wouldn’t have known I would need to think about go-to-market strategy in my product sense interview.
Third, they have a lot of examples of 10/10 answers to Facebook interview questions. Many are brilliant answers. When I am in need of product ideas, I would refer to those videos for inspirations.
It is pricey though. Their individual courses, like the Flagship Meta PM Interview Course, cost $489 each. I ended up buying their Full Library Access Pass with all 9 courses for $579. My reasoning was:
1)For the things that I mentioned above, I believe their content will significantly improve my chance. If I can get Facebook offer in one shot, that’s great, and then it is definitely a good investment.
2) If not, then I will likely try it again in a year. The subscription is for life-time access, and they keep updating the courses regularly. I know several people who got Facebook PM offer in their 2nd or 3rd try. If I spread the few hundred dollars over a few years, it will not be as costly.
3) I also planned to interview with other top tech companies that the courses cover, if I fail Facebook. With only $90 more, I get the access to the prep courses for Google, Microsoft, Amazon and Uber. That seems a good deal to me.
Please make sure you have enough time to go over their content before your interview though. I recommend you spend a month on it. If your interview is coming up next week, and you don’t want to push it for some reason (maybe you’ve already pushed it once, and you are too shy to ask the recruiter to push it again), then you should not purchase the course. You just don’t have enough time to consume, digest, and internalize their content.
Disclaimer: I will get referral fee from Product Alliance if you use the links to purchase. I think it will be a worthwhile investment, but please decide for yourself.
This is another source for me to get Facebook interview questions. Questions are contributed by users, and it is updated frequently.
I got a lot of mock interview partners from this resource. Many of them are good. Occasionally there will be some no-shows. My advice is to pick partners that are really familiar with Facebook interviews. I’ve had some partners who were preparing for other companies. Even though they were good, they could not ask real Facebook interview questions, and could not give feedback based on the Facebook standard.
I came across a few YouTube videos from Exponent, and I like their videos. For questions that I was not so sure, I always tried to search for answers on Exponent. From my experience, the quality of their answers are usually better than what I could find elsewhere online.
They really did a great job in SEO, and became the first resource I found when I started my Facebook interview preparation. I did spend almost all of my first month of preparation on them. Eventually I realized their biggest value for me was their (more or less) comprehensive Facebook interview questions. I could sort those questions by time so I knew which ones were the latest, and from my experience, the latest questions are more likely to be asked in the interview. The answers, which were provided by users, were not always the best though.
I watched a few YouTube videos from Rocketblocks, and I think they are good.
I watched one of their videos about metrics, but didn’t finish. I am under the impression that their videos tend to be longer, and may not be the most efficient use of my time, but it’s only my personal opinion.
I think Facebook PM interview is worth trying for every person who would like to find a PM job at a tech company in the silicon valley. The reason is simple. Many tech companies, including Instacart and Coinbase, structure their interviews in the same way as Facebook does. They have product sense interviews and execution interviews. Some of them even use the exact same questions that are asked in Facebook interviews. So you are essentially preparing for multiple companies, which is an efficient use of your time.
You may think that you need to know the ins and outs of every Facebook product before coming into a Facebook PM interview. That’s not true. I am not a heavy user of Facebook products myself. Whenever I encountered a Facebook feature or product that I was not familiar with, I would just look it up to get a sense of how it works. I find a high level understanding is more than enough for the interviews. Also, the interviewers will help if you are not clear about how the feature/product works. They are more interested in your thought process than in your knowledge in their products.
We all know that Facebook PM interviews are stressful. The questions could be random, and the false negative rate is very high. But you don’t need to stress yourself. If you spend your time on the best resources, and be really disciplined in your practice, you should be able to maximize your chance.
In my case, I had 40+ mock interviews, and countless solo practice sessions. Between my practices and mock interviews, I was able to go over all questions I could find for the two months before my interviews. I would suggest you do the same. You will then be able to internalize the framework, and find many ideas to be reusable for other questions. Keep the notes for all your practices, and go over them in the last few days before the actual interview.
I hope this article will help you ace the Facebook PM interview. If you have any suggestions or questions, please let me know by leaving a comment.