Working in a Domain interview questions

Domain knowledge as a skill rather than as a subject: why it decides between two technically equal candidates, how the vocabulary gates entry, and how to acquire it deliberately instead of absorbing it over a decade.

6 published across 3 topics.

Domain knowledge fundamentals57 short answers on one page, for revising rather than studying.

Acquiring Domain Knowledge

2 questions

How to learn an industry on purpose: the documents worth reading, the questions worth asking, and how to tell real understanding from fluent vocabulary.

hardScenarioBehaviouralCase Study

The domain expert tells you one thing and the written procedure says another. How do you work out which one the system should follow?

Treat both as evidence, not verdicts: a document records an intention on a date, an expert reports today's practice inside their own scope. Most contradictions resolve as staleness, scope or the exception path, and practice departing from a control is a finding to escalate rather than a requirement to build.

5 minmid, senior, staff, lead

mediumBehaviouralScenario

You are joining a business whose industry you have never worked in. How do you get up to speed in ninety days?

Trace one real unit of work end to end, read the operational artefacts rather than the marketing ones, interview the people who handle exceptions, and publish a glossary inviting correction. Understanding shows as prediction and knowing why a rule exists; fluency only names things.

6 minmid, senior, staff, lead

Speaking the Vocabulary

2 questions

The terms a stakeholder will use without explaining, and how to ask for a definition without losing credibility.

mediumConceptScenarioBehavioural

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.

4 minmid, senior, staff

easyBehaviouralScenario

A stakeholder keeps using a term you have never heard. What do you do in the meeting?

Judge whether the term blocks the decision in front of you: if it does, ask immediately, and ask for a concrete instance rather than a definition; if it does not, note it and follow up afterwards. Then play back your understanding in your own words so the correction happens in the meeting rather than in the code.

5 minentry, mid, senior

Domain Modelling in Practice

2 questions

Turning what the business says into a model that survives contact with its exceptions, and where domain-driven design earns its keep.

hardDesignScenarioCase Study

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.

6 minmid, senior, staff, lead

hardDesignConceptCase Study

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.

7 minmid, senior, staff