Web browser for 7- to 14-year-olds: users, core needs and a prioritized feature set

Quick Overview

A product sense question asking a PM candidate to design a web browser for children aged 7 to 14. It tests how the candidate sets a goal, weighs the needs of children, parents and schools, handles a wide age range, prioritizes features, and defines success metrics and risks.

Web browser for 7- to 14-year-olds: users, core needs and a prioritized feature set

Company: Microsoft

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager asked to design a web browser for children between 7 and 14 years old. Decide what the product should achieve, choose who you are designing for first, identify their biggest problems, and propose a prioritized set of features along with how you would measure success. ```hint Separate who chooses from who browses Before picking features, work out who installs and configures the browser and who uses it every day, and how differently a 7-year-old and a 14-year-old use the web. ``` ### Clarifying Questions - Should one product cover the whole 7–14 range, or may the design treat younger and older children differently? - Which devices come first: a shared family computer or tablet, a school-issued laptop, or the child's own phone? - Is the main aim keeping children safe, helping them learn and do schoolwork online, or bringing more young users to the company's browser? - Is this a standalone product or a mode inside a browser the family already uses? ### What a Strong Answer Covers - A stated goal for the browser that serves both the children and the adults responsible for them - Children, parents and schools compared as users and buyers, with a focus segment chosen and justified - How needs and acceptable limits change across the 7–14 range, and how the design reflects that - Pain points ranked and features prioritized with explicit criteria, weighing protection against the friction it adds to legitimate browsing - A success metric with guardrails for safety, privacy and continued use, plus the main risks, including how the product fails if children route around it ### Follow-up Questions - How would you keep a 13-year-old from simply switching to a regular browser, and should you try? - When the filter cannot tell whether a page is appropriate, should it block it, allow it or ask a parent, and how would you check that the choice works? - What would change if a school district, rather than parents, deployed the browser on student laptops?

Overview: A product sense question asking a PM candidate to design a web browser for children aged 7 to 14. It tests how the candidate sets a goal, weighs the needs of children, parents and schools, handles a wide age range, prioritizes features, and defines success metrics and risks.

Microsoft logo
Microsoft
Dec 15, 2023
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager asked to design a web browser for children between 7 and 14 years old. Decide what the product should achieve, choose who you are designing for first, identify their biggest problems, and propose a prioritized set of features along with how you would measure success.

Clarifying Questions Guidance

  • Should one product cover the whole 7–14 range, or may the design treat younger and older children differently?
  • Which devices come first: a shared family computer or tablet, a school-issued laptop, or the child's own phone?
  • Is the main aim keeping children safe, helping them learn and do schoolwork online, or bringing more young users to the company's browser?
  • Is this a standalone product or a mode inside a browser the family already uses?

What a Strong Answer Covers Guidance

  • A stated goal for the browser that serves both the children and the adults responsible for them
  • Children, parents and schools compared as users and buyers, with a focus segment chosen and justified
  • How needs and acceptable limits change across the 7–14 range, and how the design reflects that
  • Pain points ranked and features prioritized with explicit criteria, weighing protection against the friction it adds to legitimate browsing
  • A success metric with guardrails for safety, privacy and continued use, plus the main risks, including how the product fails if children route around it

Follow-up Questions Guidance

  • How would you keep a 13-year-old from simply switching to a regular browser, and should you try?
  • When the filter cannot tell whether a page is appropriate, should it block it, allow it or ask a parent, and how would you check that the choice works?
  • What would change if a school district, rather than parents, deployed the browser on student laptops?