Java interview discussion prompts

Questions to explain

1. How is a primitive value different from an object reference? 2. What is the difference between an instance method and a static method? 3. When would you choose a list rather than a set?

A useful answer structure

Define the concept, give a tiny example and explain one tradeoff. Ask a follow-up question if the problem lacks context.

Try it

Write a two-minute explanation of why a mutable object can be changed through a reference even when the reference variable is final.

Trace a contract, then state the caveat

For an equality question, ask whether the operator compares primitive values, object identity or an equals implementation. String interning can make an incorrect identity test appear to work for literals. A runtime-created value exposes the difference. Follow up by describing stable hash keys rather than reciting only an equals slogan.

For a pass-by-value question, separate the copied reference from the shared object. A method can mutate the object reachable through the copied reference; assigning its parameter to another object does not replace the caller’s variable. The runnable reference example makes both effects observable.

For a collection complexity question, name the operation and its precondition. LinkedList insertion after an already positioned iterator differs from insertion at an index that first requires traversal. An answer that says all insertions are constant-time hides the lookup cost.

Turn a prediction into a checked example

Write the smallest complete program that preserves the disputed condition, compile it for the stated Java release and compare the output. For concurrency, one observed output is not proof that no other interleaving exists. Explain the visibility or synchronization rule that constrains possible outcomes.

A strong answer also distinguishes a guarantee from a diagnostic. ConcurrentModificationException is not a lock, and a garbage collector is not a deterministic resource closer. Use resource scopes to close files and connections.

Continue with object-contract questions and concurrency reasoning. Predict a failure case as well as the ordinary result, then explain which change repairs the violated contract.

Common Mistakes

Check empty inputs and invalid values before applying this operation to application data. State whether a method edits shared state or returns a separate value.