When would you use zero-shot versus few-shot prompting?

Uses examples to clarify ambiguous task behavior while accounting for token cost, bias, maintenance, and evaluation evidence.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Zero-shot prompting gives the task and constraints without examples. Few-shot prompting adds representative input-output examples. I start zero-shot when the task is simple and well specified, then add a small set of examples when they improve ambiguous classification, tone, edge-case handling, or output conventions in evaluation.

Full answer below

Practice focus

Whether examples are chosen for a concrete behavioral need instead of added as a ritual.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Few-shot examples are useful when they teach a boundary the instruction alone does not communicate reliably.
Zero-shot prompting gives the task and constraints without examples. Few-shot prompting adds representative input-output examples. I start zero-shot when the task is simple and well specified, then add a small set of examples when they improve ambiguous classification, tone, edge-case handling, or output conventions in evaluation.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
The examples need to cover meaningful distinctions, not repeat the easiest case. For a ticket router, I might include a request that looks like billing but is actually account access, plus an explicit unknown case. I keep examples consistent with the schema and avoid leaking real customer data. More examples consume context and can bias the model toward their wording or class distribution.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Adding examples without measuring whether they improve the task.
Using only ideal happy-path examples.
Including sensitive production inputs verbatim.
Assuming more examples always improve generalization.

When would you use zero-shot versus few-shot prompting?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Tech stacks

Skill areas

Human editorial direction

Was this drill useful?

Found this answer useful?