Skip to content
RED SAGSkills
mediumPrompt Engineer interview question

When would you split a task into a chain of prompts instead of one large prompt? What are the trade-offs?

What the interviewer wants to hear

  • Chain when task has distinct steps or skills
  • Easier to test, debug and improve each step
  • Structured handoffs between steps
  • Trade-offs: more latency, more cost, error propagation
  • Single prompt is simpler when it performs well enough

Model answer

I split a task when it has clearly different steps, like extracting facts, then checking them against rules, then writing a message. Each smaller prompt can focus on one job, which usually improves quality. It is also easier to evaluate and debug: if the final email is wrong, I can see whether extraction or drafting failed. I pass structured outputs between steps so they can be validated in code, and some steps might not even need a model. The trade-offs are more calls, so more latency and cost, and errors from early steps flow into later ones, so the first steps need to be reliable. If a single prompt already meets the quality bar on the eval set, I keep it, because simple systems are easier to maintain.

Can you answer it under time pressure?

Take a timed medium round and get scored on every answer.

Start mock interview

More medium Prompt Engineer questions