Reduce YouTube App Battery Drain on Phones With No Visible Product Changes

Quick Overview

A Google product manager improvement prompt about lowering the battery drain of the YouTube mobile app while keeping its interface and user experience unchanged. It tests whether you can break energy use into components the app controls, prioritize invisible engineering fixes, and measure savings against video quality and start-up guardrails.

Reduce YouTube App Battery Drain on Phones With No Visible Product Changes

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager for the YouTube mobile app and have been asked to make the app use less battery, with one constraint: you may not change the user interface or the user experience. How would you do it? Explain why battery use matters for YouTube, which users and usage patterns you would focus on, what you would change, how you would prioritize those changes, and how you would know they worked. ```hint Follow the energy Break the app's battery use into the parts of the phone it keeps busy, such as the screen, video decoding, the cellular and Wi-Fi radio, the processor and background work, and ask which of those the app could make cheaper without the viewer seeing any difference. ``` ### Clarifying Questions - Does the constraint rule out only visible interface changes, or also changes a viewer might notice, such as a slightly different automatic resolution on a small screen or a slower video start? - Should I focus on drain during playback, drain in the background when the app is not on screen, or both, and on Android, iOS or both? - What prompted the goal: battery complaints in reviews, phones flagging YouTube as a heavy battery user, or a push for longer viewing sessions? ### What a Strong Answer Covers - Why battery life matters to YouTube's goals, and a clear reading of the "no UI/UX change" constraint - Segmentation by device tier, usage mode (long-form, Shorts, background listening) and network, with a reasoned focus - A breakdown of where the energy goes, with solutions mapped to the components the app controls (decoding, networking, rendering, background work) - Prioritization by energy saved, reach, effort and the risk of any perceptible change - Success metrics such as energy per hour of watch time, with quality and start-up guardrails and an experiment-based rollout ### Follow-up Questions - If the change that saves the most battery also adds a fraction of a second to video start time, how would you decide whether to ship it? - How would you measure battery impact in the field, given that phones report per-app energy use only coarsely? - Which parts of your plan change on iOS, where the operating system limits background work more strictly?

Overview: A Google product manager improvement prompt about lowering the battery drain of the YouTube mobile app while keeping its interface and user experience unchanged. It tests whether you can break energy use into components the app controls, prioritize invisible engineering fixes, and measure savings against video quality and start-up guardrails.

Google logo
Google
May 14, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager for the YouTube mobile app and have been asked to make the app use less battery, with one constraint: you may not change the user interface or the user experience. How would you do it?

Explain why battery use matters for YouTube, which users and usage patterns you would focus on, what you would change, how you would prioritize those changes, and how you would know they worked.

Clarifying Questions Guidance

  • Does the constraint rule out only visible interface changes, or also changes a viewer might notice, such as a slightly different automatic resolution on a small screen or a slower video start?
  • Should I focus on drain during playback, drain in the background when the app is not on screen, or both, and on Android, iOS or both?
  • What prompted the goal: battery complaints in reviews, phones flagging YouTube as a heavy battery user, or a push for longer viewing sessions?

What a Strong Answer Covers Guidance

  • Why battery life matters to YouTube's goals, and a clear reading of the "no UI/UX change" constraint
  • Segmentation by device tier, usage mode (long-form, Shorts, background listening) and network, with a reasoned focus
  • A breakdown of where the energy goes, with solutions mapped to the components the app controls (decoding, networking, rendering, background work)
  • Prioritization by energy saved, reach, effort and the risk of any perceptible change
  • Success metrics such as energy per hour of watch time, with quality and start-up guardrails and an experiment-based rollout

Follow-up Questions Guidance

  • If the change that saves the most battery also adds a fraction of a second to video start time, how would you decide whether to ship it?
  • How would you measure battery impact in the field, given that phones report per-app energy use only coarsely?
  • Which parts of your plan change on iOS, where the operating system limits background work more strictly?