How would you implement real-time client-side validation in React?

WHAT THIS TESTS: This question probes whether you think in state-driven UI patterns rather than imperative jQuery-style DOM manipulation. The interviewer wants to see if you model the input as a finite set of visual states such as empty, typing, invalid, or valid, and derive the interface from that state rather than toggling elements directly.

A GOOD ANSWER COVERS: First, use a single status state variable such as typing, submitting, or error to represent the current visual mode rather than a collection of unrelated booleans. Second, keep the raw input value in state with useState and compute validation errors from that value during render or inside an event handler, avoiding redundant state like an errorMessage string that duplicates information already present in the input. Third, provide real-time feedback by validating on change or blur events rather than only on submit, but debounce expensive checks if necessary, for example waiting 300 milliseconds after the user stops typing before running a regex. Fourth, render error messages conditionally based on the derived validation result and status state, ensuring the message is accessible via aria-live or role alert. Fifth, disable the submit button when status is submitting or when validation fails, deriving disabled state from the same source of truth.

COMMON WRONG ANSWERS: A red flag is storing multiple boolean flags such as isEmpty, isTooShort, and hasInvalidChars in separate useState calls, which forces you to manually synchronize them on every keystroke and invites stale state bugs. Another anti-pattern is mutating the DOM directly with refs to show or hide error text instead of letting React re-render based on state. Candidates also sometimes store computed values like fullName when firstName and lastName already exist, violating the principle that state should not contain redundant information.

LIKELY FOLLOW-UPS: The interviewer might ask how you would preserve or reset validation state when the component unmounts and remounts, how you would share validation logic across multiple form fields without prop drilling, or how you would handle async validation such as checking username availability against an API.

ONE CONCRETE EXAMPLE: Suppose you are building an email input. You would store the email string in useState initialized to an empty value and store a status string initialized to typing. During render you compute isValid by checking whether the email includes an at symbol and has length greater than five. The error message renders only when status is error or when the user has blurred the field and isValid is false, using a paragraph element with an alert role. You never store isValid or the error message in state because both can be derived directly from the email value.

Source: react.dev