← Better.com Interview Insights

Better.com·Product Manager·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Jun 2026

Summary

Interviewed at Better.com for what seemed like a product or systems-adjacent role. One question, pretty open-ended, and I left not totally sure if I nailed it or completely missed the point.

Questions Asked (1)

Q1

How would you design a web browser that still works effectively when the internet is unavailable half the time?

System DesignTechnical Trade-offsProduct Sense & Ideation
Author's notes

My first instinct was to just talk about caching and I kind of ran with that for too long.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the user segments and use cases, then frame the problem as a product design challenge that balances offline functionality with seamless online experiences. Propose a solution that prioritizes core browsing tasks offline, leverages caching and sync, and includes clear user communication about connectivity status.

Pro tip: Tie your answer back to Better.com's mission of simplifying the home buying process—emphasize how offline browsing could support users with unreliable internet, such as those in rural areas or during home tours, and how it aligns with the company's customer-centric approach.

1. Clarify Requirements and User Needs

Ask questions to understand the target users, their browsing habits, and the specific scenarios where internet is unavailable half the time. Identify critical tasks (e.g., accessing saved documents, filling forms) that must work offline.

2. Define Core Offline Capabilities

Prioritize features that can function offline, such as viewing cached pages, reading saved articles, and accessing previously loaded web apps. Consider using service workers and local storage to enable these.

3. Design Seamless Online-Offline Transitions

Implement mechanisms to detect connectivity changes and automatically switch modes. Use background sync to update content when online and queue user actions (e.g., form submissions) for later.

4. Address Technical Trade-offs

Discuss trade-offs like storage limits, cache freshness, and security. Propose strategies like intelligent caching algorithms, compression, and user controls for cache management.

5. Communicate Status and Manage Expectations

Design clear UI indicators for offline mode and pending actions. Educate users on what works offline and how to manage offline content.

Key Points to Mention

  • Progressive Web App (PWA) technologies like service workers and IndexedDB for offline caching
  • Prioritization of user tasks based on frequency and criticality (e.g., accessing saved homes, mortgage documents)
  • Background sync and conflict resolution for actions taken offline
  • Clear user interface indicators for connectivity status and offline capabilities
  • Data synchronization strategies to ensure consistency when reconnecting
  • Metrics to measure success, such as offline task completion rate and user satisfaction

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