← Google Interview Insights

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

SeniorPrefer not to say
Jun 2026

Summary

Google PM interview, one question about accessibility that sounds deceptively simple but has a lot of surface area if you're not careful about scoping.

Questions Asked (1)

Q1

Name a product with poor accessibility. How would you improve it, and how would you measure whether your improvements worked?

Product Sense & IdeationProduct Analytics & MetricsA/B Testing & Experimentation
Author's notes

I picked a product fast without really thinking through whether I could actually say something interesting about it.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a widely-used product with clear, well-documented accessibility issues (e.g., a popular app or website) and briefly explain why it matters. Then, outline a prioritized set of improvements based on accessibility guidelines (WCAG) and user impact, and propose a measurement plan that combines quantitative metrics (e.g., task success rate, time on task) and qualitative feedback (e.g., user interviews) with A/B testing where feasible.

Pro tip: Tie accessibility improvements to business metrics like user retention or conversion to show you understand the broader impact, and mention that accessibility benefits all users, not just those with disabilities.

1. Select a product and identify accessibility issues

Choose a product you know well (e.g., a popular e-commerce site or social media app) and describe 2-3 specific accessibility problems, such as lack of screen reader support, poor color contrast, or keyboard navigation issues.

2. Prioritize improvements based on impact and effort

Explain how you would prioritize fixes using a framework like RICE or impact/effort matrix, focusing on issues that affect the most users or are critical for basic functionality.

3. Propose concrete improvements

Detail specific changes, such as adding ARIA labels, improving color contrast to meet WCAG AA standards, enabling full keyboard navigation, and providing text alternatives for images.

4. Define success metrics

Identify quantitative metrics (e.g., task completion rate, error rate, time on task for users with disabilities) and qualitative measures (e.g., user satisfaction surveys, usability testing with assistive technology users).

5. Design measurement and experimentation plan

Describe how you would measure the impact, such as A/B testing with a control group, pre/post analysis, or longitudinal studies, and how you would ensure statistical significance and avoid bias.

Key Points to Mention

  • WCAG guidelines and compliance levels (A, AA, AAA)
  • Assistive technologies like screen readers, voice control, and switch devices
  • Inclusive design principles and universal design
  • Quantitative metrics: task success rate, error rate, time on task, SUS score
  • Qualitative methods: user interviews, usability testing with diverse users
  • A/B testing considerations: sample size, segmentation, ethical concerns

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