4 ms·

Hi, GitLab team member here. Due to a number of factors, which includes high applicant volumes, the talent acquisition team may not be able to provide detailed

Hi, GitLab team member here. Due to a number of factors, which includes high applicant volumes, the talent acquisition team may not be able to provide detailed decline feedback. You can get more details on our handbook page: https://about.gitlab.com/handbook/hiring/interviewing/#rejecting-candidates https://about.gitlab.com/handbook/hiring/interviewing/#rejec...

jaclaz 4y ago
> it may not be possible for the talent acquisition team to provide detailed decline feedback That sounds like the exception, but ok, what happens when it is not possible? Like you know, send a message "Dear candidate, unfortunately the talent acquisiton team did not manage to provide decline feedback because of xxxxxxx[0] , sorry." Or "nothing"? And in how many cases does this happen? Like 1%, 5%, 35% or 99%? IMHO it would be much simpler to directly write in your handbook something like: "No decline feedback will be provided. No exceptions." This way the candidate won't be expecting it. [0] Examples: my dog ate the feedback the feedback was stored in a cabinet that got flooded the hard disk where the feedback was stored failed before a backup was made
jdmg94 4y ago
idk about Gitlab specifically but its a slap on the face after dedicating 6 hours to jumping through hoops just to get ghosted.
- thenoblesunfish 4y ago
  There was no ghosting in this case, just a template rejection, two days later.
muzani 4y ago
I think the "If people argue with the feedback..." section is more telling. The fact that there's a SOP for this means it happens a lot.
lesuorac 4y ago
But you already have the detailed decline feedback (it's bullet point #2 [1]). The only effort on your part would be a simple copy-paste. I have to imagine that something else in the "number of factors" matters much more than "high applicant volumes". [1]: https://about.gitlab.com/handbook/hiring/interviewing/#rejecting-candidates https://about.gitlab.com/handbook/hiring/interviewing/#rejec... > Everyone who interviews a candidate must complete a scorecard and are required to input pros and cons as well as an overall recommendation.

jaclaz 4y ago

> it may not be possible for the talent acquisition team to provide detailed decline feedback That sounds like the exception, but ok, what happens when it is not possible? Like you know, send a message "Dear candidate, unfortunately the talent acquisiton team did not manage to provide decline feedback because of xxxxxxx[0] , sorry." Or "nothing"? And in how many cases does this happen? Like 1%, 5%, 35% or 99%? IMHO it would be much simpler to directly write in your handbook something like: "No decline feedback will be provided. No exceptions." This way the candidate won't be expecting it. [0] Examples: my dog ate the feedback the feedback was stored in a cabinet that got flooded the hard disk where the feedback was stored failed before a backup was made

jdmg94 4y ago

idk about Gitlab specifically but its a slap on the face after dedicating 6 hours to jumping through hoops just to get ghosted.

thenoblesunfish 4y ago
There was no ghosting in this case, just a template rejection, two days later.

muzani 4y ago

I think the "If people argue with the feedback..." section is more telling. The fact that there's a SOP for this means it happens a lot.

lesuorac 4y ago

But you already have the detailed decline feedback (it's bullet point #2 [1]). The only effort on your part would be a simple copy-paste. I have to imagine that something else in the "number of factors" matters much more than "high applicant volumes". [1]: https://about.gitlab.com/handbook/hiring/interviewing/#rejecting-candidates https://about.gitlab.com/handbook/hiring/interviewing/#rejec... > Everyone who interviews a candidate must complete a scorecard and are required to input pros and cons as well as an overall recommendation.