How does CSS specificity decide which rule wins?
PICTURE THIS: 1, 2, 2, 8
Simple meaning
The browser scores inline styles, then IDs, then classes and attributes, then elements.
WHY — CSS instead of guessing?
Why interviewers care about CSS:
question about CSS.
trade-offs, and what you would actually do on a Frontend project - not buzzwords.
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:
- 1The browser scores inline
styles, then IDs, then classes and attributes, then elements.
- 2Equal specificity means the
later stylesheet rule wins.
- 3I avoid !important except
as a last resort because it makes later overrides painful.
- 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
The browser scores inline styles, then IDs, then classes and attributes, then elements. Equal specificity means the later stylesheet rule wins.