“If you were an animal, what would you be and why?” “If you were a tree, what tree?” “What superpower would you choose?” “What would your last meal be?” These questions occupy a strange archetype in the interview canon. They are not technical, not behavioral in the STAR-framework sense, not designed to test specific job-related skills. They are the meta-questions, asked to provoke a candidate into volunteering some piece of self-characterization that the interviewer can score on a vague rubric of “did this answer reveal anything interesting about how this person thinks?”
Some interviewers swear by them. Some companies have explicitly retired them. Most candidates dread them, partly because they are unpredictable and partly because no preparation framework feels appropriate. Understanding what the questions actually test is the only useful preparation.
The archetype
The questions in this family share four properties:
- No factually correct answer. The candidate cannot study for them.
- Apparent triviality. The surface question is whimsical, often disarming.
- Required justification. The “why” is more important than the “what”.
- Self-characterization invited. The answer is supposed to reveal something about the candidate’s values, personality, or thinking style.
The classic examples: animal, tree, superpower, song, last meal, dinner-party guest, cereal-box character, pirate name. Some interviewers ask milder versions (“what’s something you’re passionate about outside work?”); others ask harder ones (“what’s a hill you’d die on professionally?”). The category is broad and the specific question varies, but the underlying test is the same.
What interviewers are looking for
The honest answer: most interviewers who use these questions are not entirely sure what they are looking for. The questions are inherited from earlier hiring traditions, and many interviewers ask them out of habit rather than according to a rubric. Where there is a rubric, it tends to be:
- Composure under unexpected questions. Can the candidate engage with the question without flinching, refusing, or asking for time?
- Self-awareness. Does the answer reveal that the candidate has thought about themselves in a coherent way?
- Communication. Can they justify their answer in 30–60 seconds with structure rather than rambling?
- Cultural fit. Does the answer match the kind of personality the interviewer thinks works well on this team?
The fourth criterion is the one that has caused the format to fall out of favor at large tech companies — it is a poorly-defined proxy for demographic and personality preferences that has been shown to hurt diversity outcomes when not anchored in a structured rubric.
Why some interviewers love them
The case for these questions, articulated by the interviewers who still use them: they are one of the few moments in a structured interview when the candidate has to think on their feet about something not pre-rehearsed. Behavioral questions can be prepared. Coding questions can be prepared. The animal question, in some sense, cannot be — and that unscripted moment is exactly when the candidate’s actual personality leaks through the interview armor.
Whether this is true is contested. Some research suggests that candidates simply prepare different scripts for these questions (“I’d be an octopus because I value adaptability”). Other research suggests that the unprepared moment does reveal something — but that what it reveals is more about social comfort with unexpected questions than about job-relevant traits.
Why other interviewers retired them
The case against, articulated by hiring leaders at most large tech companies in 2026: these questions are unstructured, hard to score consistently, vulnerable to interviewer bias, and not predictive of job performance. Google’s post-2013 retreat from brainteasers also pushed against the broader category of “questions that test something other than job-relevant skills”. Most FAANG companies have either retired these questions outright or pushed them out of formal scoring rubrics.
The other reason: candidates universally hate them. Forums and Glassdoor are full of complaints about being asked “what tree would you be?” in a coding interview. The candidate signal — “this company has unserious hiring practices” — is the cost of asking, and the benefit (an unscripted moment) is increasingly seen as not worth it.
Where the format survives
- Smaller startups. Founders who run their own interviews often ask these questions because they value the “vibe check” element and have not adopted structured rubrics.
- Some PM and design interviews. Where personality and creative thinking are job-relevant, these questions appear more often.
- Sales and customer-facing roles. Where the candidate’s social presence is part of the job, the unscripted moment is a more defensible test.
- Some old-line investment banks. A subset of senior bankers still asks these questions out of tradition; the questions have not been formally retired in many places.
- Senior leadership interviews. CEO, CTO, and similar roles sometimes include “soft” questions designed to probe values and worldview at depth that a STAR question cannot reach.
The format is essentially absent from new-grad and junior tech roles at FAANG, from most structured engineering loops, and from any company that has invested in interviewer training and rubric design.
How to handle them when they come up
The strong response has three components:
- Don’t refuse. “I find these questions strange” or “I don’t really know” is the failure mode. The interviewer interprets refusal as inability to engage with ambiguity, which is a worse signal than a mediocre answer.
- Pick a real answer. Not the “what would impress this interviewer” answer but a real answer that you can justify. Authentic answers, even unusual ones, score better than rehearsed-sounding clichés.
- Justify in 30–60 seconds. “I’d be an otter because I value playfulness, but I think the underlying skill of being able to dive deep on a problem when needed and surface for air with a clear answer matches how I work best.” Specific, structured, brief.
What not to do: spend 90+ seconds on the answer (over-explaining is its own bad signal); pick a bizarre answer designed to be memorable (interviewers see through this); refuse the premise (worst possible response).
The Beuys-tree story
One small piece of cultural history. Joseph Beuys, the German artist, gave an interview in 1982 in which he was asked “if you were a tree, what tree would you be?” — apparently an unusually whimsical question for an art interview. He paused, then said, “An oak. Because oaks are the slowest, and they last.” The answer became famous in art-criticism circles as a model of the genre — short, specific, justified, true to the person answering.
This is the model. The answer does not need to be impressive. It needs to be specific, justified, and true to the person giving it.
Common bad answers
- “I’d be an eagle because I’m a leader.” Reads as humblebrag and rehearsed-cliché.
- “I’d be a chameleon because I adapt.” Same problem; everyone says this.
- “I’d be a dolphin because they’re smart.” Bland; gives the interviewer nothing to score.
- “I haven’t really thought about it.” Refusal-disguised-as-honesty. Interpret it as failure to engage.
- “I’d be a unicorn because I’m one of a kind.” Trying too hard to be memorable; the artificiality shows.
Common good answers
The good answers vary because they are personal. Examples I have heard that landed well:
- “I’d be a crow. They’re problem-solvers, they remember faces, they can hold grudges. I think that captures my professional personality more accurately than I’d want to admit.”
- “I’d be an old apple tree in someone’s backyard. Productive, but useful in a slow, cumulative way rather than a flashy way. That matches how I think about my engineering career.”
- “My superpower would be the ability to ask one perfect question at the right moment. Not flying, not strength — the right question is more useful than either.”
What makes these work: they are specific, they reveal something true and slightly self-critical, they connect to professional identity, and they are short enough to land without rambling.
Is it asked in 2026?
Less than it used to be in tech, more than it used to be at smaller companies that have not adopted structured rubrics. Roughly half of senior tech interviews in 2026 do not include any version of this format; the other half include something at least adjacent. If you are interviewing at a large structured-process tech company, you can mostly skip preparing for it. If you are interviewing at a startup or a smaller firm, prepare a real answer to one or two of the standard variants.
Frequently Asked Questions
Is it OK to ask why they’re asking this?
Generally no. The interviewer expects you to engage with the question, and asking “why are you asking this” reads as deflection. Engage briefly, then move on.
How long should my answer be?
30–60 seconds. Long enough to justify the answer; short enough not to seem to be over-explaining.
Should I prepare an answer in advance?
Have a real answer in mind, but do not memorize a script. Memorized answers read as memorized; specific answers with personal justification read as authentic.
Are these questions still asked at FAANG?
Rarely in the formal scoring rubric. Sometimes informally, especially during “fit chat” segments at the end of structured rounds. Mostly extinct in new-grad and junior FAANG interviews.
Should I refuse to answer?
No. Refusing is the worst signal. Engage briefly, give a real answer, and move on. Even a weak answer is a better signal than a refusal.