Booking.com·Product Manager·Onsite - Product Sense / Strategy·Intermediate

Intermediate

Jun 2026

Summary

PM interview at Booking.com with a technical troubleshooting scenario. One question, pretty focused, felt more like a product ops problem than a pure strategy question.

Questions Asked (1)

You're a PM at Booking.com and a sales manager tells you the app is returning a 404 error. Walk through how you'd investigate.

Root Cause AnalysisCross-functional AlignmentProduct Analytics & Metrics

Author's notes

I went straight to triage mode: is this one user or widespread, which surface (web vs app vs API), recent deployments, that kind of thing.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by acknowledging the sales manager's report and committing to a swift, structured investigation. Then, systematically narrow down the issue by gathering specifics, checking dashboards, and coordinating with engineering to identify the root cause and impact. Finally, outline a plan for resolution, communication, and prevention.

Pro tip: Demonstrate empathy by recognizing the sales manager's urgency and the potential revenue impact, then show you can balance quick mitigation with long-term fixes. Mention that you'd personally verify the issue to avoid miscommunication.

1. Gather Details and Reproduce

Ask the sales manager for specifics: exact URL, user account, device, browser, and steps to reproduce. Attempt to reproduce the 404 yourself to confirm and understand the scope.

2. Check Monitoring and Analytics

Review error monitoring tools (e.g., Sentry, New Relic) and product analytics (e.g., Mixpanel, Amplitude) to see if the 404 is widespread or isolated. Look for recent deployments or configuration changes that might correlate.

3. Engage Engineering and Triage

Escalate to the on-call engineer or relevant team with the gathered evidence. Collaborate to triage: is it a frontend routing issue, backend API failure, or infrastructure problem? Determine severity and impact.

4. Communicate and Mitigate

Provide timely updates to the sales manager and other stakeholders. If needed, implement a hotfix or rollback. Document the incident and ensure affected users are informed if necessary.

5. Root Cause and Prevent

After resolution, conduct a post-mortem to identify the root cause. Implement preventive measures such as better testing, monitoring alerts, or process improvements to avoid recurrence.

Key Points to Mention

Prioritize customer impact and revenue implications
Use data and monitoring tools to assess scope and severity
Collaborate cross-functionally with engineering, sales, and support
Follow incident management best practices (triage, communication, post-mortem)
Consider both immediate fixes and long-term preventive actions
Maintain clear and proactive communication with stakeholders

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.