Why is constructor injection preferred over field @Autowired?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
Constructor injection makes dependencies required and final, which is easier to reason about and to unit test without Spring.
WHY — Spring Boot instead of guessing?
Why interviewers care about Spring Boot:
on Spring Boot.
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 dependencies
required and final, which is easier to reason about and to unit test without Spring.
- 2Field injection hides dependencies,
complicates testing, and can fail later with NullPointerException.
- 3Since Spring 4.3 a
single constructor does not even need @Autowired.
- 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 dependencies required and final, which is easier to reason about and to unit test without Spring. Field injection hides dependencies, complicates testing, and can fail later with NullPointerException.