Behavioral Interview Questions

Dean Z. - "I will use below 4 pillars to rate and prioritize those 5 projects: Analyze the impact of those 5 projects, to our team and to the whole company maybe Find out if those 5 projects have any dependency between each other Clarify the timeline of each project Identity the status of resources to work on those 5 projects and also the status of their dependencies"See full answer

Mohammad shahid S. - "We were working on a very high stake migration project where were suppose to migrate all the traffic (more than 40 million users per day) from legacy to modern micro-services based architecture. Before making this massive migration decision, company has already developed a lot of services outside monolith and we were suppose to utilise those services. Some these services there were PADs responsible to communicate the specific vendor APIs. For each vendor we had a dedicated PAD. Fast forward"See full answer

Pradeep V. - "No Interoperability between Digital Wallet Payments ? User Pain Points: Lack of Interoperability: Digital wallets operate in silos, forcing users to rely on inefficient workarounds, such as transferring funds to a bank account and then to another wallet, resulting in delays and extra effort. Time-Consuming Process: Current methods to move money between wallets are tedious, often taking 1-3 business days, which can be especially inconvenient for time-sensitive transactions. High Friction fo"See full answer

Hamzeh H. - "S – Situation: In a university project, my team was building a collaborative code editor. As part of the functionality, we needed a login system so users could securely access their sessions and collaborate in real time. T – Task: I was responsible for implementing the authentication system. Initially, I planned to build the entire login system from scratch, including user management, password storage, and session handling. But as the deadline approached, I realized that implementing thi"See full answer

Sam - "Disagreement --> persistent ---> more data insights ---> positive relationship ---> mentor/trust"See full answer

Lati K. - "I generally struggle with stakeholders and partners who doesn't communicate enough. Now it could be either they don't invest sufficient time and energy in doing so or at times they lack the skill sets to do so. In both the cases, the entire responsibility fell on the other person to dig deep into why someone is doing the way they are doing, reading into patterns and behaviour of their personality and adapting to those communication styles"See full answer

Vikas T. - "This is coming from an Amazon manager who are taught to PIP people out. The first part he said is completely opposite with Amazon. They just pull people randomly into the room and put them either on dev list or PIP. This is unfortunately true for all of Amazon."See full answer

Issac K. - "I learned that people and teams build great products, not processes and job descriptions. The quality of the teamwork will directly reflect in the quality of the product. My biggest failure as a product manager was failing to build a foundation of teamwork before starting a project with a new cross-functional team. As the PM of a new product, I like to get my engineers involved early and often in the design process, but tight schedules with an even tighter resources made the tension and st"See full answer

Danny - "There are way more learning opportunities for us here if we acknowledge that this was not a good example and provide tips on how to improve the answer. All the answers here are superficial and it is clear that the interviewee was unprepared. . The mention of quote "a wise man told me..." (instead of getting to his own personal points) and some lack of confidence with the metrics portion are red flags. . For more concrete example, it is hard to believe that no one wants to fix the slow build proc"See full answer

Siddharth P. - "I believe these are the traits of a great PM. I see PM to be somone who is a great manager of customer problems and for that he/she has to be: Be an expert at the one domain and know the customer of the product in that domain and curate experiences for them better than the competition. Be persuasive - Get things done by convincing rather than commanding. Learn how great products are by being an engineer. Be a fearless leader by championing teams ideas all the way to the management la"See full answer

Ashley C. - "I follow a variation of the RICE framework when prioritizing how I ship product features. I start by looking at: Reach: Because the customer segmentation across our product portfolio is so similar, I tend to hold a lot of weight on product features that will maximize our customer reach with a minimal LOE. Impact: After establishing which customer segments will benefit from the product feature, I determine the urgency and estimated impact on each customer segment based on customer i"See full answer

Hamzeh J. - "Evaluate how much the issue affects the sprint goal and timeline. If it blocks the main goal, it needs to be prioritized. Discuss the issue with the team. Analyze the root cause of the issue. Is it because of unclear requirements or a design flaw? You may need to re-prioritize tasks. If the issue is serious enough to delay or change the sprint goal, communicate the updates to stakeholders and manage their expectations. Keep an eye on the solution’s progress and adjust your plans a"See full answer

Balaji G. - "This is the answer I have prepared. Please let me know your comments and how I can improve the answer. I have worked on many process improvement initiatives and projects. I want to share an initiative that I led and delivered while at my previous employer. It had a great impact on over 60 programs and projects across teams in six different countries. Analysts and program managers used to generate a monthly program performance report that deals with all aspects, including schedule, risks, costs"See full answer

Anjali V. - "I feel this is more about "Describe a time when I failed or struggled" rather than "Project Failure"."See full answer

A R. - "I liked the role of a TPM due to the opportunity to contribute to the multiple dimensions of software product development. As a TPM I need to collaborate with multiple teams like Engineering, Product, and other business functions, but I also get the opportunity to contribute to the technical aspects of the program/project. I can use my sharp analytical skills to identify/anticipate problems, and leverage my problem solving skills to unblock the teams. I orchestrate multiple teams effort to del"See full answer

Anonymous Raven - "How often do we get 15 min to answer a question? Wondering isn't the expectation to answer this in 3-5 min?"See full answer

Umang S. - "In my role as a Product Owner, I was developing a platform for a logistics company. As a PO and that too of a digital agency, my work was mostly before-end-to-after-end, it would start from pitching, strategy, product management, launch, funding deck prep. In mid of the product management cycle, the client starts adding pressure to deliver way before the deadline, as they had found the PE firm that conceptually was ready to start funding discussion, since this was not scoped before the start,"See full answer

Karthik T. - "In our product portfolio there were many teams and we were almost 12 product managers interacting closely to deliver the entire product feature area. Situation was that we were frequently had defects come in which will result in defects pushed back and forth. Goal was to avoid this as SLA of defects was getting impacted immensely there were priority 2 defects which we were sitting for couple of weeks before being looked at. There was a need to establish a triaging process. Along with my leaders"See full answer

Saket S. - "I will divide my answer in 2 parts: Process I use for managing risks in any Project I will explain a real life situation where a Risk occurred and how I managed it Process for Risk Management can be broken down into 3 parts: Risk Identification: Risk identification is a team effort and is an ongoing process that happens throughout the Project. Technical Risks are usually identified during design/build/testing stage. I maintain a Risk register document to capture all the risks identified"See full answer