When is a pie or donut chart appropriate?
Tests judgment of part-to-whole encoding. Answer: use for few categories with clear dominance, cite a share scenario like device traffic, and name angle-comparison difficulty and 3D distortion as pitfalls.
What's really being asked
This question probes your data visualization literacy and whether you understand how visual encodings map to human perception. Interviewers want to see that you know pie charts represent proportions through arc length and central angle, and that you can articulate when those encodings help rather than hinder comprehension.
The full answer
A great response starts by stating that pie and donut charts are appropriate only for simple part-to-whole relationships with very few categories, ideally two to five slices, and when approximate proportion is more important than precise comparison. Next, it provides a specific scenario such as an executive dashboard showing market share across three segments where one player dominates at roughly sixty percent, because the eye can immediately grasp a simple majority without reading exact values. Then it names two concrete pitfalls: first, that human vision is poor at comparing angles and curved areas, so adding many slices forces viewers into error-prone judgments; second, that 3D tilting, exploded slices, or excessive decoration distort the arc lengths and make proportions impossible to assess accurately. A bonus mention is that donut charts preserve the same arc-length encoding while freeing the center for a total label or icon.
The mistakes people make
Watch out for dogmatic claims that pie charts are never acceptable, which signals inflexibility, or the opposite extreme of recommending them for time-series trends, precise rankings, or datasets with more than seven categories. Another red flag is blaming colors rather than the angle encoding itself, or suggesting that 3D effects add visual interest without acknowledging the proportional distortion they introduce.
What usually comes next
The interviewer may ask what you would use instead for a twelve-category breakdown, pushing you toward treemaps, stacked bars, or simple tables. They might also ask whether the donut hole improves readability or just follows fashion, or how you would handle negative values and parts that exceed the whole.
A concrete example
Consider a quarterly business review slide showing customer acquisition channels: organic search at fifty-five percent, paid social at thirty percent, and referrals at fifteen percent. A pie chart works here because there are only three segments, the majority is instantly recognizable, and exact percentages can be labeled directly. If the designer instead used a 3D pie chart with the referral slice exploded, the perspective would make the fifteen percent slice appear nearly equal to the thirty percent slice, actively misleading the leadership team about channel performance.
Interview question
Which scenario best justifies using a pie or donut chart for an executive dashboard?
- a.Displaying three customer acquisition channels where organic search accounts for about 55% of the totalCorrect
- b.Comparing monthly website traffic from five sources to identify the exact rank order of each
- c.Showing how a quarterly budget divides among ten departments with roughly equal allocations
- d.Plotting year-over-year revenue changes for four product lines to highlight upward trends
Why? this is the answer
Pie charts are appropriate only for simple part-to-whole relationships with very few categories and a recognizable majority, making the three-channel scenario ideal. The ten-department budget is a tempting distractor because it is genuinely part-to-whole, but similar angles across ten slices force viewers into error-prone judgments that undermine the chart’s purpose.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
- #data visualization
- #analytics
- #charts
- #perception
- #communication
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on data visualization — each one lists the topics its interview covers.
See open roles