Concept guide · Prompting and context engineering
How do you evaluate a prompt change?
A slower explanation for when the short interview answer is not enough. Start with the intuition, then connect it to the technical idea and the way an interviewer expects you to reason about it.
ML area
Generative AI → Prompting and context engineering
Interview format
Core · Scenario
Question
GENAI-025
Start with the idea
In simple terms
This question is about How do you evaluate a prompt change. In a Generative AI system, connect the idea to the model, context, retrieval, tool, or user experience involved instead of explaining it as an isolated definition.
Make it concrete
Imagine this inside a document assistant or agent: the system receives a user request, selects the relevant context or action, and must produce a useful result without inventing facts or exceeding its permissions.
Build the answer
How to approach it
- 1Name the role this concept plays in a Generative AI application.
- 2Explain the main trade-off or failure mode an engineer must control.
- 3State how you would test it with a representative task and production constraint.
Go one level deeper
The technical explanation
Keep a versioned test set, run old and new prompts on the same cases, score task quality and failure types, repeat stochastic tasks, and compare cost and latency. Hold out some cases for confirmation and inspect regressions rather than accepting one impressive answer as evidence. To reason about this in a real Generative AI system, identify where the component sits in the request path, what can fail before and after it, and which quality, latency, cost, and safety signals would tell you whether it is working.
Say this in the interview
Keep a versioned test set, run old and new prompts on the same cases, score task quality and failure types, repeat stochastic tasks, and compare cost and latency. Hold out some cases for confirmation and inspect regressions rather than accepting one impressive answer as evidence.
Keep preparing