Product Manager Behavioral Interview Questions

Anonymous Crayfish - "Let me tell you about a time when I solved a problem at my previous company (one of the top 10 Fortune 500 companies). This was an internship and I was coming with almost 2 years of experience and 2 semesters of my graduate program. My experiences have mostly been theoretical or with startups. I've never solved problems at scale. The first week at this team was slow and relaxed, it was just onboarding. The real work started from the 2nd week when I felt like I was pushed into the ocean with n"See full answer

Sathwik N. - "I worked on an automated customer support WhatsApp chatbot for my previous organisation, IIMLoans. The project was not initially on the roadmap. The reason for it being prioritised in the middle of the roadmap was the user drop-off rates that were observed at the inbound to lead qualification step due to the short team size. Since the organisation was an emerging startup and had constraints on budget and man-power, we decided that leveraging AI could help us solve this problem and avoid bigger p"See full answer

Howard H. - "We have to work with the c-suite to understood the direct quartly outcomes or goals. This could be our epic and then we try to break that down into business value and complexity . This will allow us to prioritize whats next. From there we can structure a mvp to cover maybe some of these areas to understand the estimation of this work. After the first couple weeks we can structure a roadmap and then define when"See full answer

Dhruv M. - "During my internship at Inspira Analytics, our intern team had worked for two weeks on a client presentation for a new data dashboard. Unfortunately, during the final review, the manager pointed out several major flaws in our analysis and asked us to redo the entire structure. The feedback was blunt, and the team felt discouraged, questioning whether our efforts were even valued. As the informal team lead, I felt responsible for helping lift the team’s morale and refocus everyone so we could del"See full answer

Naresh A. - "Although there is no fixed or predefined framework that I follow to prioritize, I do have a methodical criterion that is suitable to my organization and practices. The business outcome/value proposition of each project/request - try to quantitative every metric below Number of customers going to be impacted in that product vertical - item with more customers gets more weight Is this an existing feature or a new feature - existing features get more weightage especially if thi"See full answer

Aimable - "."See full answer

S G. - "If it's a product end to end, then there's a lot to say. If it's just a feature on top of a product then I will focus on the complexity and how I break complex tasks into small milestones to partner with XFN teams to nail it. Focus on situation, task, actions and results"See full answer

George A. - "strengths- Working with engineering, working with metrics, execution Weakness- ideation and visioning, working with design"See full answer

Nishant S. - "First step would be to define the goals. Many different opinions could themselves be due to unclear goals. The process of arriving at goals could be based on what are the larger goals of the company or based on prioritization of impact/potential impact. Although not all the stakeholders would possibly be involved in the goal setting exercise, it's important to explain the process behind arriving at the goals and why these are important. Next step would be to get buy-in of the stakeho"See full answer

Sergio C. - "There are many places where you can gather feedback. We can divide the feedback from external and internal sources External sources: facebook twitter reddit G2. Internal sources: on-app surveys or chats support Support engineers Sellers Recordings or notes from other PMs However, you always have to talk with the customers so customer interviews are very important. "See full answer