Design a product for people who are blind or have low vision.

How to answer the "design a product for the blind" PM interview question without designing from assumption or reinventing tools that already exist.

"Design a product for the blind"

The trap is designing from assumption. Sighted candidates invent needs instead of starting from how blind users actually live and what tools already serve them well. Interviewers at Google, Microsoft, and Apple are not scoring framework recitation; they are scoring whether you have thought about this community with enough precision to say something true about it.

What you must know before you start

There are two distinct segments with completely different problems, different relationships to technology, and different identities.

Born-blind adults are expert AT (assistive technology) users. They navigate with VoiceOver, JAWS, or TalkBack fluently. They use Be My Eyes (live volunteer video assistance) and Seeing AI (Microsoft, free) for label reading and object identification. High-end smart glasses like OrCam add real-time scene description, though they cost thousands of dollars and insurance coverage is inconsistent. Proposing “an app with voice control” in this segment signals you have done zero homework, because you are describing software that has existed for fifteen years.

Late-onset low vision adults (age-related macular degeneration, diabetic retinopathy) are the fastest-growing segment and the most underserved. They often do not identify as blind and resist specialist tools because the label conflicts with how they see themselves. The product design challenge is not technical: it is dignity-preserving.

A 2025 PMC Scientific Reports study (n=16 legally or completely blind adults) found that object location is the number one underexplored domestic pain point: “if I drop my medicine, it’s like it’s gone into a black hole.” No good solution exists, digital or tactile. The same study documented that modern touchscreen appliances actively broke independence: “since we have newer machines, it’s really hard if I do have to fix the settings because the screen is digital.” Progress that sighted people celebrate has made daily life harder for this segment.

Critically, participants followed a strict problem-solving hierarchy: (1) attempt the task independently, (2) use tactile aids like bump dots and braille labels, (3) use digital tools as a last resort. Most candidates assume blind users want more apps. The research inverts that assumption entirely.

Market context: approximately 2.2 billion people worldwide have vision impairment; 43 million are fully blind (WHO). Employment rate for adults with visual impairments is 52.3% versus 76.3% for sighted adults, with inaccessible workplace software cited as the primary barrier. Both figures give you the viability frame you need to argue market size.

The 2026 shift

AI vision models (GPT-4V, Gemini, Apple Intelligence) can now describe scenes, read labels, identify stains, and locate objects in real time using multimodal APIs. Indoor navigation using Bluetooth beacons and LiDAR became technically solved in 2025. Any competent team can build these features quickly.

Feasibility is not the constraint. The interviewer is evaluating whether you can identify a viable market (someone who will pay), a genuine unmet job (something existing tools do not cover), and a design that does not make the user feel like a charity case. Empathy precision and market understanding are the scarce skills on display now, not technical creativity.

Start your answer with a clarifying question: “Are we optimizing for independent daily living, employment access, or social participation? And are we designing for someone born blind or someone who has lost vision over time?” This costs 20 seconds and signals you know the segments are different from each other, which most candidates demonstrably do not.

Strong answer 1: late-onset low vision, domestic independence

strong

"I'll focus on adults who've lost significant vision in their 50s or 60s. This is the fastest-growing segment globally, driven by age-related macular degeneration. These users own smart speakers and smartphones already, but they do not identify as blind and will not download anything labeled a blindness aid. The unmet job is finding dropped objects at home: a dropped pill, a phone, a set of keys becomes effectively gone with no solution that works today. I'd build a UWB tag system using the same technology as AirTags for the ten or fifteen items in their home most likely to be dropped, with audio feedback through a Bluetooth earpiece they already use for calls. No new device, no stigma, no app with a disability-adjacent name. Distribution through optometrists at the point of low vision diagnosis reaches people before they've built workarounds or accepted dependence on a caregiver. Success metric: weekly domestic tasks completed without assistance from another person."

Strong answer 2: born-blind expert user, employment access

strong

"I'd focus on the 24-point employment gap: 52% employment for people with visual impairments versus 76% for sighted adults. The specific friction: navigating a new office or campus independently on day one, before facilities have configured any accommodation. GPS doesn't resolve indoors. Screen readers can't generate a floor plan. I'd build an employer-facing wayfinding product using Bluetooth beacons and LiDAR that delivers audio turn-by-turn directions through the user's existing screen reader, requiring nothing new from the user. Employers pay for it as part of their ADA accommodation budget, the same line item they already spend on interpreters and modified workstations. That means the user pays nothing and faces no stigma: it appears to them as a standard onboarding tool. Employer-paid is the viability argument. Arriving independently on day one and finding your desk without a sighted guide is the lovable moment. Success metric: time to independent navigation of a new building without assistance."

Weak answer

weak

"I'd build an app with voice control, big text, and high contrast." This fails three ways. First, it conflates low vision with total blindness: these are different segments with different tools and different self-identities. Second, everything described already exists: VoiceOver and TalkBack handle voice-native phone navigation, JAWS handles desktop, Seeing AI reads labels and identifies objects, Be My Eyes connects users to live volunteers for real-time visual assistance. Proposing any of these signals no research. Third, the answer has no segment, no specific job-to-be-done, and no viability argument. The interviewer hears: "I invented a need without talking to anyone who has it."

Why this question is hard

Not technically. Interviewers ask it because most candidates treat the segment as a monolith and treat the problem as obvious. The hardest pain points are ones sighted people do not notice because they are mundane: finding a dropped object on the kitchen floor, operating a touchscreen oven, navigating a hospital lobby. The strong answer is grounded in something specific and true about how people actually live, not something that sounds generous from the outside.

The word “blind” in the prompt is a choice, not a constraint. You get to decide whether to interpret it as total blindness, legal blindness, or significant low vision; born-blind expertise or late-onset adjustment. Naming that choice to the interviewer, and explaining why you made it, is itself part of what they are evaluating.