Most candidates treat the product sense interview like a brainstorming session. They fire off features, sketch UIs in the air, and talk about "enhancing user experience." That’s not what they’re testing.

This is a stress test for decision-making under ambiguity. You’re handed a vague problem and expected to cut through noise, prioritize ruthlessly, and land on a focused path forward. It’s not about inspiration. It’s about discipline.

The structure is straightforward: Why → Who → Pain → What → Validate. But most fail not because they miss the format — they fail because they skip depth.

You don’t win by listing more ideas.
You win by making fewer, better choices.
You win by showing how you think, not what you know.

It’s not about market size — it’s about whether we can win

Starting with “There are 300 million visually impaired people worldwide” gets you nowhere. Big market doesn’t mean it’s yours to take.

The real question is: Does this align with the company’s current goals? Are we in growth, retention, or defense mode? What metric are we trying to move?

A weak answer: “This unlocks a huge underserved market.”
A strong answer: “Improving accessibility reduces legal risk, strengthens brand trust, and supports expansion into regulated sectors — it’s a strategic enabler, not just a feature.”

It is not A. It is B.
It is not a user need dump. It is a business alignment argument.
It is not about what users say. It is about what they reveal through behavior.
It is not about being nice. It is about being necessary.

Judgment starts here. If you can’t justify why now, nothing else matters.

It’s not about user segments — it’s about a real person’s life

“Blind users” is not a user. “A 34-year-old software engineer who relies on VoiceOver, takes the subway daily, and avoids asking for help because he doesn’t want to be a burden” — that’s a user.

You must make the interviewer see him. Rush hour. Subway door opens. Navigation stops. He steps out. No tactile cues. No one speaks to him. He hesitates. Wind hits his face from the left. Is that the building? The street? He takes a step forward — someone bumps him. He’s disoriented. Stressed. Silent.

That’s not a persona. That’s a scene.
That’s not segmentation. That’s storytelling with teeth.
That’s not research. That’s reality.

You don’t serve “groups.” You serve individuals.
And if your user could be anyone, you haven’t chosen.

It is not A. It is B.
It is not about demographics. It is about behavior under pressure.
It is not about averages. It is about extremes.
It is not about scale. It is about specificity.

It’s not about pain points — it’s about leverage

Not every problem is worth solving. The best candidates don’t list pains — they score them.

Use: Severity × Frequency × Solution Gap

Most say, “They can’t see signs.” True, but low frequency. Others say, “They struggle with menus.” Mild inconvenience.

The high-leverage pain? The last 100 meters ， from subway exit to building entrance. Unmapped. Unstructured. No support. High anxiety. Existing tools do nothing here.

Solve this, and you don’t just reduce friction ， you build trust.
This is not a nice-to-have. This is the moment they feel abandoned.

It is not A. It is B.
It is not about how many problems you find. It is about which one changes behavior.
It is not about user complaints. It is about silent suffering.
It is not about convenience. It is about dignity.

Focus on the pain that’s invisible until it breaks.

It’s not about ideas ， it’s about tradeoffs

Saying “I’d build audio cues, haptic feedback, and real-time object detection” shows you don’t understand prioritization.

PMs don’t generate ideas. They eliminate them.

Say: “Option A （ AI object detection ） has high impact but requires new hardware and 12-month development. Option B （ audio guidance using Bluetooth beacons ） has moderate impact but ships in six weeks with existing infrastructure. I pick B. It solves the highest-leverage pain with minimal dependency.”

Then define the MVP concretely:
“When the user exits the subway, Bluetooth beacons trigger location detection. The app delivers a voice prompt: ‘You are facing east. Take five steps forward. Turn right at the tactile paving. The building entrance is 20 meters ahead on your right.’”

No “and also” features. No “maybe later” add-ons. One solution. One pain. One decision.

It is not A. It is B.
It is not about creativity. It is about execution clarity.
It is not about options. It is about ownership.
It is not about doing more. It is about doing the right thing.

FAQ

Q：产品意识面试中常见的误区是什么？

A：产品意识面试中常见的误区是候选人将其视为头脑风暴会议，提出大量的功能和特性，而不是真正评估产品的可行性和用户体验。这种方法可能导致候选人无法展示自己的判断力和决策能力。

Q：如何在产品意识面试中展示自己的判断力？

A：展示判断力的关键在于能够对产品的功能和特性进行有理有据的评估，考虑到用户需求、市场趋势和技术可行性等因素。候选人应该能够清晰地阐述自己的思考过程和决策依据。

Q：产品意识面试中，面试官真正想要测试什么？

A：面试官真正想要测试的是候选人的决策能力和判断力，而不是他们的创造力或提出新颖想法的能力。通过一系列问题和场景，面试官试图评估候选人在实际产品开发中如何做出合理的决定和权衡取舍。