Top 3 Domain modelling Interview Questions
Browse 3 real-world technical and behavioral interview questions about Domain modelling. Review scenarios, edge cases, and architectural best practices.
How do you turn what the business tells you into a domain model that holds up once the exceptions arrive?
Model the state changes and invariants rather than the nouns the business names, and go looking for reversal, amendment, partial completion and manual override before committing to a shape. Domain-driven design earns its keep where rules are contested; on CRUD and reporting it is ceremony.
Everyone in the business calls it the fax queue, and nothing has been faxed since 2014. Do you keep that name in the code?
Usually yes for the label and no for the concept. A fossil name is still the word that lets you and the business point at the same thing, so keep it as the shared term, but model what the queue is for today rather than the channel it was named after.
The operations team says there is no rule for this, they just use judgement. How do you model that?
Judgement is an unwritten rule plus a genuine discretion, so separate the two. Sample real decisions to find the factors deciding most cases, automate the unambiguous ends, and model the discretionary middle as a recorded decision carrying its inputs, recommendation and reason.