When should you raise temperature versus lower it?
PICTURE THIS: DATABASE INDEX
Simple meaning
Lower it for extraction, classification, SQL, and customer-support facts.
WHY — Temperature instead of guessing?
Why interviewers care about Temperature:
contrast on Temperature, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Lower it for extraction,
classification, SQL, and customer-support facts.
- 2Raise it for brainstorming
and varied copy.
- 3Keep a separate setting
from top-p so you can tune diversity without destroying format compliance.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Lower it for extraction, classification, SQL, and customer-support facts. Raise it for brainstorming and varied copy.