Product design question
Figma Weave needs to grow beyond early adopters without losing the depth that power users value. How would you choose the first adjacent user segment to target, what evidence would you use to justify that choice, and what product changes would you ship in the first two quarters to make node-based workflows more approachable for that segment without capping advanced use cases?
- Figma
- Product design
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests choosing the right adjacent user segment for a power-user-oriented node-based tool, justifying the choice with evidence, and defining a two-quarter plan that broadens reach without diluting depth.
How to approach it
- Identify plausible segments: junior designers wanting node-based power without the learning curve, or marketers wanting on-brand variations without touching the node graph.
- Use evidence to choose: analyze where early adopters hit friction and abandon, and interview lapsed trial users to see which segment's needs align with existing gaps.
- Pick the segment with shortest distance to value, likely designers already inside Figma's ecosystem, since they need guided entry points, not a new product surface.
- Quarter one: ship guided templates that hide the node graph by default while remaining fully editable underneath, so beginners get value without power users losing flexibility.
- Quarter two: ship contextual education based on where quarter-one users still get stuck, refined with real usage data.
- Protect advanced use cases by keeping the full node graph accessible and unchanged for existing power users throughout both quarters.
What a strong answer includes
- Justifies the segment choice with concrete evidence, abandonment points and exit interviews, not intuition about who should adopt next.
- Picks a segment with the shortest distance to value, already inside the Figma ecosystem, over one needing a new go-to-market motion.
- Ships a progressive-disclosure approach, hidden graph by default with full access preserved, protecting power users while broadening entry.
Common mistakes
- Picking an adjacent segment based on market size alone without evidence of what's blocking them today.
- Building a simplified interface that removes access to the node graph, alienating existing power users.
- Committing to a fixed two-quarter plan without incorporating what's learned from quarter one.
Likely follow-up questions
- How would you validate this segment choice before committing two quarters of work?
- What would you do if power users start using the simplified templates and lose depth?
More product design questions
- Assume users say Figma Weave’s multi-step creation pipeline feels too rigid for experts and too complex for newer users. How would you diagnose where the workflow is breaking down, and how would you decide whether the next investment should go into foundational workflow improvements versus user-facing UX changes?Figma · Product design · Hard
- Teams need to modify and extend shared workflows in Figma Weave without breaking brand consistency or creative intent. How would you design the abstraction model, such as templates, locked steps, editable parameters, permissions, previews, and versioning, so that teams get flexibility where it matters while preserving reliable, on-brand output?Figma · Product design · Hard
- Pick a core collaborative workflow in Figma, such as co-editing, commenting, or design handoff. How would you identify the highest-value user needs across different personas, simplify the workflow end-to-end, and decide what 'high craft' should mean in the final experience?Figma · Product design · Hard
- Design a TV for a car.Google · Product design · Hard
- Design a refrigerator for the blind.Google · Product design · Hard
- Redesign Twitter for eCommerce.Shopify · Product design · Hard
More questions from Figma
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop