BackendGeneral
Repository Pattern
A design pattern that puts a layer between an application's business logic and its data access code (database queries, ORM calls), so the rest of the app doesn't need to know how data is actually stored or fetched.
Think of it like
Like ordering from a restaurant menu without needing to know which supplier, fridge, or shelf the ingredients came from — the kitchen (repository) handles that.
Junior or senior?
Junior sounds like
Says the repository pattern makes code 'cleaner' with no further detail.
Senior sounds like
Can describe a concrete benefit it gave them, like swapping a data source or mocking data access in a test.
Ask them
“Did using a repository layer ever let you swap a data source, or mock data access for a test, without touching business logic?”