I found that there are very few interview experiences for product positions recruited by large factories on the Internet, and many interview questions of large factories category email list do not have ready-made "correct answers" on the Internet, which leads to a lot of time for everyone to review the interviews when preparing for the interviews of large factories. And sorting, there are category email list many detours in the middle. Here is a brief introduction to my background. I have operated tens of millions of revenue projects in the top 1 vocational education vertical company, and also started a business. I am currently working as a product manager in a listed education company. Unfortunately.
I have not caught up with the dividends of the mobile Internet explosion. It did not get on the rocket of the rapid development of the category email list industry's business. So my experience sharing is about the savage growth experience of vertical industry products from 0 to 1. It may not category email list be so convincing, but it is better than those who graduated from 985/211 and entered the big factory with a halo all the way. The "face scriptures" that jumped over and over again and again are more down-to-earth (I am sour). As a user, I just hope that I can find real "amateurs" like me to share on the Internet. Well, let's get down to business, please listen to the question: 1. Why do you want to make this product? 1. Error demonstration.
This is a question that tests the core competence category email list of product managers. If our answer is: because the boss, company, and customer have requested, our score on this question is almost 0. Such an answer can only show that we are a product assistant, or a functional product category email list manager, referred to as a "tool person", whose main role is to complete the tasks assigned by the leader or the company. 2. Problem solving ideas What the interviewer wants to hear is whether we have researched user needs when we are making this product? Have you tapped the user's pain points? There is almost no perfect answer to this question, because as long as the product.