Product Sense · Interview

Product sense interview questions.

Product sense is more judgment than craft. Ten questions designed to reveal the judgment without being 'estimate McDonald's revenue'.

10 questions · rubric-backed · Built for small-team hiring panels
The rubric these map to
40%
Product judgment
Trade-off reasoning. Says no with structure. Cites user evidence.
15%
Experience relevance
Shipped products you can point to. Specifics on scope, metrics, decisions.
20%
Stakeholder communication
Aligns eng + design + sales without being vague or political.
15%
Attitude & ownership
Owns outcomes, not output. Learns from failed launches.
10%
Culture fit
Behavior in roadmap disagreement + when strategy shifts.

The questions.

  1. 01
    situational medium · data-conflict

    Your quant analyst says users don't want feature X. Your best customer says they do. Who do you believe?

    Strong answer
    Neither blindly. Investigates — is it the same feature they're describing? Is the quant measuring the right thing? Talks to 5 users to triangulate.
    Weak answer
    'Data wins.' Or 'the customer is always right.' Either is wrong.
  2. 02
    culture medium · feedback

    A designer pushes back hard on a decision you made. How do you respond?

    Strong answer
    Curious, not defensive. Asks what they're seeing that you're not. Separates their reasoning from their emotion. Changes your mind if they're right. Explains clearly if they're not.
    Weak answer
    Either steamrolls or caves. Either way, no real conversation.
  3. 03
    stakeholder medium · sales

    Sales commits to a feature with an enterprise prospect that's not on your roadmap. How do you handle?

    Strong answer
    Debriefs with sales to understand real need vs stated need. Evaluates fit with strategy. Clear yes-with-conditions or no-with-alternative. Doesn't punish sales for closing deals.
    Weak answer
    Either adds it silently or refuses without engaging.
  4. 04
    product medium · prioritization

    You have 10 feature requests from enterprise customers. How do you prioritize?

    Strong answer
    Frameworks (RICE, ICE) used sanely, not dogmatically. Asks about strategic fit, not just loudest customer. Distinguishes 'painful' from 'asked for.'
    Weak answer
    Whoever yelled loudest or paid most. Or a Jira-style priority queue with no strategy.
  5. 05
    product medium · metrics

    You're launching a new feature. What metric tells you it's succeeding?

    Strong answer
    Leads with user-facing value (not just 'DAU went up'). Distinguishes leading from lagging indicators. Guardrails to catch unintended harm.
    Weak answer
    'Users will love it.' Or picks a vanity metric.
  6. 06
    product hard · strategy

    Your product has product-market fit in one segment. CEO wants to expand to a new one. How do you think about whether to do it?

    Strong answer
    Evaluates whether current PMF transfers. Cost of serving new segment. Risk to existing segment's experience. Would talk to 10 prospects first. Discusses focus as a strategic choice.
    Weak answer
    'Sure, let's do it.' Or 'no, stay focused' — either without analysis.
  7. 07
    stakeholder medium · eng-disagreement

    Engineering tells you a feature you need will take 6 months. You think it should take 6 weeks. What do you do?

    Strong answer
    Asks why. Doesn't assume engineering is gaming estimates or they're being unreasonable. Breaks down the 6 months into components. Proposes phased shipping. Respects engineering judgment while pushing back.
    Weak answer
    Either accepts silently or escalates aggressively. No curiosity.
  8. 08
    product medium · failure

    Tell me about a feature you shipped that failed. What did you learn?

    Strong answer
    Specific feature. Specific failure mode (low adoption, negative metric, user complaint). Clear lesson applied to next shipment.
    Weak answer
    'Everything worked.' Or vague 'we iterated.'
  9. 09
    communication medium · launch

    Write a tweet announcing a new feature. What's your editing process?

    Strong answer
    Cuts 50% of words. Leads with user benefit. Avoids buzzwords. Knows who they're writing for. Has colleagues read it.
    Weak answer
    First draft is the final. Lots of adjectives.
  10. 10
    experience baseline · resume-probe

    Your resume says you grew product X's usage by Y%. What did YOU do vs what the team did?

    Strong answer
    Clear boundary between individual contribution + team. Credits specific colleagues. Knows why certain decisions were made even those they didn't make.
    Weak answer
    Claims credit for team output. Vague about own role.
Why stop at ten?

Lucida runs round one for you, and books the shortlist on your calendar.

Adaptive interviews tuned to the role, rubric-backed scoring, and a founder-ready briefing for every candidate who clears the bar. You do the human call.

Try it on your next role → See how Lucida works
Related interview question sets