Why do you prefer forward declarations in headers?
PICTURE THIS: HOW TO EXPLAIN IT
IdeaBuild
HowWhat happens inside
Why they askShows real use
Simple meaning
They cut include graphs and compile times.
WHY — Build instead of guessing?
Why interviewers care about Build:
They are checking judgment
on Build.
A good answer names
the situation, the default choice, and one exception - that reads as experience.
Stay structured
Name the idea, why it exists, then one short example.
Close cleanly
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:
- 1They cut include graphs
and compile times.
- 2Heavy headers in every
translation unit slow CI.
- 3I include what I
use in .cpp files.
- 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:
Say this line
“Heavy headers in every translation unit slow CI.”
Break into beats
Heavyheadersineverytranslationunit
Speaking order
2987408337471632900
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
They cut include graphs and compile times. Heavy headers in every translation unit slow CI.