All jobs / Product manager

UX Collaboration interview questions

UX Collaboration questions a Product manager can be asked, from first job to senior. Open one to see the strongest answer and why it works.

  1. A designer walks you through a flow for inviting a teammate: three screens, all working.

    What do you look for as the PM?

    The strongest answer: The paths that are not on the happy screens: how someone arrives here, what happens when the invite fails or the person already has an account, and where they land afterwards

    Why it works: Exactly — your job in a flow review is the states the business cares about: entry, failure, already-exists, and where the user ends up.

    • Read the paths, not the screens.
    • How do they get here?
    • What happens when it fails?
    • Where do they land after?

  2. You have one passionate quote. What do you not write on the slide?

    The strongest answer: “Users want this” as if it were a study — I label it n=1 and say what I will do next

    Why it works: Exactly. Label the one. Research-shows, pies of one, and 90% scores are fiction.

    • Label n=1.
    • Say the next check.
    • Do not write “users want.”
    • No invented need %.

  3. The first-run screen is blank. Whose job is that?

    The strongest answer: Product’s — an empty state is a moment with a next step, not “design will decorate later”

    Why it works: Exactly. First-run is a job. Fake busy accounts are a trust problem.

    • Empty states are a product moment.
    • Give a next step.
    • Do not leave it as décor later.
    • Do not fake accounts for screenshots.

  4. A designer shares a lo-fi wireframe and asks for your feedback. Your instinct is to say the button should be on the right and the list should be a table.

    How do you give the feedback?

    The strongest answer: Against the problem, not the pixels: name the case that worries me and why — someone with two hundred of these has to find one — and leave the layout to the designer

    Why it works: Right — describe the job, the case and the constraint. Prescribing a control hides the reason, so the designer cannot solve for it.

    • Feed back on the problem.
    • Name the case that worries you.
    • Give the constraint, not the control.
    • Lo-fi is the cheap moment.

  5. Engineering asks if five interviews “count.” What do you say?

    The strongest answer: They count as qualitative evidence for a decision, labelled as such — they are not a 73% and I will not pretend

    Why it works: Exactly. Label the method. 73%, funnel-only, and fake weights are three lies.

    • Qualitative counts when labelled.
    • Do not turn 5 into 73%.
    • Funnels are not the only evidence.
    • No fake weights.

  6. You are observing a usability session. The participant has been hunting for the export button for a minute and looks uncomfortable.

    What do you do?

    The strongest answer: Stay quiet and let the moderator run it — that minute is the finding. I write down what they tried and the words they used, and save my questions for the debrief

    Why it works: Exactly — the struggle is the data, and it is the moderator’s session. Note behaviour and quotes; argue about meaning afterwards.

    • Watch; do not rescue.
    • The struggle is the finding.
    • Write what they did and said.
    • Take questions to the debrief.

  7. You are invited to a design critique. Two directions are on the wall and the team has forty minutes.

    What do you contribute, and what do you not?

    The strongest answer: I restate the problem, the users and the hard constraints — legal, technical, what we have promised — and critique each direction against those. I do not rank them by taste or redesign in the room

    Why it works: Right — the PM brings the criteria. A critique with no shared problem statement collapses into taste.

    • Bring the criteria, not the verdict.
    • Restate the problem and users.
    • Name the hard constraints.
    • Critique against them, not taste.

  8. Growth wants a confirm-shaming cancel flow. What do you do?

    The strongest answer: No — that is a trust tax, and I will not take a short-term number that way — I offer a clearer cancel and a real save offer

    Why it works: Exactly. A no with a real alternative. Legal-bury and hurt-if-up are how you become the pattern.

    • Refuse confirm-shaming.
    • Offer a clear cancel + honest save.
    • Do not bury the control.
    • Up-and-to-the-right ≠ allowed.