"Product manager is someone who drives a product with customer-first approach while doing what is right for the business. They absorb chaos from all directions(customers, internal stakeholders, leadership) and bring clarity and direction to the whole team, marching them towards a common goal."
Phani C. - "Product manager is someone who drives a product with customer-first approach while doing what is right for the business. They absorb chaos from all directions(customers, internal stakeholders, leadership) and bring clarity and direction to the whole team, marching them towards a common goal."See full answer
"Designing a system to track review abuse on Amazon.com involves detecting fraudulent, manipulative, or biased reviews while ensuring genuine customer feedback isn't mistakenly flagged. Here's a high-level breakdown:
1. Goals
Detect and prevent fake or abusive reviews.
Maintain integrity and trust in the review system.
Support scalability for millions of products and reviews.
2. Key Abuse Scenarios
Fake positive reviews (e.g., sellers boosting their own products).
Fake"
Tesfaye M. - "Designing a system to track review abuse on Amazon.com involves detecting fraudulent, manipulative, or biased reviews while ensuring genuine customer feedback isn't mistakenly flagged. Here's a high-level breakdown:
1. Goals
Detect and prevent fake or abusive reviews.
Maintain integrity and trust in the review system.
Support scalability for millions of products and reviews.
2. Key Abuse Scenarios
Fake positive reviews (e.g., sellers boosting their own products).
Fake"See full answer
"Clarify
"What do you mean by favorite product? Are you thinking specifically hardware, software, or a feature within those, or something non-electronic? Dealer's Choice.
"Are you asking why I love this product, or to explain why this product is a market leader independent of how i feel about it? Talk about why YOU love this product.
Rephrase Question
With all that in mind, i want to rephrase the question. "What is your favorite software product and what features in this product"
Tim W. - "Clarify
"What do you mean by favorite product? Are you thinking specifically hardware, software, or a feature within those, or something non-electronic? Dealer's Choice.
"Are you asking why I love this product, or to explain why this product is a market leader independent of how i feel about it? Talk about why YOU love this product.
Rephrase Question
With all that in mind, i want to rephrase the question. "What is your favorite software product and what features in this product"See full answer
"Recently, I had to make a decision that I could automate a part of a process now and help the operations team reducing 9 hours of manual work to 60 minutes for one client. The second option was to fully automate the end to end process that would take 4 weeks of development, but fully automate the process and that could be rolled out across the board.
The process was to change the member's paperless preference to paper when a sent email gets bounced 3 times in a row and inform her with a paper"
Anonymous Aardvark - "Recently, I had to make a decision that I could automate a part of a process now and help the operations team reducing 9 hours of manual work to 60 minutes for one client. The second option was to fully automate the end to end process that would take 4 weeks of development, but fully automate the process and that could be rolled out across the board.
The process was to change the member's paperless preference to paper when a sent email gets bounced 3 times in a row and inform her with a paper"See full answer
"Firstly, it's mentioned "ideas" & not "idea". I would like to get more context.
Is it one idea or multiple ideas on a roadmap? Is it tied to the same broader goal?
Is this a pattern where team has been disagreeing with ideas for a while?
If it's the 1st, then it's fine, we can look into it. If it's the 2nd, then it raises a bit of a concern.
Gonna assume it's the 1st.
I'd probably get clarity by asking questions
To the team:
Which idea/s are being disagreed upon?
Are all member"
Debajyoti B. - "Firstly, it's mentioned "ideas" & not "idea". I would like to get more context.
Is it one idea or multiple ideas on a roadmap? Is it tied to the same broader goal?
Is this a pattern where team has been disagreeing with ideas for a while?
If it's the 1st, then it's fine, we can look into it. If it's the 2nd, then it raises a bit of a concern.
Gonna assume it's the 1st.
I'd probably get clarity by asking questions
To the team:
Which idea/s are being disagreed upon?
Are all member"See full answer
Product Manager
Behavioral
🧠 Want an expert answer to a question? Saving questions lets us know what content to make next.
"My approach to dealing with difficult stakeholders has always been:
Engage - Directly engage with the stakeholder, meet or chat
Listen - Listen to what they have to say, patiently.
Understand - Understand their POV, even if it is impossible at some times
Ask - Ask clarifying questions. Why? When? What?
Engage again - Keep them in the loop until there is closure
For example, we were in the final stages of a very important, strategic project for our organization. I was leading th"
Jane D. - "My approach to dealing with difficult stakeholders has always been:
Engage - Directly engage with the stakeholder, meet or chat
Listen - Listen to what they have to say, patiently.
Understand - Understand their POV, even if it is impossible at some times
Ask - Ask clarifying questions. Why? When? What?
Engage again - Keep them in the loop until there is closure
For example, we were in the final stages of a very important, strategic project for our organization. I was leading th"See full answer
"Let me tell you about a time where a website I managed suddenly showed slow performance and the mistake on our side was it was unnoticed until a user reported the issue to management. As a PM for that project, I took full responsibility of the situation and worked with the engineering team to quickly resolve it. This mistake taught me the importance of focusing and monitoring non functional requirements as well in addition to new feature development /adoption where I was mostly spending my time"
Sreenisha S. - "Let me tell you about a time where a website I managed suddenly showed slow performance and the mistake on our side was it was unnoticed until a user reported the issue to management. As a PM for that project, I took full responsibility of the situation and worked with the engineering team to quickly resolve it. This mistake taught me the importance of focusing and monitoring non functional requirements as well in addition to new feature development /adoption where I was mostly spending my time"See full answer
"I most want to communicate a few principals of conflict resolution that I believe were integral in this situation, which are mutual respect, a results orientation, an unwavering focus on the user.
To that end, here’s how I’d like to structure this answer: First, I’ll tell you about the project we were working on, to provide some background for you. Second, I’ll describe the disagreement. Third, I’ll describe how we arrived at a solution, and finally, I’ll discuss how those 3 conflict resolut"
Ross B. - "I most want to communicate a few principals of conflict resolution that I believe were integral in this situation, which are mutual respect, a results orientation, an unwavering focus on the user.
To that end, here’s how I’d like to structure this answer: First, I’ll tell you about the project we were working on, to provide some background for you. Second, I’ll describe the disagreement. Third, I’ll describe how we arrived at a solution, and finally, I’ll discuss how those 3 conflict resolut"See full answer
"Best practices for prioritizing customer service requests
Prioritizing support requests is a key part of creating a customer journey optimized for maximum revenue. If you want to start using a ticket prioritization process that will boost both customer satisfaction and your bottom line, we've got nine proven best practices below:
Respond to your most loyal customers first
Tag repeat customers as high-priority tickets
Automate simple requests wherever possible
Mark tickets with urg"
Hayatu H. - "Best practices for prioritizing customer service requests
Prioritizing support requests is a key part of creating a customer journey optimized for maximum revenue. If you want to start using a ticket prioritization process that will boost both customer satisfaction and your bottom line, we've got nine proven best practices below:
Respond to your most loyal customers first
Tag repeat customers as high-priority tickets
Automate simple requests wherever possible
Mark tickets with urg"See full answer
"1. Requirements Analysis
Functional Requirements
Video streaming with multiple quality levels
Content browsing and search
Continue watching functionality
Content recommendations
Non-Functional Requirements
Low latency video delivery (<2s startup time)
High availability (99.99% uptime)
Scalability to handle millions of concurrent streams
API response time < 100ms
2. Microservices Architecture
Core Microservices
Content Service
Content metadata mana"
Vince S. - "1. Requirements Analysis
Functional Requirements
Video streaming with multiple quality levels
Content browsing and search
Continue watching functionality
Content recommendations
Non-Functional Requirements
Low latency video delivery (<2s startup time)
High availability (99.99% uptime)
Scalability to handle millions of concurrent streams
API response time < 100ms
2. Microservices Architecture
Core Microservices
Content Service
Content metadata mana"See full answer
"Found bug will not impact on the new requirements, if the engineering team aware of the source of the bug and the severity, than it can easily be handled and regression test to perform for a quality check. The new requirement should be equally prioritize for groom and start creating task and team to work on it. Finally based on the severity of the bug you can shuffle the resources between these items."
Jagat mohan B. - "Found bug will not impact on the new requirements, if the engineering team aware of the source of the bug and the severity, than it can easily be handled and regression test to perform for a quality check. The new requirement should be equally prioritize for groom and start creating task and team to work on it. Finally based on the severity of the bug you can shuffle the resources between these items."See full answer
"We had a huge launch on September 1st of this year where we completely redesigned our application from the grounds up and also migrated to a new platform (React.JS). This project took us 8 months and the launch was a huge deal for the team.
Unfortunately the launch wasn't as smooth as we expected and despite doing multiple rounds of QA, some major issues cropped up in the core part of the app right after launch and our client was quite upset since it was disrupting their day-to-day workflow.
"
Aabid S. - "We had a huge launch on September 1st of this year where we completely redesigned our application from the grounds up and also migrated to a new platform (React.JS). This project took us 8 months and the launch was a huge deal for the team.
Unfortunately the launch wasn't as smooth as we expected and despite doing multiple rounds of QA, some major issues cropped up in the core part of the app right after launch and our client was quite upset since it was disrupting their day-to-day workflow.
"See full answer
"A clarifying question: Is this question asking about when I met a tight deadline in a project or how did I manage a project that had a tight deadline?
The answer uploaded to this question is good, I would also add 'creating a critical path from overall project schedule and then making sure that none of the deliverables in the critical path are sacrificed in order to meet the tight deadline' as an action taken."
Ushita S. - "A clarifying question: Is this question asking about when I met a tight deadline in a project or how did I manage a project that had a tight deadline?
The answer uploaded to this question is good, I would also add 'creating a critical path from overall project schedule and then making sure that none of the deliverables in the critical path are sacrificed in order to meet the tight deadline' as an action taken."See full answer
"select employeename, employeeid, salary, department, DR
from (
select employeename, employeeid, salary, dense_rank() over (partition by department order by salary desc) DR, department from employee
)
where DR <=3
order by department, DR"
Sreeram reddy B. - "select employeename, employeeid, salary, department, DR
from (
select employeename, employeeid, salary, dense_rank() over (partition by department order by salary desc) DR, department from employee
)
where DR <=3
order by department, DR"See full answer
"Let me tell you about the time where I pivoted strategies and we launched a paid loyalty program Instead of a free one.
This was a time at Reddoorz when we were gearing up to launch a loyalty program to drive sustainable business by creating a loyal user base.
Initially , we had decided to launch a program where users can Opt-In for free. The idea was to get On-Board at least 40% of repeat user base into the loyalty program to drive retention. Competitive bench marking also led to our inclinat"
Vivek S. - "Let me tell you about the time where I pivoted strategies and we launched a paid loyalty program Instead of a free one.
This was a time at Reddoorz when we were gearing up to launch a loyalty program to drive sustainable business by creating a loyal user base.
Initially , we had decided to launch a program where users can Opt-In for free. The idea was to get On-Board at least 40% of repeat user base into the loyalty program to drive retention. Competitive bench marking also led to our inclinat"See full answer
"One of the most challenging situations was joining a new startup to realize that they did not figure out their core product and that customers were dissatisfied and leaving in droves.
I worked together with the leaders to understand the core issue and the reasons that the customers were leaving. Then together with the team, we set out to map out those core issues and the gaps that we had in our product.
We then worked towards designing a new solution to address those gaps and build an MVP. W"
WaterBuffalo - "One of the most challenging situations was joining a new startup to realize that they did not figure out their core product and that customers were dissatisfied and leaving in droves.
I worked together with the leaders to understand the core issue and the reasons that the customers were leaving. Then together with the team, we set out to map out those core issues and the gaps that we had in our product.
We then worked towards designing a new solution to address those gaps and build an MVP. W"See full answer
"Just a bit of context on what could be a risk in Product or Software Development. We talk about the Scope, Quality, and Time Triangle. IMHO the only variables that can matter and can pose risk are these.
Try to form an answer where you used the Effort, Value, Risk framework to quantify the risk.
The answer can be similar to short term sacrifices for long term gains, as you do take in mind the risk the short term sacrifices pose.
Situation - I was leading the team to complete an overhaul of the"
Umang S. - "Just a bit of context on what could be a risk in Product or Software Development. We talk about the Scope, Quality, and Time Triangle. IMHO the only variables that can matter and can pose risk are these.
Try to form an answer where you used the Effort, Value, Risk framework to quantify the risk.
The answer can be similar to short term sacrifices for long term gains, as you do take in mind the risk the short term sacrifices pose.
Situation - I was leading the team to complete an overhaul of the"See full answer
"Step 1: Clarifying the Problem Scope
Assumptions and basic system requirements:
Cashless payments: The machine supports cashless payment methods like credit cards, mobile wallets, or NFC-based payments (e.g., Apple Pay, Google Pay).
Multiple candy options: The machine offers different types of candy.
Inventory management: The system tracks the stock of candy in real-time.
User interface: A display screen for users to select the type of candy, make payments, an"
Ramendra S. - "Step 1: Clarifying the Problem Scope
Assumptions and basic system requirements:
Cashless payments: The machine supports cashless payment methods like credit cards, mobile wallets, or NFC-based payments (e.g., Apple Pay, Google Pay).
Multiple candy options: The machine offers different types of candy.
Inventory management: The system tracks the stock of candy in real-time.
User interface: A display screen for users to select the type of candy, make payments, an"See full answer