Service Design · interview question
Which explanation would sound strongest in an interview when discussing dependency injection?
Multiple choiceMediumchapter-13-curatedpremiumservice-designdependency-injection
Answer and explanation
Correct answer
B. Inject repositories and services at boundary seams so tests and reasoning stay local and explicit. Candidates who speak clearly about seams and ownership sound more maintainable.
Why
Interviewers usually care less about keywords than about whether you can explain why the code is shaped the way it is.
Test yourself on Service Design
A free test with instant, explained results. No account needed.
More Service Design questions
- When is dependency injection being used in the wrong way?
- When is service layer being used in the wrong way?
- Which response shows the healthiest evidence-first mindset around dto mapping?
- Which option treats integration client shape as an engineering policy decision instead of a syntax trick?
- What is the clearest sign that code around integration client shape should be refactored?
- Another engineer will maintain this code later. What choice helps the most around service layer?