When do you prefer List over array in C#?
PICTURE THIS: ARRAY IN MEMORY
Index starts at 0. Scan once for max — O(n).
Simple meaning
List grows dynamically and has helpful methods.
WHY — Collections instead of guessing?
Why interviewers care about Collections:
on Collections.
the situation, the default choice, and one exception - that reads as experience.
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:
- 1List grows dynamically and
has helpful methods.
- 2Arrays are fixed size
and slightly leaner.
- 3I start with List
unless a fixed buffer or span-friendly API needs an array.
- 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
List grows dynamically and has helpful methods. Arrays are fixed size and slightly leaner.