Interview Questions

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

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

Jacky Y. - "Problem scope: Can this system detect Bot in real-time online or offline? Both. Online traffic: 1M DAU. Latency: 2s. Offline frequency: daily Offline data: 2B activity logs. Data: How do we know a Bot player (Label)? Human label. Imbalance data: reweight, resample. Develop a Bot simulator to generate more data offline for training. Given lower weight to simulator data than human label. Features: Signals from different models online. Log all the features for offline. Propose new features: dail"See full answer

Sarah K. - "I once had to change a decision i had previously made when I got stakeholder feedback that seemed to contradict what was already designed or already even built - such as the way a page was architected or the designs or colors used on a page. I had a justification for all decisions made, but sometimes the stakeholder feedback brings a perspective, such as a part of the user experience, that I had not thought of before. So I then went back to the original design or product and made an adjustment o"See full answer