Where do instance variables live versus local variables: heap or stack?
PICTURE THIS: HOW JAVA RUNS
Simple meaning
Local variables and method call frames live on the stack of the current thread.
WHY — JVM instead of guessing?
Why interviewers care about JVM:
contrast on JVM, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Local variables and method
call frames live on the stack of the current thread.
- 2Objects and their instance
fields live on the heap.
- 3Primitive locals sit on
the stack
- 4if you box them
into objects, those objects go on the heap.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Local variables and method call frames live on the stack of the current thread. Objects and their instance fields live on the heap.