Explain equals and hashCode contract.
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of Java conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
Rules:
- If a.equals(b) is true then a.hashCode() == b.hashCode() must be true.
- If two objects are unequal, their hash codes may still collide (allowed).
- equals must be reflexive, symmetric, transitive and consistent.
- Override both together, or hash-based collections (HashMap, HashSet) misbehave.
@Override
public boolean equals(Object o) {
if (this == o) return true;
if (!(o instanceof User u)) return false; // pattern matching (Java 16+)
return id == u.id && Objects.equals(email, u.email);
}
@Override
public int hashCode() { return Objects.hash(id, email); }
Mutable fields used in equals/hashCode are a classic bug: mutating them after insertion corrupts the collection.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.