Should I say anything 'bad' about candidate(s) who'll be replacing me?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
18
down vote
favorite
I'm currently serving notice period in my current company and will be joining a new company in some time (a little over a month). So naturally my current company is looking for a replacement, and I was asked to conduct a technical round before our director meets and finalizes a candidate. I have worked for the company for a couple of years now, and don't want my/any projects to fail. I really hope they succeed with as little overhead as possible. Hence, I would really like to get someone settled in my position before leaving.
Recently, I met a candidate who is highly supported by our HR and looked good on paper but didn't answer most of my questions well. Hence, I didn't find the person suitable for the job. Having said that, my last day at work is approaching and we haven't found a replacement for my position yet. So, my question is "Will me speaking badly about a 'highly desired' candidate be viewed as me being disloyal, damaging, etc in any way to the company?"
I have had no issues with any of my colleagues, managers, etc including the said HR and I'd like to keep it that way if possible.
Side notes: As far as I know, my technical round is final, but our director also has exposure to the technical aspects and may ask some questions of his own (which kind of adds to my worry, as if he found I passed an unsuitable candidate, I may lose his trust).
FYI, even though I framed the question like I'm currently in the situation, I was short on time and had to give my answer yesterday evening. I rejected the candidate, citing some of the 'shaky' responses they gave (which clearly didn't convince our HR who seems upset), but I would like to be prepared and act more cautiously in similar situations in the future. I don't know how else I could handle it better.
professionalism software-industry conflict
New contributor
|
show 5 more comments
up vote
18
down vote
favorite
I'm currently serving notice period in my current company and will be joining a new company in some time (a little over a month). So naturally my current company is looking for a replacement, and I was asked to conduct a technical round before our director meets and finalizes a candidate. I have worked for the company for a couple of years now, and don't want my/any projects to fail. I really hope they succeed with as little overhead as possible. Hence, I would really like to get someone settled in my position before leaving.
Recently, I met a candidate who is highly supported by our HR and looked good on paper but didn't answer most of my questions well. Hence, I didn't find the person suitable for the job. Having said that, my last day at work is approaching and we haven't found a replacement for my position yet. So, my question is "Will me speaking badly about a 'highly desired' candidate be viewed as me being disloyal, damaging, etc in any way to the company?"
I have had no issues with any of my colleagues, managers, etc including the said HR and I'd like to keep it that way if possible.
Side notes: As far as I know, my technical round is final, but our director also has exposure to the technical aspects and may ask some questions of his own (which kind of adds to my worry, as if he found I passed an unsuitable candidate, I may lose his trust).
FYI, even though I framed the question like I'm currently in the situation, I was short on time and had to give my answer yesterday evening. I rejected the candidate, citing some of the 'shaky' responses they gave (which clearly didn't convince our HR who seems upset), but I would like to be prepared and act more cautiously in similar situations in the future. I don't know how else I could handle it better.
professionalism software-industry conflict
New contributor
3
@downvoter(s) Pls explain your action.
– Badhan Ganesh
15 hours ago
6
Yes, It'll be really helpful if you can tell me the reason for downvotes, I'll edit the question as required.
– Lifelong Scholar
12 hours ago
7
Keep in mind that downvotes must reflect the question itself, not OP's actions or beliefs. If you disagree with them, write an answer or take it to chat.
– rath
10 hours ago
8
@rath Downvotes "must" not reflect anything other than the downvoter's wish to use it.
– pipe
9 hours ago
11
@pipe Please read the hover label over the vote down button: This question does not show any research effort; it is unclear or not useful. It doesn't say This question says something I disagree with. The premise of many questions can be seen as problematic, regardless, this is the place they come to get help.
– rath
9 hours ago
|
show 5 more comments
up vote
18
down vote
favorite
up vote
18
down vote
favorite
I'm currently serving notice period in my current company and will be joining a new company in some time (a little over a month). So naturally my current company is looking for a replacement, and I was asked to conduct a technical round before our director meets and finalizes a candidate. I have worked for the company for a couple of years now, and don't want my/any projects to fail. I really hope they succeed with as little overhead as possible. Hence, I would really like to get someone settled in my position before leaving.
Recently, I met a candidate who is highly supported by our HR and looked good on paper but didn't answer most of my questions well. Hence, I didn't find the person suitable for the job. Having said that, my last day at work is approaching and we haven't found a replacement for my position yet. So, my question is "Will me speaking badly about a 'highly desired' candidate be viewed as me being disloyal, damaging, etc in any way to the company?"
I have had no issues with any of my colleagues, managers, etc including the said HR and I'd like to keep it that way if possible.
Side notes: As far as I know, my technical round is final, but our director also has exposure to the technical aspects and may ask some questions of his own (which kind of adds to my worry, as if he found I passed an unsuitable candidate, I may lose his trust).
FYI, even though I framed the question like I'm currently in the situation, I was short on time and had to give my answer yesterday evening. I rejected the candidate, citing some of the 'shaky' responses they gave (which clearly didn't convince our HR who seems upset), but I would like to be prepared and act more cautiously in similar situations in the future. I don't know how else I could handle it better.
professionalism software-industry conflict
New contributor
I'm currently serving notice period in my current company and will be joining a new company in some time (a little over a month). So naturally my current company is looking for a replacement, and I was asked to conduct a technical round before our director meets and finalizes a candidate. I have worked for the company for a couple of years now, and don't want my/any projects to fail. I really hope they succeed with as little overhead as possible. Hence, I would really like to get someone settled in my position before leaving.
Recently, I met a candidate who is highly supported by our HR and looked good on paper but didn't answer most of my questions well. Hence, I didn't find the person suitable for the job. Having said that, my last day at work is approaching and we haven't found a replacement for my position yet. So, my question is "Will me speaking badly about a 'highly desired' candidate be viewed as me being disloyal, damaging, etc in any way to the company?"
I have had no issues with any of my colleagues, managers, etc including the said HR and I'd like to keep it that way if possible.
Side notes: As far as I know, my technical round is final, but our director also has exposure to the technical aspects and may ask some questions of his own (which kind of adds to my worry, as if he found I passed an unsuitable candidate, I may lose his trust).
FYI, even though I framed the question like I'm currently in the situation, I was short on time and had to give my answer yesterday evening. I rejected the candidate, citing some of the 'shaky' responses they gave (which clearly didn't convince our HR who seems upset), but I would like to be prepared and act more cautiously in similar situations in the future. I don't know how else I could handle it better.
professionalism software-industry conflict
professionalism software-industry conflict
New contributor
New contributor
edited 43 mins ago
Sharlike
1154
1154
New contributor
asked 16 hours ago
Lifelong Scholar
10214
10214
New contributor
New contributor
3
@downvoter(s) Pls explain your action.
– Badhan Ganesh
15 hours ago
6
Yes, It'll be really helpful if you can tell me the reason for downvotes, I'll edit the question as required.
– Lifelong Scholar
12 hours ago
7
Keep in mind that downvotes must reflect the question itself, not OP's actions or beliefs. If you disagree with them, write an answer or take it to chat.
– rath
10 hours ago
8
@rath Downvotes "must" not reflect anything other than the downvoter's wish to use it.
– pipe
9 hours ago
11
@pipe Please read the hover label over the vote down button: This question does not show any research effort; it is unclear or not useful. It doesn't say This question says something I disagree with. The premise of many questions can be seen as problematic, regardless, this is the place they come to get help.
– rath
9 hours ago
|
show 5 more comments
3
@downvoter(s) Pls explain your action.
– Badhan Ganesh
15 hours ago
6
Yes, It'll be really helpful if you can tell me the reason for downvotes, I'll edit the question as required.
– Lifelong Scholar
12 hours ago
7
Keep in mind that downvotes must reflect the question itself, not OP's actions or beliefs. If you disagree with them, write an answer or take it to chat.
– rath
10 hours ago
8
@rath Downvotes "must" not reflect anything other than the downvoter's wish to use it.
– pipe
9 hours ago
11
@pipe Please read the hover label over the vote down button: This question does not show any research effort; it is unclear or not useful. It doesn't say This question says something I disagree with. The premise of many questions can be seen as problematic, regardless, this is the place they come to get help.
– rath
9 hours ago
3
3
@downvoter(s) Pls explain your action.
– Badhan Ganesh
15 hours ago
@downvoter(s) Pls explain your action.
– Badhan Ganesh
15 hours ago
6
6
Yes, It'll be really helpful if you can tell me the reason for downvotes, I'll edit the question as required.
– Lifelong Scholar
12 hours ago
Yes, It'll be really helpful if you can tell me the reason for downvotes, I'll edit the question as required.
– Lifelong Scholar
12 hours ago
7
7
Keep in mind that downvotes must reflect the question itself, not OP's actions or beliefs. If you disagree with them, write an answer or take it to chat.
– rath
10 hours ago
Keep in mind that downvotes must reflect the question itself, not OP's actions or beliefs. If you disagree with them, write an answer or take it to chat.
– rath
10 hours ago
8
8
@rath Downvotes "must" not reflect anything other than the downvoter's wish to use it.
– pipe
9 hours ago
@rath Downvotes "must" not reflect anything other than the downvoter's wish to use it.
– pipe
9 hours ago
11
11
@pipe Please read the hover label over the vote down button: This question does not show any research effort; it is unclear or not useful. It doesn't say This question says something I disagree with. The premise of many questions can be seen as problematic, regardless, this is the place they come to get help.
– rath
9 hours ago
@pipe Please read the hover label over the vote down button: This question does not show any research effort; it is unclear or not useful. It doesn't say This question says something I disagree with. The premise of many questions can be seen as problematic, regardless, this is the place they come to get help.
– rath
9 hours ago
|
show 5 more comments
6 Answers
6
active
oldest
votes
up vote
44
down vote
"I was asked to conduct a technical round before our director meets
and finalizes a candidate".
You were probably asked to do this because you have the best grasp of what the candidate will be doing and if he is able to perform that.
There are many candidates that look good in HR eyes but are terrible while doing their job.
I would say it's professional to share your concerns with the director so he may be aware and ask similar questions to dispel or confirm doubts.
6
The key is to keep it as objective as possible. If there are weak areas, definitely highlight them, but similarly if they have any strengths or areas where you feel they have potential, absolutely add those too. You don't want it to appear that you're being deliberately unhelpful or trying to shoot down your replacement, but they asked for your opinion for a reason and they ignore your expertise at their own risk.
– delinear
8 hours ago
12
If OP was asked to do this when they were in their notice period, then someone respects/values OPs opinion on the issue and they deserve OPs best efforts
– cdkMoose
8 hours ago
add a comment |
up vote
27
down vote
No, you did the right thing. The candidate wasn't good enough, so you said so. That's just simple honesty and professionalism, assuming that your judgement isn't being influenced by the fact you're leaving (and it very much sounds like it's not being influenced). You gave management the information they needed to make a decision. They're still at liberty to say "we'll hire this candidate anyway, even though our technical team has reservations about them".
In fact, I'd think worse of a leaving employee who just said "yes, they're great" to everybody they interviewed as their potential replacement because that's the "easy" thing to say.
1
To add to this as someone who has been on both ends of the technical interview process: Saying, "yes, they're great!" when the candidate is not capable of doing the job will reflect poorly on the interviewer in the future. It may signal that the interviewer is not a competent judge of skill and not a suitable team leader, and if they need to work with anyone from the company they're leaving in the future, that reputation may do a disservice.
– Logan Bertram
3 hours ago
add a comment |
up vote
8
down vote
Don't think of it as speaking "badly" about the candidate.
You shouldn't be any more worried about giving negative feedback about a favored candidate as you would be about giving positive feedback about a unfavored candidate. You, HR, and your director are all involved in the hiring process for specific reasons, it's OK if you don't all agree.
The thing you need to worry about is giving accurate feedback. Make sure you understand what kind of feedback you're being asked to provide - in this case, it sounds clear that you're being asked to evaluate technical skills. So, do that.
Honestly, the fact that you're leaving soon, or that you're personally interested in these project succeeding, shouldn't play into it. You're still an employee of this company (for now), you've been given a task, and you can and should do your best to perform it.
1
OP's edit: "I rejected the candidate citing some of the 'shaky' responses from the candidate (which clearly didn't convince our HR who seems upset)", so it seems it was exactly this accurate feedback that was needed and that the OP did not have time to prepare in advance. Lesson learned.
– CPHPython
9 hours ago
add a comment |
up vote
8
down vote
While you are still working at the company, you should work to the same standard as you would if you weren't currently serving your notice period (though you are only human, and motivation will probably slip towards the end).
Hiring / recruitment is a key part of any job, and arguably the most important thing any company can do. You have been asked to be a part of the recruitment process, so you should do it to the best of your ability.
If you believe that the best thing for the company would be to reject the candidate - then you should recommend that the candidate is rejected. That isn't "speaking bad about your replacement", that is doing your job on behalf of the company. It is the professional and proper thing to do. Conversely, a positive recommendation would be putting the company at risk of a bad hire, which is not a good outcome.
(If it helps you worry less: if the only answer it was acceptable for you to give was "yes", they wouldn't have bothered asking you at all...)
add a comment |
up vote
1
down vote
I agree with other answers that say that you should provide a clear and thruthful feedback.
Only I suggest that you make sure you and your director and HR all agree on what kind of a person they want to hire. For example, if your director and HR are OK with hiring a capable junior, and you asked some advanced technical questions, then probably it is not correct to outright reject the candidate. In any case, you should clearly state your doubts, but don't say that the candidate is not good for the position until you clearly understand what others expect from that position.
In fact, I do not know how hiring process is organized in your company, but in some organisations you might have some kind of "veto right" to completely reject a candidate. In situations when you are not leaving such a right is sensble, as you would work with a successfull candidate, and so you may have all rights to reject a candidate that did not suit your expectations.
But you are leaving, so the candidate will work with your director, not you. So I think that you should not use such "veto right" in this case. State your doubts clearly, but make it clear that it is director and HR who should make the final decision.
New contributor
add a comment |
up vote
-1
down vote
Not telling them truthfully that you wouldn’t hire this candidate, that would be disloyal, damaging, not doing your job.
How this can be seen wouldn’t matter to me. If they ask for my opinion and then don’t like it, that’s not my problem, that is someone else’s problem. But most likely your HR and hiring manager are reasonable people and will realise that they are getting good advise.
add a comment |
StackExchange.ready(function () {
$("#show-editor-button input, #show-editor-button button").click(function () {
var showEditor = function() {
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
};
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True') {
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup({
url: '/post/self-answer-popup',
loaded: function(popup) {
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
}
})
} else{
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true) {
showEditor();
}
}
});
});
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
44
down vote
"I was asked to conduct a technical round before our director meets
and finalizes a candidate".
You were probably asked to do this because you have the best grasp of what the candidate will be doing and if he is able to perform that.
There are many candidates that look good in HR eyes but are terrible while doing their job.
I would say it's professional to share your concerns with the director so he may be aware and ask similar questions to dispel or confirm doubts.
6
The key is to keep it as objective as possible. If there are weak areas, definitely highlight them, but similarly if they have any strengths or areas where you feel they have potential, absolutely add those too. You don't want it to appear that you're being deliberately unhelpful or trying to shoot down your replacement, but they asked for your opinion for a reason and they ignore your expertise at their own risk.
– delinear
8 hours ago
12
If OP was asked to do this when they were in their notice period, then someone respects/values OPs opinion on the issue and they deserve OPs best efforts
– cdkMoose
8 hours ago
add a comment |
up vote
44
down vote
"I was asked to conduct a technical round before our director meets
and finalizes a candidate".
You were probably asked to do this because you have the best grasp of what the candidate will be doing and if he is able to perform that.
There are many candidates that look good in HR eyes but are terrible while doing their job.
I would say it's professional to share your concerns with the director so he may be aware and ask similar questions to dispel or confirm doubts.
6
The key is to keep it as objective as possible. If there are weak areas, definitely highlight them, but similarly if they have any strengths or areas where you feel they have potential, absolutely add those too. You don't want it to appear that you're being deliberately unhelpful or trying to shoot down your replacement, but they asked for your opinion for a reason and they ignore your expertise at their own risk.
– delinear
8 hours ago
12
If OP was asked to do this when they were in their notice period, then someone respects/values OPs opinion on the issue and they deserve OPs best efforts
– cdkMoose
8 hours ago
add a comment |
up vote
44
down vote
up vote
44
down vote
"I was asked to conduct a technical round before our director meets
and finalizes a candidate".
You were probably asked to do this because you have the best grasp of what the candidate will be doing and if he is able to perform that.
There are many candidates that look good in HR eyes but are terrible while doing their job.
I would say it's professional to share your concerns with the director so he may be aware and ask similar questions to dispel or confirm doubts.
"I was asked to conduct a technical round before our director meets
and finalizes a candidate".
You were probably asked to do this because you have the best grasp of what the candidate will be doing and if he is able to perform that.
There are many candidates that look good in HR eyes but are terrible while doing their job.
I would say it's professional to share your concerns with the director so he may be aware and ask similar questions to dispel or confirm doubts.
edited 15 hours ago
Magellan
32
32
answered 15 hours ago
SZCZERZO KŁY
1,757213
1,757213
6
The key is to keep it as objective as possible. If there are weak areas, definitely highlight them, but similarly if they have any strengths or areas where you feel they have potential, absolutely add those too. You don't want it to appear that you're being deliberately unhelpful or trying to shoot down your replacement, but they asked for your opinion for a reason and they ignore your expertise at their own risk.
– delinear
8 hours ago
12
If OP was asked to do this when they were in their notice period, then someone respects/values OPs opinion on the issue and they deserve OPs best efforts
– cdkMoose
8 hours ago
add a comment |
6
The key is to keep it as objective as possible. If there are weak areas, definitely highlight them, but similarly if they have any strengths or areas where you feel they have potential, absolutely add those too. You don't want it to appear that you're being deliberately unhelpful or trying to shoot down your replacement, but they asked for your opinion for a reason and they ignore your expertise at their own risk.
– delinear
8 hours ago
12
If OP was asked to do this when they were in their notice period, then someone respects/values OPs opinion on the issue and they deserve OPs best efforts
– cdkMoose
8 hours ago
6
6
The key is to keep it as objective as possible. If there are weak areas, definitely highlight them, but similarly if they have any strengths or areas where you feel they have potential, absolutely add those too. You don't want it to appear that you're being deliberately unhelpful or trying to shoot down your replacement, but they asked for your opinion for a reason and they ignore your expertise at their own risk.
– delinear
8 hours ago
The key is to keep it as objective as possible. If there are weak areas, definitely highlight them, but similarly if they have any strengths or areas where you feel they have potential, absolutely add those too. You don't want it to appear that you're being deliberately unhelpful or trying to shoot down your replacement, but they asked for your opinion for a reason and they ignore your expertise at their own risk.
– delinear
8 hours ago
12
12
If OP was asked to do this when they were in their notice period, then someone respects/values OPs opinion on the issue and they deserve OPs best efforts
– cdkMoose
8 hours ago
If OP was asked to do this when they were in their notice period, then someone respects/values OPs opinion on the issue and they deserve OPs best efforts
– cdkMoose
8 hours ago
add a comment |
up vote
27
down vote
No, you did the right thing. The candidate wasn't good enough, so you said so. That's just simple honesty and professionalism, assuming that your judgement isn't being influenced by the fact you're leaving (and it very much sounds like it's not being influenced). You gave management the information they needed to make a decision. They're still at liberty to say "we'll hire this candidate anyway, even though our technical team has reservations about them".
In fact, I'd think worse of a leaving employee who just said "yes, they're great" to everybody they interviewed as their potential replacement because that's the "easy" thing to say.
1
To add to this as someone who has been on both ends of the technical interview process: Saying, "yes, they're great!" when the candidate is not capable of doing the job will reflect poorly on the interviewer in the future. It may signal that the interviewer is not a competent judge of skill and not a suitable team leader, and if they need to work with anyone from the company they're leaving in the future, that reputation may do a disservice.
– Logan Bertram
3 hours ago
add a comment |
up vote
27
down vote
No, you did the right thing. The candidate wasn't good enough, so you said so. That's just simple honesty and professionalism, assuming that your judgement isn't being influenced by the fact you're leaving (and it very much sounds like it's not being influenced). You gave management the information they needed to make a decision. They're still at liberty to say "we'll hire this candidate anyway, even though our technical team has reservations about them".
In fact, I'd think worse of a leaving employee who just said "yes, they're great" to everybody they interviewed as their potential replacement because that's the "easy" thing to say.
1
To add to this as someone who has been on both ends of the technical interview process: Saying, "yes, they're great!" when the candidate is not capable of doing the job will reflect poorly on the interviewer in the future. It may signal that the interviewer is not a competent judge of skill and not a suitable team leader, and if they need to work with anyone from the company they're leaving in the future, that reputation may do a disservice.
– Logan Bertram
3 hours ago
add a comment |
up vote
27
down vote
up vote
27
down vote
No, you did the right thing. The candidate wasn't good enough, so you said so. That's just simple honesty and professionalism, assuming that your judgement isn't being influenced by the fact you're leaving (and it very much sounds like it's not being influenced). You gave management the information they needed to make a decision. They're still at liberty to say "we'll hire this candidate anyway, even though our technical team has reservations about them".
In fact, I'd think worse of a leaving employee who just said "yes, they're great" to everybody they interviewed as their potential replacement because that's the "easy" thing to say.
No, you did the right thing. The candidate wasn't good enough, so you said so. That's just simple honesty and professionalism, assuming that your judgement isn't being influenced by the fact you're leaving (and it very much sounds like it's not being influenced). You gave management the information they needed to make a decision. They're still at liberty to say "we'll hire this candidate anyway, even though our technical team has reservations about them".
In fact, I'd think worse of a leaving employee who just said "yes, they're great" to everybody they interviewed as their potential replacement because that's the "easy" thing to say.
answered 15 hours ago
Philip Kendall
47.5k32118149
47.5k32118149
1
To add to this as someone who has been on both ends of the technical interview process: Saying, "yes, they're great!" when the candidate is not capable of doing the job will reflect poorly on the interviewer in the future. It may signal that the interviewer is not a competent judge of skill and not a suitable team leader, and if they need to work with anyone from the company they're leaving in the future, that reputation may do a disservice.
– Logan Bertram
3 hours ago
add a comment |
1
To add to this as someone who has been on both ends of the technical interview process: Saying, "yes, they're great!" when the candidate is not capable of doing the job will reflect poorly on the interviewer in the future. It may signal that the interviewer is not a competent judge of skill and not a suitable team leader, and if they need to work with anyone from the company they're leaving in the future, that reputation may do a disservice.
– Logan Bertram
3 hours ago
1
1
To add to this as someone who has been on both ends of the technical interview process: Saying, "yes, they're great!" when the candidate is not capable of doing the job will reflect poorly on the interviewer in the future. It may signal that the interviewer is not a competent judge of skill and not a suitable team leader, and if they need to work with anyone from the company they're leaving in the future, that reputation may do a disservice.
– Logan Bertram
3 hours ago
To add to this as someone who has been on both ends of the technical interview process: Saying, "yes, they're great!" when the candidate is not capable of doing the job will reflect poorly on the interviewer in the future. It may signal that the interviewer is not a competent judge of skill and not a suitable team leader, and if they need to work with anyone from the company they're leaving in the future, that reputation may do a disservice.
– Logan Bertram
3 hours ago
add a comment |
up vote
8
down vote
Don't think of it as speaking "badly" about the candidate.
You shouldn't be any more worried about giving negative feedback about a favored candidate as you would be about giving positive feedback about a unfavored candidate. You, HR, and your director are all involved in the hiring process for specific reasons, it's OK if you don't all agree.
The thing you need to worry about is giving accurate feedback. Make sure you understand what kind of feedback you're being asked to provide - in this case, it sounds clear that you're being asked to evaluate technical skills. So, do that.
Honestly, the fact that you're leaving soon, or that you're personally interested in these project succeeding, shouldn't play into it. You're still an employee of this company (for now), you've been given a task, and you can and should do your best to perform it.
1
OP's edit: "I rejected the candidate citing some of the 'shaky' responses from the candidate (which clearly didn't convince our HR who seems upset)", so it seems it was exactly this accurate feedback that was needed and that the OP did not have time to prepare in advance. Lesson learned.
– CPHPython
9 hours ago
add a comment |
up vote
8
down vote
Don't think of it as speaking "badly" about the candidate.
You shouldn't be any more worried about giving negative feedback about a favored candidate as you would be about giving positive feedback about a unfavored candidate. You, HR, and your director are all involved in the hiring process for specific reasons, it's OK if you don't all agree.
The thing you need to worry about is giving accurate feedback. Make sure you understand what kind of feedback you're being asked to provide - in this case, it sounds clear that you're being asked to evaluate technical skills. So, do that.
Honestly, the fact that you're leaving soon, or that you're personally interested in these project succeeding, shouldn't play into it. You're still an employee of this company (for now), you've been given a task, and you can and should do your best to perform it.
1
OP's edit: "I rejected the candidate citing some of the 'shaky' responses from the candidate (which clearly didn't convince our HR who seems upset)", so it seems it was exactly this accurate feedback that was needed and that the OP did not have time to prepare in advance. Lesson learned.
– CPHPython
9 hours ago
add a comment |
up vote
8
down vote
up vote
8
down vote
Don't think of it as speaking "badly" about the candidate.
You shouldn't be any more worried about giving negative feedback about a favored candidate as you would be about giving positive feedback about a unfavored candidate. You, HR, and your director are all involved in the hiring process for specific reasons, it's OK if you don't all agree.
The thing you need to worry about is giving accurate feedback. Make sure you understand what kind of feedback you're being asked to provide - in this case, it sounds clear that you're being asked to evaluate technical skills. So, do that.
Honestly, the fact that you're leaving soon, or that you're personally interested in these project succeeding, shouldn't play into it. You're still an employee of this company (for now), you've been given a task, and you can and should do your best to perform it.
Don't think of it as speaking "badly" about the candidate.
You shouldn't be any more worried about giving negative feedback about a favored candidate as you would be about giving positive feedback about a unfavored candidate. You, HR, and your director are all involved in the hiring process for specific reasons, it's OK if you don't all agree.
The thing you need to worry about is giving accurate feedback. Make sure you understand what kind of feedback you're being asked to provide - in this case, it sounds clear that you're being asked to evaluate technical skills. So, do that.
Honestly, the fact that you're leaving soon, or that you're personally interested in these project succeeding, shouldn't play into it. You're still an employee of this company (for now), you've been given a task, and you can and should do your best to perform it.
answered 11 hours ago
dwizum
8,06321937
8,06321937
1
OP's edit: "I rejected the candidate citing some of the 'shaky' responses from the candidate (which clearly didn't convince our HR who seems upset)", so it seems it was exactly this accurate feedback that was needed and that the OP did not have time to prepare in advance. Lesson learned.
– CPHPython
9 hours ago
add a comment |
1
OP's edit: "I rejected the candidate citing some of the 'shaky' responses from the candidate (which clearly didn't convince our HR who seems upset)", so it seems it was exactly this accurate feedback that was needed and that the OP did not have time to prepare in advance. Lesson learned.
– CPHPython
9 hours ago
1
1
OP's edit: "I rejected the candidate citing some of the 'shaky' responses from the candidate (which clearly didn't convince our HR who seems upset)", so it seems it was exactly this accurate feedback that was needed and that the OP did not have time to prepare in advance. Lesson learned.
– CPHPython
9 hours ago
OP's edit: "I rejected the candidate citing some of the 'shaky' responses from the candidate (which clearly didn't convince our HR who seems upset)", so it seems it was exactly this accurate feedback that was needed and that the OP did not have time to prepare in advance. Lesson learned.
– CPHPython
9 hours ago
add a comment |
up vote
8
down vote
While you are still working at the company, you should work to the same standard as you would if you weren't currently serving your notice period (though you are only human, and motivation will probably slip towards the end).
Hiring / recruitment is a key part of any job, and arguably the most important thing any company can do. You have been asked to be a part of the recruitment process, so you should do it to the best of your ability.
If you believe that the best thing for the company would be to reject the candidate - then you should recommend that the candidate is rejected. That isn't "speaking bad about your replacement", that is doing your job on behalf of the company. It is the professional and proper thing to do. Conversely, a positive recommendation would be putting the company at risk of a bad hire, which is not a good outcome.
(If it helps you worry less: if the only answer it was acceptable for you to give was "yes", they wouldn't have bothered asking you at all...)
add a comment |
up vote
8
down vote
While you are still working at the company, you should work to the same standard as you would if you weren't currently serving your notice period (though you are only human, and motivation will probably slip towards the end).
Hiring / recruitment is a key part of any job, and arguably the most important thing any company can do. You have been asked to be a part of the recruitment process, so you should do it to the best of your ability.
If you believe that the best thing for the company would be to reject the candidate - then you should recommend that the candidate is rejected. That isn't "speaking bad about your replacement", that is doing your job on behalf of the company. It is the professional and proper thing to do. Conversely, a positive recommendation would be putting the company at risk of a bad hire, which is not a good outcome.
(If it helps you worry less: if the only answer it was acceptable for you to give was "yes", they wouldn't have bothered asking you at all...)
add a comment |
up vote
8
down vote
up vote
8
down vote
While you are still working at the company, you should work to the same standard as you would if you weren't currently serving your notice period (though you are only human, and motivation will probably slip towards the end).
Hiring / recruitment is a key part of any job, and arguably the most important thing any company can do. You have been asked to be a part of the recruitment process, so you should do it to the best of your ability.
If you believe that the best thing for the company would be to reject the candidate - then you should recommend that the candidate is rejected. That isn't "speaking bad about your replacement", that is doing your job on behalf of the company. It is the professional and proper thing to do. Conversely, a positive recommendation would be putting the company at risk of a bad hire, which is not a good outcome.
(If it helps you worry less: if the only answer it was acceptable for you to give was "yes", they wouldn't have bothered asking you at all...)
While you are still working at the company, you should work to the same standard as you would if you weren't currently serving your notice period (though you are only human, and motivation will probably slip towards the end).
Hiring / recruitment is a key part of any job, and arguably the most important thing any company can do. You have been asked to be a part of the recruitment process, so you should do it to the best of your ability.
If you believe that the best thing for the company would be to reject the candidate - then you should recommend that the candidate is rejected. That isn't "speaking bad about your replacement", that is doing your job on behalf of the company. It is the professional and proper thing to do. Conversely, a positive recommendation would be putting the company at risk of a bad hire, which is not a good outcome.
(If it helps you worry less: if the only answer it was acceptable for you to give was "yes", they wouldn't have bothered asking you at all...)
answered 8 hours ago
BittermanAndy
1,522110
1,522110
add a comment |
add a comment |
up vote
1
down vote
I agree with other answers that say that you should provide a clear and thruthful feedback.
Only I suggest that you make sure you and your director and HR all agree on what kind of a person they want to hire. For example, if your director and HR are OK with hiring a capable junior, and you asked some advanced technical questions, then probably it is not correct to outright reject the candidate. In any case, you should clearly state your doubts, but don't say that the candidate is not good for the position until you clearly understand what others expect from that position.
In fact, I do not know how hiring process is organized in your company, but in some organisations you might have some kind of "veto right" to completely reject a candidate. In situations when you are not leaving such a right is sensble, as you would work with a successfull candidate, and so you may have all rights to reject a candidate that did not suit your expectations.
But you are leaving, so the candidate will work with your director, not you. So I think that you should not use such "veto right" in this case. State your doubts clearly, but make it clear that it is director and HR who should make the final decision.
New contributor
add a comment |
up vote
1
down vote
I agree with other answers that say that you should provide a clear and thruthful feedback.
Only I suggest that you make sure you and your director and HR all agree on what kind of a person they want to hire. For example, if your director and HR are OK with hiring a capable junior, and you asked some advanced technical questions, then probably it is not correct to outright reject the candidate. In any case, you should clearly state your doubts, but don't say that the candidate is not good for the position until you clearly understand what others expect from that position.
In fact, I do not know how hiring process is organized in your company, but in some organisations you might have some kind of "veto right" to completely reject a candidate. In situations when you are not leaving such a right is sensble, as you would work with a successfull candidate, and so you may have all rights to reject a candidate that did not suit your expectations.
But you are leaving, so the candidate will work with your director, not you. So I think that you should not use such "veto right" in this case. State your doubts clearly, but make it clear that it is director and HR who should make the final decision.
New contributor
add a comment |
up vote
1
down vote
up vote
1
down vote
I agree with other answers that say that you should provide a clear and thruthful feedback.
Only I suggest that you make sure you and your director and HR all agree on what kind of a person they want to hire. For example, if your director and HR are OK with hiring a capable junior, and you asked some advanced technical questions, then probably it is not correct to outright reject the candidate. In any case, you should clearly state your doubts, but don't say that the candidate is not good for the position until you clearly understand what others expect from that position.
In fact, I do not know how hiring process is organized in your company, but in some organisations you might have some kind of "veto right" to completely reject a candidate. In situations when you are not leaving such a right is sensble, as you would work with a successfull candidate, and so you may have all rights to reject a candidate that did not suit your expectations.
But you are leaving, so the candidate will work with your director, not you. So I think that you should not use such "veto right" in this case. State your doubts clearly, but make it clear that it is director and HR who should make the final decision.
New contributor
I agree with other answers that say that you should provide a clear and thruthful feedback.
Only I suggest that you make sure you and your director and HR all agree on what kind of a person they want to hire. For example, if your director and HR are OK with hiring a capable junior, and you asked some advanced technical questions, then probably it is not correct to outright reject the candidate. In any case, you should clearly state your doubts, but don't say that the candidate is not good for the position until you clearly understand what others expect from that position.
In fact, I do not know how hiring process is organized in your company, but in some organisations you might have some kind of "veto right" to completely reject a candidate. In situations when you are not leaving such a right is sensble, as you would work with a successfull candidate, and so you may have all rights to reject a candidate that did not suit your expectations.
But you are leaving, so the candidate will work with your director, not you. So I think that you should not use such "veto right" in this case. State your doubts clearly, but make it clear that it is director and HR who should make the final decision.
New contributor
edited 8 hours ago
New contributor
answered 8 hours ago
Petr
1114
1114
New contributor
New contributor
add a comment |
add a comment |
up vote
-1
down vote
Not telling them truthfully that you wouldn’t hire this candidate, that would be disloyal, damaging, not doing your job.
How this can be seen wouldn’t matter to me. If they ask for my opinion and then don’t like it, that’s not my problem, that is someone else’s problem. But most likely your HR and hiring manager are reasonable people and will realise that they are getting good advise.
add a comment |
up vote
-1
down vote
Not telling them truthfully that you wouldn’t hire this candidate, that would be disloyal, damaging, not doing your job.
How this can be seen wouldn’t matter to me. If they ask for my opinion and then don’t like it, that’s not my problem, that is someone else’s problem. But most likely your HR and hiring manager are reasonable people and will realise that they are getting good advise.
add a comment |
up vote
-1
down vote
up vote
-1
down vote
Not telling them truthfully that you wouldn’t hire this candidate, that would be disloyal, damaging, not doing your job.
How this can be seen wouldn’t matter to me. If they ask for my opinion and then don’t like it, that’s not my problem, that is someone else’s problem. But most likely your HR and hiring manager are reasonable people and will realise that they are getting good advise.
Not telling them truthfully that you wouldn’t hire this candidate, that would be disloyal, damaging, not doing your job.
How this can be seen wouldn’t matter to me. If they ask for my opinion and then don’t like it, that’s not my problem, that is someone else’s problem. But most likely your HR and hiring manager are reasonable people and will realise that they are getting good advise.
answered 15 hours ago
gnasher729
78.6k34143248
78.6k34143248
add a comment |
add a comment |
Lifelong Scholar is a new contributor. Be nice, and check out our Code of Conduct.
Lifelong Scholar is a new contributor. Be nice, and check out our Code of Conduct.
Lifelong Scholar is a new contributor. Be nice, and check out our Code of Conduct.
Lifelong Scholar is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f122891%2fshould-i-say-anything-bad-about-candidates-wholl-be-replacing-me%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
@downvoter(s) Pls explain your action.
– Badhan Ganesh
15 hours ago
6
Yes, It'll be really helpful if you can tell me the reason for downvotes, I'll edit the question as required.
– Lifelong Scholar
12 hours ago
7
Keep in mind that downvotes must reflect the question itself, not OP's actions or beliefs. If you disagree with them, write an answer or take it to chat.
– rath
10 hours ago
8
@rath Downvotes "must" not reflect anything other than the downvoter's wish to use it.
– pipe
9 hours ago
11
@pipe Please read the hover label over the vote down button: This question does not show any research effort; it is unclear or not useful. It doesn't say This question says something I disagree with. The premise of many questions can be seen as problematic, regardless, this is the place they come to get help.
– rath
9 hours ago