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

Intermediate

May 2026

Summary

PM interview at Booking.com with a product sense question about refining a user story for a calendar app. Pretty focused session, just the one scenario but they really dug into it.

Questions Asked (1)

You're a PM on a calendar app focused on improving error handling. Given the user story 'As a user, I want to see when my changes haven't been synchronized recently so that I know there was a problem,' how would you prepare this for the backlog and what would you change about it?

Agile / Sprint ManagementProduct Sense & Ideation

Author's notes

I spent the first minute just restating the user story back to them which, in retrospect, was a waste of time.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by critiquing the user story against INVEST criteria, identifying its ambiguity and lack of user value. Then propose a refined story with clear acceptance criteria, and outline the steps to prepare it for the backlog, including prioritization, estimation, and dependencies.

Pro tip: Frame the story around the user's need to trust the app, not just see errors. This shifts the focus from technical implementation to user value, which resonates with stakeholders.

1. Critique the User Story

Evaluate the story against INVEST criteria: it's independent, negotiable, valuable, estimable, small, and testable. Identify issues: vague terms like 'recently' and 'problem', and lack of clear user benefit.

2. Refine the User Story

Rewrite the story to be specific and valuable. For example: 'As a user, I want to see a clear indicator when my calendar changes haven't synced in the last 5 minutes, so I can take action to resolve the issue and trust my calendar.'

3. Define Acceptance Criteria

Specify measurable conditions: e.g., indicator appears if sync fails for >5 minutes, shows last successful sync time, and provides a way to retry or troubleshoot.

4. Prepare for Backlog

Break down into tasks, estimate effort, identify dependencies (e.g., sync service, UI components), and prioritize based on user impact and business value.

5. Consider Edge Cases and Metrics

Think about offline mode, multiple devices, and how to measure success (e.g., reduction in support tickets, increased user trust).

Key Points to Mention

INVEST criteria for user stories
Ambiguity in 'recently' and 'problem'
User value: trust and transparency
Acceptance criteria and definition of done
Prioritization based on impact vs effort
Metrics to measure success (e.g., support tickets, user engagement)

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