How would you explain the difference between task success and model quality?

Instruction: Describe the difference between judging the model itself and judging whether the user task was completed.

Context: Checks whether the candidate can explain the core concept clearly and connect it to real production decisions. Describe the difference between judging the model itself and judging whether the user task was completed.

Updated

Example Answer

I would distinguish component quality from the completed user workflow. Model quality can include factual accuracy, instruction following, calibration and proposed tool arguments under specified conditions; it is broader than prose quality alone. Task success asks whether the whole system reached the authorized user outcome. The measures overlap, but they are not interchangeable.

A model can produce fluent, highly rated text and still fail the task because it used the wrong tool, skipped a required step, gave an answer too late, or created work the user then had to clean up. The reverse can also happen: the wording is imperfect, but the user still reaches the right outcome quickly.

That is why I separate model metrics from workflow metrics. Model quality helps me understand how the system reasons and responds. Task success tells me whether the product is actually useful. If I collapse them into one number, I usually end up overvaluing polished output and undervaluing operational correctness.

Common Poor Answer

A weak answer is saying task success is just model quality plus a few product metrics. That misses the fact that workflow completion and output quality can move in different directions.

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

Related Questions