Figma — Design Platform & Growth — Product Case Questions
Role context: Data Scientist, embedded across Product / Marketing / Finance / Platform · Est. study time: 60 min · 5 questions
How to approach product cases here
Every case is one move in the same decision chain: understand the business, break it into a data problem, choose the metric or method, name the bias and the trade-off, land on a decision and an action. A strong answer walks that chain out loud and survives the follow-ups.
Four things make Figma cases distinctive. Get these right and most questions become straightforward.
1. The money is expansion, not acquisition. Net dollar retention is 139%, so existing customers spend 1.39x what they did a year ago before a single new logo. When you are asked about growth, the default answer is about getting more people inside an existing org onto seats, not about acquiring new companies.
2. Free users are the pipeline, not a cost. Viewers and commenters pay nothing, but every paid seat starts as somebody who was invited to a file. Figma's own research says teams that collaborate in month 1 are 1.75x more likely to retain and 6.5x more likely to become a customer. Any proposal that "cleans up" the free tier has to be priced against that loop.
3. The buyer is not the user. An admin approves seats. You cannot A/B test a procurement decision, so you push measurement onto the leading indicator (edit intent) and use quasi-experimental methods for the contract-level question.
4. Averages lie here, in two specific ways. There are about 690,000 paid customers but only 1,525 above $100k ARR, so a blended average describes nobody. And a handful of enormous orgs can move a companywide rate by themselves, without any behavior changing. Whenever a rate moves, ask whether behavior changed or the mix changed. That reflex is worth a lot of points.
The traps to watch for: reading a 2% lift as noise (at this scale it is often real and valuable, if it was powered), reading an observational multiple as causal (the 6.5x is the classic), and reading a two-week test for an effect that lands in six months.
This role is a generalist embedded across Product, Marketing, Finance, and Platform, so it gets probed broadly. The five below cover all five shapes: diagnose, measure success, launch or not, measure impact without an experiment, and forecasting. Nothing is skipped, because a role this broad does not let you skip anything. If you only have time for two, do bc3 and bc4: the free-versus-paid trade-off and the causal read on collaboration are the two questions that are unmistakably about Figma.