What are the advantages of a Kotlin data class and its functions?

What's really being asked

This question assesses your practical knowledge of Kotlin's language features beyond basic syntax. The interviewer wants to see if you understand why data class exists and how its generated functions, particularly copy(), support modern development patterns like immutability. It's a check for idiomatic Kotlin usage versus just translating Java patterns.

The full answer

A strong answer has three parts. First, state the primary advantage: data class saves developers from writing and maintaining boilerplate code for toString(), equals(), and hashCode(), making code more concise and less error-prone. Second, name at least three (but ideally all five) compiler-generated functions: toString() for readable logging, equals() for value-based comparison, hashCode() for use in hash-based collections, copy() for creating modified instances, and componentN() for destructuring declarations. Third, explain a practical use case for copy(). The best examples involve immutability, such as updating the state of a UI model. For instance, if you have a User data class and need to update their email, you'd use user.copy(email = "new@email.com") to create a new instance for a StateFlow or LiveData to emit, triggering a UI update without mutating the original state object.

The mistakes people make

A red flag is treating a data class like a simple POJO and not understanding its specific benefits. Many candidates can list toString() and equals() but fail to provide a compelling, real-world use case for copy(). Saying "it copies the object" is not enough. The key is explaining why you'd want a modified copy instead of just changing the original object's properties, which ties directly to immutability and predictable state management. Another mistake is being unaware of the restrictions, such as a data class needing at least one primary constructor parameter.

What usually comes next

"When would you NOT use a data class?" (Answer: When the class has behavior/logic, not just data, or when object identity matters more than value equality). "How does the equals() implementation differ from a regular class?" (Answer: Data class equals() compares property values; regular class equals() by default compares memory addresses). "What is the difference between val and var in a data class constructor?" (Answer: val creates an immutable property, var a mutable one; val is strongly preferred for data classes to support immutability).

A concrete example

A regular class Product("Keyboard", 49.99) might print a useless memory address like Product@6d06d69c. The equivalent data class prints a readable, useful string: Product(name=Keyboard, price=49.99). This is invaluable for debugging. For copy(), if you have val state = ViewState(isLoading = true, items = emptyList()), you can create an updated state with val newState = state.copy(isLoading = false, items = fetchedItems). The original state object is untouched.