Clarify the goal
- Start from a human experience, not technology
- Give the recommendation before the framework.
Apple · Product manager · Apple Product Sense & Design
Design an Apple product experience for a user with low vision.
Build a defensible answer, then pressure-test it in the same workspace where you can save the attempt.
See this question in OfferHack Browse the question first. Premium opens the complete worked answer and coaching when you need them.This is a constructed rehearsal, not an official company answer or a prediction of what an interviewer will ask. A company-specific practice prompt synthesized from published interview guidance, candidate reports, official product material, role descriptions, and company values; it is not a claim that this exact question will be asked.
Start with a position
Give the interviewer your decision before the framework.
For “Design an Apple product experience for a user with low vision.” at Apple, I would prioritize a person using assistive technology who needs an equivalent, independently operable path through the core experience, focus on the unmet job created because visual hierarchy and gestures often encode meaning that is missing from semantic labels, focus order, audio feedback, or alternative input, and ship an equivalent task path built around semantic structure, predictable focus, adjustable presentation, multimodal feedback, and direct testing with disabled users before expanding the audience or feature surface.
Preview the reasoning
Three moves to make the answer concrete.
Choose the user
- Prioritize one coherent interaction model
- Compare at least one credible alternative.
Find the unmet job
- Explain what you deliberately leave out
- Compare at least one credible alternative.
Measurement check
A metric is useful only when it changes the decision.
- North star
- independent core tasks completedMeasures the repeated user or customer outcome, not mere feature activity.
- Diagnostic
- time, error, and navigation-recovery rateExplains whether quality and the critical journey improved for the intended segment.
- Guardrail
- accessibility blockers, parity gaps, and assistive-technology satisfactionMakes the principal downside observable: passing an automated checklist while the real task remains slower, confusing, or impossible without assistance.
Interviewer pressure test
Do not stop when the first answer sounds polished.
- Why prioritize a person using assistive technology who needs an equivalent, independently operable path through the core experience, and who did you explicitly defer?
- How would your answer change with two weeks, three engineers, or a tenfold scale increase?
- What is the strongest rejected alternative and when would it win?
Turn reading into retrieval