Make Chrome on Phones and Tablets a Better Reader for Long Articles, PDFs and E-Books

Quick Overview

A Google product manager question about improving how people read long articles, PDFs and books in Chrome on phones and tablets. It tests choosing a reader segment, finding small-screen pain points, prioritizing features against publisher and ad trade-offs, and setting reading-focused success metrics.

Make Chrome on Phones and Tablets a Better Reader for Long Articles, PDFs and E-Books

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager for Chrome on phones and tablets. More and more people use the mobile browser to read long material: articles and blog posts, PDF documents such as papers, reports and manuals, and books or book-length text. How would you improve the reading experience for them? Explain which readers and which kinds of content you would focus on, what gets in their way today, what you would build first and how you would know it worked. ```hint Same reader, three documents Picture one person opening a news article, a two-column PDF and a long book chapter on a phone. Where does each one break down, and which breakdown matters most for the readers you choose? ``` ### Clarifying Questions - Which outcome matters most to the team: more long reading done in Chrome, fewer people leaving Chrome for a separate reader app, or reader satisfaction? - Are books in scope as files a user opens in the browser (for example an EPUB download), or only book-length content that web pages serve? - Can the solution change how publishers' pages look, for example by hiding ads in a reading view, given that ads fund much of the web? - Should the first version ship on Android and iOS together, or may it start on one platform? ### What a Strong Answer Covers - A stated goal and a reasoned choice of reader segment and content type - Pain points specific to small screens and to each format, such as page clutter and interruptions, fixed PDF layouts, and losing your place across long sessions - Prioritized solutions mapped to those pain points, with effort and trade-offs, including the effect on publishers and ad revenue - Success metrics that capture finished, comfortable reading rather than raw time spent, with guardrails - Risks such as publisher pushback, accessibility, privacy of reading data and platform differences ### Follow-up Questions - A reading view raises how often people finish articles but cuts publishers' ad impressions. How do you decide whether to ship it, and in what form? - Longer reading sessions could mean engaged readers or readers who keep losing their place. How would you tell them apart in the data? - What would you change for a tablet in landscape with a keyboard compared with a phone held in one hand?

Overview: A Google product manager question about improving how people read long articles, PDFs and books in Chrome on phones and tablets. It tests choosing a reader segment, finding small-screen pain points, prioritizing features against publisher and ad trade-offs, and setting reading-focused success metrics.

Google logo
Google
Aug 7, 2024
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager for Chrome on phones and tablets. More and more people use the mobile browser to read long material: articles and blog posts, PDF documents such as papers, reports and manuals, and books or book-length text. How would you improve the reading experience for them?

Explain which readers and which kinds of content you would focus on, what gets in their way today, what you would build first and how you would know it worked.

Clarifying Questions Guidance

  • Which outcome matters most to the team: more long reading done in Chrome, fewer people leaving Chrome for a separate reader app, or reader satisfaction?
  • Are books in scope as files a user opens in the browser (for example an EPUB download), or only book-length content that web pages serve?
  • Can the solution change how publishers' pages look, for example by hiding ads in a reading view, given that ads fund much of the web?
  • Should the first version ship on Android and iOS together, or may it start on one platform?

What a Strong Answer Covers Guidance

  • A stated goal and a reasoned choice of reader segment and content type
  • Pain points specific to small screens and to each format, such as page clutter and interruptions, fixed PDF layouts, and losing your place across long sessions
  • Prioritized solutions mapped to those pain points, with effort and trade-offs, including the effect on publishers and ad revenue
  • Success metrics that capture finished, comfortable reading rather than raw time spent, with guardrails
  • Risks such as publisher pushback, accessibility, privacy of reading data and platform differences

Follow-up Questions Guidance

  • A reading view raises how often people finish articles but cuts publishers' ad impressions. How do you decide whether to ship it, and in what form?
  • Longer reading sessions could mean engaged readers or readers who keep losing their place. How would you tell them apart in the data?
  • What would you change for a tablet in landscape with a keyboard compared with a phone held in one hand?