What is a ViewModel?
PICTURE THIS: DATABASE INDEX
Simple meaning
A ViewModel is a shape built for a screen, not necessarily a database entity.
WHY — MVC instead of guessing?
Why interviewers care about MVC:
who only read docs from people who shipped.
and tied to .NET MVC 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:
- 1A ViewModel is a
shape built for a screen, not necessarily a database entity.
- 2It prevents overposting and
keeps views simple.
- 3I map entities to
ViewModels explicitly.
- 4Give an example
One tiny concrete case you can say aloud.
- 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
A ViewModel is a shape built for a screen, not necessarily a database entity. It prevents overposting and keeps views simple.