· PM Editorial · Product Sense · 5 min read
Design a Product for Senior Citizens: Interview Scoring Rubric
A calibration rubric interviewers actually use to score 'design a product for senior citizens' answers, with dimension-by-dimension breakdowns of great vs. good vs. poor responses.
Updated July 2026
“Design a product for senior citizens” is one of the most recurring product sense prompts at Big Tech and growth-stage companies, precisely because it’s easy to answer shallowly and hard to answer well. Most candidates default to “big buttons and large fonts,” which signals a surface-level read of an aging user rather than a structured investigation. This article breaks down the rubric interviewers actually use to score this prompt, what separates a great answer from a good one, and the calibration mistakes that sink otherwise strong candidates.
Why This Prompt Keeps Showing Up
Interviewers like “design for senior citizens” because it forces candidates to reason about a user segment they likely don’t belong to. That gap exposes whether a candidate defaults to stereotypes (frail, tech-illiterate, needs big buttons) or does real segmentation work (varying tech fluency, varying physical constraints, varying motivations for using a product at all). It also tests whether a candidate can translate a broad demographic into a specific, falsifiable persona and a specific, falsifiable problem.
The Scoring Rubric
Most panels score across five dimensions. Each is worth roughly equal weight, though clarifying-question quality is often used as a gating filter before the rest of the rubric is applied.
| Dimension | What It Measures | Weight |
|---|---|---|
| Clarifying questions | Does the candidate segment “senior citizens” before designing? | 20% |
| Problem framing | Is the target problem specific, evidence-backed, and prioritized? | 20% |
| Solution design | Does the solution map directly to the stated problem, not a generic feature list? | 20% |
| Prioritization & tradeoffs | Can the candidate cut scope and defend the cut? | 20% |
| Success metrics | Are the metrics measurable, leading, and tied to the original problem? | 20% |
Dimension 1: Clarifying Questions
Great candidates immediately push back on the vagueness of “senior citizens” as a segment. They ask questions like: What age range — 60-70 “young-old” digital adopters, or 80+ users with declining vision and mobility? What’s the product category — health, social, financial, shopping? Is this a net-new product or a redesign of an existing one for accessibility?
Good candidates ask one or two clarifying questions but move to solutioning quickly, often settling for a single persona without testing whether it’s the right one.
Poor candidates skip clarifying questions almost entirely and open with “seniors need bigger buttons and simpler navigation,” treating the entire demographic as a monolith.
Dimension 2: Problem Framing
The single biggest differentiator on this prompt is whether the candidate identifies a felt problem versus an assumed one. Great answers surface a problem like “socially isolated seniors want to video call grandchildren but abandon the flow after one failed attempt because error recovery is unclear,” which is specific, observable, and testable. Good answers land on something reasonable but generic, like “seniors struggle with too many steps in onboarding.” Poor answers state the demographic’s supposed limitation as the problem itself — “seniors have poor eyesight and dexterity” — without ever connecting it to a task the user is trying to accomplish.
Dimension 3: Solution Design
Once the problem is framed, the solution should read as a direct answer to that problem, not a wish list. A great candidate proposes 2-3 concrete features, explains the mechanism by which each solves the stated problem, and explicitly rejects features that don’t serve it. A common trap here is scope creep: candidates who list voice control, larger fonts, simplified navigation, emergency contacts, and medication reminders all in one breath are demonstrating breadth, not judgment.
Dimension 4: Prioritization and Tradeoffs
This is where senior-level signal separates from junior signal. Interviewers want to see a candidate rank their own ideas and explain why one ships in v1 and the rest wait. A frequent mistake: candidates propose a strong prioritization framework (like RICE or impact/effort) but never actually apply it to their own list, treating the framework as a checkbox rather than a decision tool.
Dimension 5: Success Metrics
Great answers propose a primary metric that would move in weeks, not quarters, and directly reflects the original problem: e.g., “successful call completion rate” for the video-calling example, tracked against the “abandon after one failed attempt” story. Poor answers reach for vanity metrics like DAU or app store rating, which are lagging, unspecific, and disconnected from the problem statement.
Common Mistakes That Sink Strong Candidates
- Treating “senior citizens” as an undifferentiated block instead of segmenting by tech fluency, health status, and living situation.
- Anchoring on accessibility features (font size, contrast) as the entire solution, ignoring emotional and social needs.
- Skipping a clear problem statement and jumping straight into a feature list.
- Proposing metrics that can’t move within the timeframe of a product cycle.
- Failing to prioritize — presenting every idea as equally important.
Calibration: Great vs. Good vs. Poor
| Signal | Great | Good | Poor |
|---|---|---|---|
| Segmentation | 2-3 sub-personas with distinct needs | One persona, reasonable but shallow | No segmentation, one stereotype |
| Problem | Specific, evidence-backed, testable | Plausible but generic | Restates demographic trait as problem |
| Solution | 2-3 features tightly scoped to problem | Broader list, weak prioritization | Feature dump, no rationale |
| Tradeoffs | Explicit cut with reasoning | Framework mentioned, not applied | No tradeoffs discussed |
| Metrics | Leading, specific, tied to problem | Reasonable but generic | Vanity metrics (DAU, ratings) |
How to Prepare
Practice segmenting broad demographics before you get to this exact prompt — the same rubric applies to “design for new parents,” “design for college students,” or any age/role-based prompt. Build a repeatable structure: clarify, segment, pick one problem, propose 2-3 solutions, prioritize with a stated tradeoff, define one leading metric. Interviewers reward structure and judgment far more than cleverness.
For a deeper walkthrough of scoring rubrics across dozens of recurring product sense prompts, see The 100x Product Manager Interview Playbook (Amazon: https://www.amazon.com/dp/B0DBC1FQWH?tag=sirjohnnymai-20), which includes calibrated sample answers and interviewer notes for this exact question type.