Why do we hash passwords instead of encrypting them?
PICTURE THIS: HASH MAP
Simple meaning
Hashing is one-way: even the server should not be able to recover the original password.
WHY — Auth instead of guessing?
Why interviewers care about Auth:
on Auth.
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:
- 1Hashing is one-way: even
the server should not be able to recover the original password.
- 2Encryption is two-way, so
a stolen key exposes every password.
- 3Use a slow salted
algorithm such as bcrypt, scrypt, or Argon2, never a fast hash like SHA-256 alone.
- 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
Hashing is one-way: even the server should not be able to recover the original password. Encryption is two-way, so a stolen key exposes every password.