Why do teams prefer function components over class components today?
PICTURE THIS: GIT FLOW
Simple meaning
Hooks let us reuse stateful logic without HOCs and mixins.
WHY — React instead of guessing?
Why interviewers care about React:
on React.
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:
- 1Hooks let us reuse
stateful logic without HOCs and mixins.
- 2Function components are shorter
and match the current React docs.
- 3Classes still appear in
error boundaries and legacy code, so I can read both.
- 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
Hooks let us reuse stateful logic without HOCs and mixins. Function components are shorter and match the current React docs.