Prompt Engineering Interview Questions
Prompt anatomy, few-shot design, structured output and prompt evaluation.
What makes a good prompt?
A clear role, a specific task, the context the model needs, the output format, and constraints. Each part removes a guess the model would otherwise make.
Key Points:
- Show an example of the output you want.
When should you use few-shot prompting?
When the task has a specific style, label set or format that is easier to show than describe. Use diverse, representative examples.
Key Points:
- Too many similar examples can bias the output.
How do you evaluate a prompt?
Build a small test set with expected outputs, run prompt versions against it, and score with exact-match, rubric or LLM-as-judge checks. Track regressions when you change the prompt.
Key Points:
- Version prompts like code.