Skip to interview prep
Apexed

86. An upstream team wants to change a field's meaning without changing its name. What would you assess?

HardData & validation

Case
Show model answer

I'd identify consumers, reports, validation rules and decisions that depend on the current semantics. A technically compatible schema change can still break business meaning when a familiar field now represents a different status, unit, population or effective date for downstream teams.

I'd agree versioning, communication and consumer checks before transition. An unchanged name does not make semantic change harmless, and successful parsing does not demonstrate preserved business meaning downstream.

What interviewers listen for

  • Trace semantic dependencies
  • Agree versioning and transition
  • Validate consumer meaning not parsing alone
An upstream team wants to change a field's meaning without changing its name. What would you assess — Business analysis interview question — Apexed