What are the primary advantages of using a data class?

What's really being asked

Whether you understand that the data keyword is not mere syntactic sugar but a compiler contract that generates five standard functions to enable value semantics, structural equality, and safe immutable updates. Interviewers care if you know why this matters for correctness in collections, concurrency, and UI frameworks like Jetpack Compose.

The full answer

First, name at least three compiler-generated functions from the canonical five: toString for readable debugging output instead of a memory address like User@6d06d69c, equals for structural value comparison rather than reference identity, hashCode for correct behavior in HashSet and HashMap, copy for creating modified instances without mutating the original, and componentN functions for destructuring declarations. Second, explain the primary advantage as boilerplate elimination and guaranteed consistency between equals and hashCode, which prevents subtle bugs when objects are used as keys. Third, describe a practical copy use case such as updating an immutable UI state object in a ViewModel where only one property changes while the rest are preserved, ensuring thread safety and clean diffing in reactive frameworks. Fourth, mention the language restrictions: the primary constructor must have at least one parameter marked as val or var, and the class cannot be abstract, open, sealed, or inner, though it may implement interfaces.

The mistakes people make

Saying data classes are only for holding data without listing the specific generated functions. Confusing reference equality with structural equality and not knowing when each applies. Suggesting copy performs a deep clone when it actually performs a shallow copy of the primary constructor properties. Forgetting that hashCode must contractually match equals semantics, which the compiler handles automatically but candidates often fail to appreciate. Claiming data classes can be open or inherit from other classes, or that body-declared properties participate in generated functions.

What usually comes next

When would you prefer a regular class over a data class? How does copy behave with mutable properties nested inside a data class? What happens to properties declared in the class body rather than the primary constructor? How do data classes interact with Parcelable, JSON serialization, or Room? Can you override toString or equals manually in a data class, and what are the risks? Why does Kotlin enforce val or var in the primary constructor?

A concrete example

In an Android ViewModel managing a login screen, define data class LoginUiState(val email: String, val password: String, val isLoading: Boolean, val error: String?). When the user types an email, emit a new state with state.copy(email = newEmail) rather than mutating the existing object. This preserves immutability, prevents race conditions in concurrent flows, and lets Compose or Flow detect state changes reliably through structural equality without manual change detection logic.