Why prefer constructor injection over property injection?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
Constructor injection makes required dependencies obvious and testable.
WHY — DI instead of guessing?
Why interviewers care about DI:
on DI.
the situation, the default choice, and one exception - that reads as experience.
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:
- 1Constructor injection makes required
dependencies obvious and testable.
- 2Property injection hides what
is mandatory.
- 3I only use property
injection for optional framework hooks.
- 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
Constructor injection makes required dependencies obvious and testable. Property injection hides what is mandatory.