GeneralBackendFrontendTable-stakes
MVC
Also written as Model-View-Controller
A pattern for organizing an application into three parts: the Model (data), the View (what the user sees), and the Controller (the logic connecting them). Used by frameworks like Rails, Django, and Spring MVC.
Think of it like
Like a restaurant split into the pantry (Model), the dining room (View), and the waiter relaying orders between them (Controller) — each part has one job.
Junior or senior?
Junior sounds like
Name-drops MVC without depth.
Senior sounds like
Can point to a specific piece of logic in an app they built and explain why it belonged in the controller versus the model.
Ask them
“In an MVC app you built, what's an example of logic you had to decide whether it belonged in the model or the controller?”