I did indeed find a role with an engineering organization I really like. Surprisingly, they were one of my lower-ranked picks for myself when I started the process but they ended up being my top pick by a mile. :-)
Regarding your rejection letters, telling a candidate why you chose another candidate could end up adding friction as they try to justify their knowledge, but the reality is that they don't know who the other candidate is and how much experience they have with X technology, so it's hard for them to argue. They'll probably ask, but at that point it's probably best to leave those interactions to the recruiter (assuming you have internal recruiters) so you can focus more on other candidates.
But to take it back a bit, a "we prefer them" rejection is often way better received by a candidate than a "we don't want you" rejection. :-)
Some comments have been hidden by the post's author - find out more
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.
I did indeed find a role with an engineering organization I really like. Surprisingly, they were one of my lower-ranked picks for myself when I started the process but they ended up being my top pick by a mile. :-)
Regarding your rejection letters, telling a candidate why you chose another candidate could end up adding friction as they try to justify their knowledge, but the reality is that they don't know who the other candidate is and how much experience they have with X technology, so it's hard for them to argue. They'll probably ask, but at that point it's probably best to leave those interactions to the recruiter (assuming you have internal recruiters) so you can focus more on other candidates.
But to take it back a bit, a "we prefer them" rejection is often way better received by a candidate than a "we don't want you" rejection. :-)