Service Design · interview question
What does a strong engineer do when reasoning through dto mapping code?
Multiple choiceHardchapter-12-curatedpremiumservice-designdto-mapping
def to_order_summary(payload: dict[str, object]) -> dict[str, object]:
return {"id": payload["order_id"], "status": payload["state"]}Answer and explanation
Correct answer
D. Narrate the data shape, the state changes, and the exact rule order step by step.
Why
Interviewers often use simple code to test whether you can reason through execution without bluffing.
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?