How do you keep controllers from becoming god classes?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
One action does one use case: bind, call a service, map to a view model, return.
WHY — Architecture instead of guessing?
Why interviewers care about Architecture:
question about Architecture.
trade-offs, and what you would actually do on a .NET MVC project - not buzzwords.
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:
- 1One action does one
use case: bind, call a service, map to a view model, return.
- 2Why it exists
Filters handle cross-cutting concerns.
- 3I split by area
or feature folder when a controller file grows past a screen.
- 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
One action does one use case: bind, call a service, map to a view model, return. Filters handle cross-cutting concerns.