What is the difference between a value type and a reference type?
PICTURE THIS: STACK VS QUEUE
Simple meaning
Value types like int and struct live on the stack when they are locals, and assignment copies the bits.
WHY — C# instead of guessing?
Why interviewers care about C#:
contrast on C#, 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:
- 1Value types like int
and struct live on the stack when they are locals, and assignment copies the bits.
- 2Reference types live on
the heap and assignment copies a pointer.
- 3I mention boxing when
a value type is treated as object, because that extra allocation shows up in hot loops.
- 4Give an example
One tiny concrete case you can say aloud.
- 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
Value types like int and struct live on the stack when they are locals, and assignment copies the bits. Reference types live on the heap and assignment copies a pointer.