← Google Interview Insights

Google·Product Manager·Onsite - Product Sense / Strategy·Intermediate

Intermediate
May 2026

Summary

Google PM interview, got hit with an accessibility-focused product design question. Pretty open-ended and I spent a lot of time second-guessing whether I was going deep enough on the user empathy side versus the technical constraints.

Questions Asked (1)

Q1

How would you design an ATM specifically for blind users?

Product Sense & IdeationAdaptability & Ambiguity
Author's notes

I jumped straight into listing features and had to pull myself back.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the goal and constraints of the ATM design, then focus on the needs of blind users through empathy and accessibility principles. Structure your answer by outlining key design considerations, proposing specific features, and discussing trade-offs and success metrics.

Pro tip: Emphasize that accessibility features often benefit all users, and mention the importance of testing with actual blind users to validate assumptions.

1. Clarify and Define

Ask clarifying questions to understand the scope, such as the ATM's location, typical transactions, and whether it's a new design or an improvement. Define the primary goal: enabling blind users to independently and securely perform common ATM transactions.

2. Understand User Needs

Identify the key challenges blind users face with current ATMs, such as navigating touchscreens, reading screens, and locating card slots. Consider their needs for audio guidance, tactile feedback, and privacy.

3. Brainstorm Features

Propose specific design features that address the identified needs, such as audio instructions via headphones, tactile buttons with Braille, voice recognition, and haptic feedback. Prioritize features based on impact and feasibility.

4. Address Trade-offs and Constraints

Discuss potential challenges like cost, security, and usability for sighted users. Consider how to balance accessibility with other requirements, such as maintaining a familiar interface for all users.

5. Define Success Metrics

Outline how you would measure success, such as task completion rate, time to complete transactions, user satisfaction, and error rates among blind users. Mention the importance of iterative testing with real users.

Key Points to Mention

  • Audio guidance with headphone jack for privacy
  • Tactile buttons and Braille labels for keypad and functions
  • Haptic feedback to confirm actions
  • Voice recognition for hands-free operation
  • Compatibility with screen readers and mobile apps
  • Testing with blind users and accessibility experts

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.