In what order does DRF run serializer validation?
PICTURE THIS: DJANGO MVT
Simple meaning
to_internal_value runs field-level to_internal_value, then field validators, then validate_<field>, then serializer.validate.
WHY — DRF instead of guessing?
Why interviewers care about DRF:
who only read docs from people who shipped.
and tied to Python work.
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:
- 1to_internal_value runs field-level to_internal_value,
then field validators, then validate_<field>, then serializer.validate.
- 2UniqueValidator and UniqueTogetherValidator run
as serializer-level validators.
- 3Overriding create() does not
replace this pipeline
- 4invalid data never reaches
save() if is_valid() is used correctly.
- 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
to_internal_value runs field-level to_internal_value, then field validators, then validate_<field>, then serializer.validate. UniqueValidator and UniqueTogetherValidator run as serializer-level validators.