When I listen to people talk about previous work, I'm not sure if I'm actively listening for the "why". I am definitely listening for an understanding of their work though, which probably includes quite a bit of "why".
It can be difficult for people, especially those not in senior roles. Here are some valid answers you might encounter, but are challenging to formulate and not sound stupid or like a dick:
I just don't know why. My head was in this other part of the project and the discussions on this other bit just kind of passed me by.
Because my team lead was an uncompromising individual with outdated skills and forced the decision on us. (Wording here is so extremely important as not come across negatively -- that is, never say what I just wrote!)
A manager agreed with a vendor to use their product, now we're stuck with it.
It seemed more productive to just randomly pick one of A/B/C instead of wasting weeks evaluating them. (This is a legitimate reason at times, especially for smaller components).
I chose the unknown tech C, because I already know A and B and they are crap.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When I listen to people talk about previous work, I'm not sure if I'm actively listening for the "why". I am definitely listening for an understanding of their work though, which probably includes quite a bit of "why".
It can be difficult for people, especially those not in senior roles. Here are some valid answers you might encounter, but are challenging to formulate and not sound stupid or like a dick: