How does bcrypt salting protect stored passwords?
PICTURE THIS: DOM IS A TREE
Simple meaning
A salt is random data mixed into the hash so two users with the same password get different hashes.
WHY — Auth instead of guessing?
Why interviewers care about Auth:
question about Auth.
trade-offs, and what you would actually do on a Full Stack 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:
- 1A salt is random
data mixed into the hash so two users with the same password get different hashes.
- 2bcrypt also uses a
work factor that makes brute force expensive.
- 3Never reuse a global
salt or a fast hash for password storage.
- 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
A salt is random data mixed into the hash so two users with the same password get different hashes. bcrypt also uses a work factor that makes brute force expensive.