New hire was terminated from previous company [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
15
down vote
favorite
We have a new team member that happens to be a colleague of a friend from another company. This new guy was terminated from the other company due to his work ethic (slacking in work, etc.).
Should I warn or tell my manager about it?
new-hires
closed as off-topic by Jim G., gnat, Jan Doggen, David S., jcmeloni Sep 3 '14 at 12:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Jim G., gnat, David S., jcmeloni
suggest improvements |Â
up vote
15
down vote
favorite
We have a new team member that happens to be a colleague of a friend from another company. This new guy was terminated from the other company due to his work ethic (slacking in work, etc.).
Should I warn or tell my manager about it?
new-hires
closed as off-topic by Jim G., gnat, Jan Doggen, David S., jcmeloni Sep 3 '14 at 12:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Jim G., gnat, David S., jcmeloni
5
“Should I warn or tell my manager about it?†Did it ever occur to you that your manager is well aware of the new hire’s background yet hired them anyway? Also, are you sure you got the full story of what happened?
– JakeGould
Sep 3 '14 at 1:51
suggest improvements |Â
up vote
15
down vote
favorite
up vote
15
down vote
favorite
We have a new team member that happens to be a colleague of a friend from another company. This new guy was terminated from the other company due to his work ethic (slacking in work, etc.).
Should I warn or tell my manager about it?
new-hires
We have a new team member that happens to be a colleague of a friend from another company. This new guy was terminated from the other company due to his work ethic (slacking in work, etc.).
Should I warn or tell my manager about it?
new-hires
edited Sep 3 '14 at 0:36
bdesham
7272717
7272717
asked Sep 2 '14 at 16:04
eliseobeltran
18515
18515
closed as off-topic by Jim G., gnat, Jan Doggen, David S., jcmeloni Sep 3 '14 at 12:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Jim G., gnat, David S., jcmeloni
closed as off-topic by Jim G., gnat, Jan Doggen, David S., jcmeloni Sep 3 '14 at 12:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions asking for advice on what to do are not practical answerable questions (e.g. "what job should I take?", or "what skills should I learn?"). Questions should get answers explaining why and how to make a decision, not advice on what to do. For more information, click here." – Jim G., gnat, David S., jcmeloni
5
“Should I warn or tell my manager about it?†Did it ever occur to you that your manager is well aware of the new hire’s background yet hired them anyway? Also, are you sure you got the full story of what happened?
– JakeGould
Sep 3 '14 at 1:51
suggest improvements |Â
5
“Should I warn or tell my manager about it?†Did it ever occur to you that your manager is well aware of the new hire’s background yet hired them anyway? Also, are you sure you got the full story of what happened?
– JakeGould
Sep 3 '14 at 1:51
5
5
“Should I warn or tell my manager about it?†Did it ever occur to you that your manager is well aware of the new hire’s background yet hired them anyway? Also, are you sure you got the full story of what happened?
– JakeGould
Sep 3 '14 at 1:51
“Should I warn or tell my manager about it?†Did it ever occur to you that your manager is well aware of the new hire’s background yet hired them anyway? Also, are you sure you got the full story of what happened?
– JakeGould
Sep 3 '14 at 1:51
suggest improvements |Â
5 Answers
5
active
oldest
votes
up vote
53
down vote
No.
- You only have anecdotal evidence for the reason behind his firing, assuming your friend is ethical enough not to leak confidential information.
- Even if correct, you don't know if there are any underlying factors behind any poor performance (eg. not given enough work, consistently given work well below ability level, treated badly by seniors)
- Even if there were no mitigating circumstances, it's not for you to undermine him before he's even had a chance to prove himself in a fresh work environment.
- And if he turns out to perform acceptably in your company, you will have created a perception in your boss's mind that you are prepared to bad-mouth coworkers unjustifiably. Not good for future office politics.
20
Yeah, if he's already started, you have no business bad-mouthing him. If you're part of the interview process, then I think this is fair game.
– Jared
Sep 2 '14 at 16:32
1
Re anecdotal evidence: the question also seems to assume the friend in question has some special knowledge of the firing (ie, was involved somehow). If they were colleagues, this seems unlikely.
– thegrinner
Sep 2 '14 at 21:02
8
Who knows? Maybe being fired triggered him to get his act together, and there will be no further problems. Wouldn't want to sabotage that.
– AlbeyAmakiir
Sep 2 '14 at 23:50
1
I had a conversation with the new hire, and I ask him directly what's the reason he left the previous company. He said he was supposed to participate to an international event and he must be on-leave for 2 weeks but he wasn't allowed. That is why he resigned. Doesn't matter now whatever the reason - I hope he become a valued team member of our department.
– eliseobeltran
Sep 3 '14 at 10:19
suggest improvements |Â
up vote
12
down vote
These kinds of questions come loaded with tons of baggage.
Were you solicited for opinions on the new hire? Did you recommend the new hire? Is your friend in a management position such that they would know, not by rumor or conjecture, the reason this hire was let go?
I'm sure some other folks will recommend letting your manager know. I, however, will say it's nunya. As in none of your business. Unless you were in the chain of command or had direct information about this hire then you really don't know why your new colleague was terminated.
Maybe he is a lazy bum who never did any work. Or maybe the company wasn't a good fit and he felt undertrained/incapable of the workload. Maybe he had issues with his manager or team members. Maybe someone on the team was a jerk and threw him under the bus. Maybe personality wise he wasn't a good fit. Maybe the job he was hired for wasn't the job he ended up being given to do. Maybe they found out he was looking elsewhere...
My point is you don't really know. You don't know WHY he was let go and you don't know the process used on your current employer's end to vet why he was let go from a previous employer. For whatever reason, on both counts, he passed the interview and was hired. Trying to poison the well early about this new worker isn't going to benefit anyone. If he ends up being a lazy bum - why didn't you say something during the hiring process? If he ends up being a hard worker then you look like a jerk who tried to blacken his name! There's no benefit here, for you or the company, in bringing this up at this point.
My suggestion would be to forget it altogether. Often times when folks who didn't like someone know someone who works with that person at a new company they'll continuously pry into that unliked person's performance. It's beyond this question but I think it's human nature - when we don't like someone for whatever reason we want them to fail in other places as well. This is poison for you and the other person. Let it go, judge this new worker on his performance at your company and in your team.
suggest improvements |Â
up vote
4
down vote
Has this person been hired?
Yes? Then keep it to yourself. This inevitably came up during their interview, and they gave a good enough answer to get hired anyways.
No? Then bring it up. At least where I've worked, trying to find friends and old coworkers that work with a candidate is very common. Your boss is not an idiot (I hope) and will take your information into account alongside other info. The friend of a subordinate isn't exactly a reliable source, but it might help your boss look into it more closely than they might otherwise. Maybe your friend was mistaken. Maybe not.
More information means better decisions.
Once they're employed though, your boss should have all the info they need right in front of them.
suggest improvements |Â
up vote
4
down vote
There are MANY reasons why people may be terminated from a job. There are equally varied reasons that might be "rumored" about such a situation. Often those don't necessarily mix and, at least in the US, most employers wouldn't comment on the reason an employee is no longer with them anyway. (link) Further there's usually far more to a story than is generally talked about around the water cooler.
A while back, I very nearly terminated an employee based upon information provided by two others. The details aren't germane. Fortunately the employee was out sick the day I planned on taking action. This gave me an extra day to ponder the situation and reach out to others in the affected group because something just sounded a little off. What I found out made me stop and go back to the original reporters.
Ultimately the story provided had been made up by one of them and told to the other, who not only completely believed it but reported it as if they had first hand knowledge. The situation was such that if it had been true then immediate dismissal was the only responsible course. Had I fired this person I would have been doing the wrong thing.
When hiring people I feel you should allow some latitude for the past. In other words, the reasons surrounding their departure from a job may not be a reflection of their character; it might not even be wholly true. Regardless being dismissed can lead to a fair amount of introspection which can lead to a positive change.
Now if this person was "terminally" lazy - meaning they've bounced from job to job with the same issue - then it would be absolutely apparent by their work history. Those types tend not to last long at many companies; this is one of the reasons that numerous short term employments are usually a big red flag during the hiring process. Which the boss should have noticed and considered.
Point is, don't worry about it. You didn't hire them, someone else did. Presumably you aren't in charge of their continued employment, someone else is. Which means it's up to the actual responsible party here to ensure their decision was a valid one and to take action if it turns out to be incorrect.
By throwing your 2 cents in, all you would do is possibly color the boss' perception by spreading rumor and, potentially, making a career limiting move (CLM) if you turn out to be completely wrong. Or, worse, opening yourself up to potential legal trouble if the other employee found out what you had said and was willing to go to court over it.
2
having many short term jobs is quite common in some fields... It's also getting increasingly common in general here as labour law requires companies to give people a permanent position rather than a fixed term contract after 18 months (and as a result many companies automatically terminate everyone after 18 months, usually making up some reason of "unsatisfactory job performance" or "does not work well in the team" as an official excuse...).
– jwenting
Sep 3 '14 at 6:49
1
Now we all want to know what happened to the person making up the story!
– gnasher729
Sep 3 '14 at 9:44
@gnasher729: Considering they're relatively "young" (very early 20s) and they are otherwise a good employee, I elected to do a written Performance Improvement Plan that included a "nice" talk about how made up stories have a way of seriously backfiring on them. Part of the plan included an apology to the person in question. Seems to have worked out.
– NotMe
Sep 3 '14 at 13:53
suggest improvements |Â
up vote
3
down vote
Your new colleague might have been totally demotivated at his old job, for all we know. Don't pass judgment on him, let him be himself. If he is still as demotivated as ever, your management will crack down on him quickly enough.
suggest improvements |Â
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
53
down vote
No.
- You only have anecdotal evidence for the reason behind his firing, assuming your friend is ethical enough not to leak confidential information.
- Even if correct, you don't know if there are any underlying factors behind any poor performance (eg. not given enough work, consistently given work well below ability level, treated badly by seniors)
- Even if there were no mitigating circumstances, it's not for you to undermine him before he's even had a chance to prove himself in a fresh work environment.
- And if he turns out to perform acceptably in your company, you will have created a perception in your boss's mind that you are prepared to bad-mouth coworkers unjustifiably. Not good for future office politics.
20
Yeah, if he's already started, you have no business bad-mouthing him. If you're part of the interview process, then I think this is fair game.
– Jared
Sep 2 '14 at 16:32
1
Re anecdotal evidence: the question also seems to assume the friend in question has some special knowledge of the firing (ie, was involved somehow). If they were colleagues, this seems unlikely.
– thegrinner
Sep 2 '14 at 21:02
8
Who knows? Maybe being fired triggered him to get his act together, and there will be no further problems. Wouldn't want to sabotage that.
– AlbeyAmakiir
Sep 2 '14 at 23:50
1
I had a conversation with the new hire, and I ask him directly what's the reason he left the previous company. He said he was supposed to participate to an international event and he must be on-leave for 2 weeks but he wasn't allowed. That is why he resigned. Doesn't matter now whatever the reason - I hope he become a valued team member of our department.
– eliseobeltran
Sep 3 '14 at 10:19
suggest improvements |Â
up vote
53
down vote
No.
- You only have anecdotal evidence for the reason behind his firing, assuming your friend is ethical enough not to leak confidential information.
- Even if correct, you don't know if there are any underlying factors behind any poor performance (eg. not given enough work, consistently given work well below ability level, treated badly by seniors)
- Even if there were no mitigating circumstances, it's not for you to undermine him before he's even had a chance to prove himself in a fresh work environment.
- And if he turns out to perform acceptably in your company, you will have created a perception in your boss's mind that you are prepared to bad-mouth coworkers unjustifiably. Not good for future office politics.
20
Yeah, if he's already started, you have no business bad-mouthing him. If you're part of the interview process, then I think this is fair game.
– Jared
Sep 2 '14 at 16:32
1
Re anecdotal evidence: the question also seems to assume the friend in question has some special knowledge of the firing (ie, was involved somehow). If they were colleagues, this seems unlikely.
– thegrinner
Sep 2 '14 at 21:02
8
Who knows? Maybe being fired triggered him to get his act together, and there will be no further problems. Wouldn't want to sabotage that.
– AlbeyAmakiir
Sep 2 '14 at 23:50
1
I had a conversation with the new hire, and I ask him directly what's the reason he left the previous company. He said he was supposed to participate to an international event and he must be on-leave for 2 weeks but he wasn't allowed. That is why he resigned. Doesn't matter now whatever the reason - I hope he become a valued team member of our department.
– eliseobeltran
Sep 3 '14 at 10:19
suggest improvements |Â
up vote
53
down vote
up vote
53
down vote
No.
- You only have anecdotal evidence for the reason behind his firing, assuming your friend is ethical enough not to leak confidential information.
- Even if correct, you don't know if there are any underlying factors behind any poor performance (eg. not given enough work, consistently given work well below ability level, treated badly by seniors)
- Even if there were no mitigating circumstances, it's not for you to undermine him before he's even had a chance to prove himself in a fresh work environment.
- And if he turns out to perform acceptably in your company, you will have created a perception in your boss's mind that you are prepared to bad-mouth coworkers unjustifiably. Not good for future office politics.
No.
- You only have anecdotal evidence for the reason behind his firing, assuming your friend is ethical enough not to leak confidential information.
- Even if correct, you don't know if there are any underlying factors behind any poor performance (eg. not given enough work, consistently given work well below ability level, treated badly by seniors)
- Even if there were no mitigating circumstances, it's not for you to undermine him before he's even had a chance to prove himself in a fresh work environment.
- And if he turns out to perform acceptably in your company, you will have created a perception in your boss's mind that you are prepared to bad-mouth coworkers unjustifiably. Not good for future office politics.
edited Sep 2 '14 at 16:30
answered Sep 2 '14 at 16:24
Julia Hayward
12k53438
12k53438
20
Yeah, if he's already started, you have no business bad-mouthing him. If you're part of the interview process, then I think this is fair game.
– Jared
Sep 2 '14 at 16:32
1
Re anecdotal evidence: the question also seems to assume the friend in question has some special knowledge of the firing (ie, was involved somehow). If they were colleagues, this seems unlikely.
– thegrinner
Sep 2 '14 at 21:02
8
Who knows? Maybe being fired triggered him to get his act together, and there will be no further problems. Wouldn't want to sabotage that.
– AlbeyAmakiir
Sep 2 '14 at 23:50
1
I had a conversation with the new hire, and I ask him directly what's the reason he left the previous company. He said he was supposed to participate to an international event and he must be on-leave for 2 weeks but he wasn't allowed. That is why he resigned. Doesn't matter now whatever the reason - I hope he become a valued team member of our department.
– eliseobeltran
Sep 3 '14 at 10:19
suggest improvements |Â
20
Yeah, if he's already started, you have no business bad-mouthing him. If you're part of the interview process, then I think this is fair game.
– Jared
Sep 2 '14 at 16:32
1
Re anecdotal evidence: the question also seems to assume the friend in question has some special knowledge of the firing (ie, was involved somehow). If they were colleagues, this seems unlikely.
– thegrinner
Sep 2 '14 at 21:02
8
Who knows? Maybe being fired triggered him to get his act together, and there will be no further problems. Wouldn't want to sabotage that.
– AlbeyAmakiir
Sep 2 '14 at 23:50
1
I had a conversation with the new hire, and I ask him directly what's the reason he left the previous company. He said he was supposed to participate to an international event and he must be on-leave for 2 weeks but he wasn't allowed. That is why he resigned. Doesn't matter now whatever the reason - I hope he become a valued team member of our department.
– eliseobeltran
Sep 3 '14 at 10:19
20
20
Yeah, if he's already started, you have no business bad-mouthing him. If you're part of the interview process, then I think this is fair game.
– Jared
Sep 2 '14 at 16:32
Yeah, if he's already started, you have no business bad-mouthing him. If you're part of the interview process, then I think this is fair game.
– Jared
Sep 2 '14 at 16:32
1
1
Re anecdotal evidence: the question also seems to assume the friend in question has some special knowledge of the firing (ie, was involved somehow). If they were colleagues, this seems unlikely.
– thegrinner
Sep 2 '14 at 21:02
Re anecdotal evidence: the question also seems to assume the friend in question has some special knowledge of the firing (ie, was involved somehow). If they were colleagues, this seems unlikely.
– thegrinner
Sep 2 '14 at 21:02
8
8
Who knows? Maybe being fired triggered him to get his act together, and there will be no further problems. Wouldn't want to sabotage that.
– AlbeyAmakiir
Sep 2 '14 at 23:50
Who knows? Maybe being fired triggered him to get his act together, and there will be no further problems. Wouldn't want to sabotage that.
– AlbeyAmakiir
Sep 2 '14 at 23:50
1
1
I had a conversation with the new hire, and I ask him directly what's the reason he left the previous company. He said he was supposed to participate to an international event and he must be on-leave for 2 weeks but he wasn't allowed. That is why he resigned. Doesn't matter now whatever the reason - I hope he become a valued team member of our department.
– eliseobeltran
Sep 3 '14 at 10:19
I had a conversation with the new hire, and I ask him directly what's the reason he left the previous company. He said he was supposed to participate to an international event and he must be on-leave for 2 weeks but he wasn't allowed. That is why he resigned. Doesn't matter now whatever the reason - I hope he become a valued team member of our department.
– eliseobeltran
Sep 3 '14 at 10:19
suggest improvements |Â
up vote
12
down vote
These kinds of questions come loaded with tons of baggage.
Were you solicited for opinions on the new hire? Did you recommend the new hire? Is your friend in a management position such that they would know, not by rumor or conjecture, the reason this hire was let go?
I'm sure some other folks will recommend letting your manager know. I, however, will say it's nunya. As in none of your business. Unless you were in the chain of command or had direct information about this hire then you really don't know why your new colleague was terminated.
Maybe he is a lazy bum who never did any work. Or maybe the company wasn't a good fit and he felt undertrained/incapable of the workload. Maybe he had issues with his manager or team members. Maybe someone on the team was a jerk and threw him under the bus. Maybe personality wise he wasn't a good fit. Maybe the job he was hired for wasn't the job he ended up being given to do. Maybe they found out he was looking elsewhere...
My point is you don't really know. You don't know WHY he was let go and you don't know the process used on your current employer's end to vet why he was let go from a previous employer. For whatever reason, on both counts, he passed the interview and was hired. Trying to poison the well early about this new worker isn't going to benefit anyone. If he ends up being a lazy bum - why didn't you say something during the hiring process? If he ends up being a hard worker then you look like a jerk who tried to blacken his name! There's no benefit here, for you or the company, in bringing this up at this point.
My suggestion would be to forget it altogether. Often times when folks who didn't like someone know someone who works with that person at a new company they'll continuously pry into that unliked person's performance. It's beyond this question but I think it's human nature - when we don't like someone for whatever reason we want them to fail in other places as well. This is poison for you and the other person. Let it go, judge this new worker on his performance at your company and in your team.
suggest improvements |Â
up vote
12
down vote
These kinds of questions come loaded with tons of baggage.
Were you solicited for opinions on the new hire? Did you recommend the new hire? Is your friend in a management position such that they would know, not by rumor or conjecture, the reason this hire was let go?
I'm sure some other folks will recommend letting your manager know. I, however, will say it's nunya. As in none of your business. Unless you were in the chain of command or had direct information about this hire then you really don't know why your new colleague was terminated.
Maybe he is a lazy bum who never did any work. Or maybe the company wasn't a good fit and he felt undertrained/incapable of the workload. Maybe he had issues with his manager or team members. Maybe someone on the team was a jerk and threw him under the bus. Maybe personality wise he wasn't a good fit. Maybe the job he was hired for wasn't the job he ended up being given to do. Maybe they found out he was looking elsewhere...
My point is you don't really know. You don't know WHY he was let go and you don't know the process used on your current employer's end to vet why he was let go from a previous employer. For whatever reason, on both counts, he passed the interview and was hired. Trying to poison the well early about this new worker isn't going to benefit anyone. If he ends up being a lazy bum - why didn't you say something during the hiring process? If he ends up being a hard worker then you look like a jerk who tried to blacken his name! There's no benefit here, for you or the company, in bringing this up at this point.
My suggestion would be to forget it altogether. Often times when folks who didn't like someone know someone who works with that person at a new company they'll continuously pry into that unliked person's performance. It's beyond this question but I think it's human nature - when we don't like someone for whatever reason we want them to fail in other places as well. This is poison for you and the other person. Let it go, judge this new worker on his performance at your company and in your team.
suggest improvements |Â
up vote
12
down vote
up vote
12
down vote
These kinds of questions come loaded with tons of baggage.
Were you solicited for opinions on the new hire? Did you recommend the new hire? Is your friend in a management position such that they would know, not by rumor or conjecture, the reason this hire was let go?
I'm sure some other folks will recommend letting your manager know. I, however, will say it's nunya. As in none of your business. Unless you were in the chain of command or had direct information about this hire then you really don't know why your new colleague was terminated.
Maybe he is a lazy bum who never did any work. Or maybe the company wasn't a good fit and he felt undertrained/incapable of the workload. Maybe he had issues with his manager or team members. Maybe someone on the team was a jerk and threw him under the bus. Maybe personality wise he wasn't a good fit. Maybe the job he was hired for wasn't the job he ended up being given to do. Maybe they found out he was looking elsewhere...
My point is you don't really know. You don't know WHY he was let go and you don't know the process used on your current employer's end to vet why he was let go from a previous employer. For whatever reason, on both counts, he passed the interview and was hired. Trying to poison the well early about this new worker isn't going to benefit anyone. If he ends up being a lazy bum - why didn't you say something during the hiring process? If he ends up being a hard worker then you look like a jerk who tried to blacken his name! There's no benefit here, for you or the company, in bringing this up at this point.
My suggestion would be to forget it altogether. Often times when folks who didn't like someone know someone who works with that person at a new company they'll continuously pry into that unliked person's performance. It's beyond this question but I think it's human nature - when we don't like someone for whatever reason we want them to fail in other places as well. This is poison for you and the other person. Let it go, judge this new worker on his performance at your company and in your team.
These kinds of questions come loaded with tons of baggage.
Were you solicited for opinions on the new hire? Did you recommend the new hire? Is your friend in a management position such that they would know, not by rumor or conjecture, the reason this hire was let go?
I'm sure some other folks will recommend letting your manager know. I, however, will say it's nunya. As in none of your business. Unless you were in the chain of command or had direct information about this hire then you really don't know why your new colleague was terminated.
Maybe he is a lazy bum who never did any work. Or maybe the company wasn't a good fit and he felt undertrained/incapable of the workload. Maybe he had issues with his manager or team members. Maybe someone on the team was a jerk and threw him under the bus. Maybe personality wise he wasn't a good fit. Maybe the job he was hired for wasn't the job he ended up being given to do. Maybe they found out he was looking elsewhere...
My point is you don't really know. You don't know WHY he was let go and you don't know the process used on your current employer's end to vet why he was let go from a previous employer. For whatever reason, on both counts, he passed the interview and was hired. Trying to poison the well early about this new worker isn't going to benefit anyone. If he ends up being a lazy bum - why didn't you say something during the hiring process? If he ends up being a hard worker then you look like a jerk who tried to blacken his name! There's no benefit here, for you or the company, in bringing this up at this point.
My suggestion would be to forget it altogether. Often times when folks who didn't like someone know someone who works with that person at a new company they'll continuously pry into that unliked person's performance. It's beyond this question but I think it's human nature - when we don't like someone for whatever reason we want them to fail in other places as well. This is poison for you and the other person. Let it go, judge this new worker on his performance at your company and in your team.
answered Sep 2 '14 at 16:26


Nahkki
4,6281927
4,6281927
suggest improvements |Â
suggest improvements |Â
up vote
4
down vote
Has this person been hired?
Yes? Then keep it to yourself. This inevitably came up during their interview, and they gave a good enough answer to get hired anyways.
No? Then bring it up. At least where I've worked, trying to find friends and old coworkers that work with a candidate is very common. Your boss is not an idiot (I hope) and will take your information into account alongside other info. The friend of a subordinate isn't exactly a reliable source, but it might help your boss look into it more closely than they might otherwise. Maybe your friend was mistaken. Maybe not.
More information means better decisions.
Once they're employed though, your boss should have all the info they need right in front of them.
suggest improvements |Â
up vote
4
down vote
Has this person been hired?
Yes? Then keep it to yourself. This inevitably came up during their interview, and they gave a good enough answer to get hired anyways.
No? Then bring it up. At least where I've worked, trying to find friends and old coworkers that work with a candidate is very common. Your boss is not an idiot (I hope) and will take your information into account alongside other info. The friend of a subordinate isn't exactly a reliable source, but it might help your boss look into it more closely than they might otherwise. Maybe your friend was mistaken. Maybe not.
More information means better decisions.
Once they're employed though, your boss should have all the info they need right in front of them.
suggest improvements |Â
up vote
4
down vote
up vote
4
down vote
Has this person been hired?
Yes? Then keep it to yourself. This inevitably came up during their interview, and they gave a good enough answer to get hired anyways.
No? Then bring it up. At least where I've worked, trying to find friends and old coworkers that work with a candidate is very common. Your boss is not an idiot (I hope) and will take your information into account alongside other info. The friend of a subordinate isn't exactly a reliable source, but it might help your boss look into it more closely than they might otherwise. Maybe your friend was mistaken. Maybe not.
More information means better decisions.
Once they're employed though, your boss should have all the info they need right in front of them.
Has this person been hired?
Yes? Then keep it to yourself. This inevitably came up during their interview, and they gave a good enough answer to get hired anyways.
No? Then bring it up. At least where I've worked, trying to find friends and old coworkers that work with a candidate is very common. Your boss is not an idiot (I hope) and will take your information into account alongside other info. The friend of a subordinate isn't exactly a reliable source, but it might help your boss look into it more closely than they might otherwise. Maybe your friend was mistaken. Maybe not.
More information means better decisions.
Once they're employed though, your boss should have all the info they need right in front of them.
answered Sep 2 '14 at 20:29


Telastyn
33.9k977120
33.9k977120
suggest improvements |Â
suggest improvements |Â
up vote
4
down vote
There are MANY reasons why people may be terminated from a job. There are equally varied reasons that might be "rumored" about such a situation. Often those don't necessarily mix and, at least in the US, most employers wouldn't comment on the reason an employee is no longer with them anyway. (link) Further there's usually far more to a story than is generally talked about around the water cooler.
A while back, I very nearly terminated an employee based upon information provided by two others. The details aren't germane. Fortunately the employee was out sick the day I planned on taking action. This gave me an extra day to ponder the situation and reach out to others in the affected group because something just sounded a little off. What I found out made me stop and go back to the original reporters.
Ultimately the story provided had been made up by one of them and told to the other, who not only completely believed it but reported it as if they had first hand knowledge. The situation was such that if it had been true then immediate dismissal was the only responsible course. Had I fired this person I would have been doing the wrong thing.
When hiring people I feel you should allow some latitude for the past. In other words, the reasons surrounding their departure from a job may not be a reflection of their character; it might not even be wholly true. Regardless being dismissed can lead to a fair amount of introspection which can lead to a positive change.
Now if this person was "terminally" lazy - meaning they've bounced from job to job with the same issue - then it would be absolutely apparent by their work history. Those types tend not to last long at many companies; this is one of the reasons that numerous short term employments are usually a big red flag during the hiring process. Which the boss should have noticed and considered.
Point is, don't worry about it. You didn't hire them, someone else did. Presumably you aren't in charge of their continued employment, someone else is. Which means it's up to the actual responsible party here to ensure their decision was a valid one and to take action if it turns out to be incorrect.
By throwing your 2 cents in, all you would do is possibly color the boss' perception by spreading rumor and, potentially, making a career limiting move (CLM) if you turn out to be completely wrong. Or, worse, opening yourself up to potential legal trouble if the other employee found out what you had said and was willing to go to court over it.
2
having many short term jobs is quite common in some fields... It's also getting increasingly common in general here as labour law requires companies to give people a permanent position rather than a fixed term contract after 18 months (and as a result many companies automatically terminate everyone after 18 months, usually making up some reason of "unsatisfactory job performance" or "does not work well in the team" as an official excuse...).
– jwenting
Sep 3 '14 at 6:49
1
Now we all want to know what happened to the person making up the story!
– gnasher729
Sep 3 '14 at 9:44
@gnasher729: Considering they're relatively "young" (very early 20s) and they are otherwise a good employee, I elected to do a written Performance Improvement Plan that included a "nice" talk about how made up stories have a way of seriously backfiring on them. Part of the plan included an apology to the person in question. Seems to have worked out.
– NotMe
Sep 3 '14 at 13:53
suggest improvements |Â
up vote
4
down vote
There are MANY reasons why people may be terminated from a job. There are equally varied reasons that might be "rumored" about such a situation. Often those don't necessarily mix and, at least in the US, most employers wouldn't comment on the reason an employee is no longer with them anyway. (link) Further there's usually far more to a story than is generally talked about around the water cooler.
A while back, I very nearly terminated an employee based upon information provided by two others. The details aren't germane. Fortunately the employee was out sick the day I planned on taking action. This gave me an extra day to ponder the situation and reach out to others in the affected group because something just sounded a little off. What I found out made me stop and go back to the original reporters.
Ultimately the story provided had been made up by one of them and told to the other, who not only completely believed it but reported it as if they had first hand knowledge. The situation was such that if it had been true then immediate dismissal was the only responsible course. Had I fired this person I would have been doing the wrong thing.
When hiring people I feel you should allow some latitude for the past. In other words, the reasons surrounding their departure from a job may not be a reflection of their character; it might not even be wholly true. Regardless being dismissed can lead to a fair amount of introspection which can lead to a positive change.
Now if this person was "terminally" lazy - meaning they've bounced from job to job with the same issue - then it would be absolutely apparent by their work history. Those types tend not to last long at many companies; this is one of the reasons that numerous short term employments are usually a big red flag during the hiring process. Which the boss should have noticed and considered.
Point is, don't worry about it. You didn't hire them, someone else did. Presumably you aren't in charge of their continued employment, someone else is. Which means it's up to the actual responsible party here to ensure their decision was a valid one and to take action if it turns out to be incorrect.
By throwing your 2 cents in, all you would do is possibly color the boss' perception by spreading rumor and, potentially, making a career limiting move (CLM) if you turn out to be completely wrong. Or, worse, opening yourself up to potential legal trouble if the other employee found out what you had said and was willing to go to court over it.
2
having many short term jobs is quite common in some fields... It's also getting increasingly common in general here as labour law requires companies to give people a permanent position rather than a fixed term contract after 18 months (and as a result many companies automatically terminate everyone after 18 months, usually making up some reason of "unsatisfactory job performance" or "does not work well in the team" as an official excuse...).
– jwenting
Sep 3 '14 at 6:49
1
Now we all want to know what happened to the person making up the story!
– gnasher729
Sep 3 '14 at 9:44
@gnasher729: Considering they're relatively "young" (very early 20s) and they are otherwise a good employee, I elected to do a written Performance Improvement Plan that included a "nice" talk about how made up stories have a way of seriously backfiring on them. Part of the plan included an apology to the person in question. Seems to have worked out.
– NotMe
Sep 3 '14 at 13:53
suggest improvements |Â
up vote
4
down vote
up vote
4
down vote
There are MANY reasons why people may be terminated from a job. There are equally varied reasons that might be "rumored" about such a situation. Often those don't necessarily mix and, at least in the US, most employers wouldn't comment on the reason an employee is no longer with them anyway. (link) Further there's usually far more to a story than is generally talked about around the water cooler.
A while back, I very nearly terminated an employee based upon information provided by two others. The details aren't germane. Fortunately the employee was out sick the day I planned on taking action. This gave me an extra day to ponder the situation and reach out to others in the affected group because something just sounded a little off. What I found out made me stop and go back to the original reporters.
Ultimately the story provided had been made up by one of them and told to the other, who not only completely believed it but reported it as if they had first hand knowledge. The situation was such that if it had been true then immediate dismissal was the only responsible course. Had I fired this person I would have been doing the wrong thing.
When hiring people I feel you should allow some latitude for the past. In other words, the reasons surrounding their departure from a job may not be a reflection of their character; it might not even be wholly true. Regardless being dismissed can lead to a fair amount of introspection which can lead to a positive change.
Now if this person was "terminally" lazy - meaning they've bounced from job to job with the same issue - then it would be absolutely apparent by their work history. Those types tend not to last long at many companies; this is one of the reasons that numerous short term employments are usually a big red flag during the hiring process. Which the boss should have noticed and considered.
Point is, don't worry about it. You didn't hire them, someone else did. Presumably you aren't in charge of their continued employment, someone else is. Which means it's up to the actual responsible party here to ensure their decision was a valid one and to take action if it turns out to be incorrect.
By throwing your 2 cents in, all you would do is possibly color the boss' perception by spreading rumor and, potentially, making a career limiting move (CLM) if you turn out to be completely wrong. Or, worse, opening yourself up to potential legal trouble if the other employee found out what you had said and was willing to go to court over it.
There are MANY reasons why people may be terminated from a job. There are equally varied reasons that might be "rumored" about such a situation. Often those don't necessarily mix and, at least in the US, most employers wouldn't comment on the reason an employee is no longer with them anyway. (link) Further there's usually far more to a story than is generally talked about around the water cooler.
A while back, I very nearly terminated an employee based upon information provided by two others. The details aren't germane. Fortunately the employee was out sick the day I planned on taking action. This gave me an extra day to ponder the situation and reach out to others in the affected group because something just sounded a little off. What I found out made me stop and go back to the original reporters.
Ultimately the story provided had been made up by one of them and told to the other, who not only completely believed it but reported it as if they had first hand knowledge. The situation was such that if it had been true then immediate dismissal was the only responsible course. Had I fired this person I would have been doing the wrong thing.
When hiring people I feel you should allow some latitude for the past. In other words, the reasons surrounding their departure from a job may not be a reflection of their character; it might not even be wholly true. Regardless being dismissed can lead to a fair amount of introspection which can lead to a positive change.
Now if this person was "terminally" lazy - meaning they've bounced from job to job with the same issue - then it would be absolutely apparent by their work history. Those types tend not to last long at many companies; this is one of the reasons that numerous short term employments are usually a big red flag during the hiring process. Which the boss should have noticed and considered.
Point is, don't worry about it. You didn't hire them, someone else did. Presumably you aren't in charge of their continued employment, someone else is. Which means it's up to the actual responsible party here to ensure their decision was a valid one and to take action if it turns out to be incorrect.
By throwing your 2 cents in, all you would do is possibly color the boss' perception by spreading rumor and, potentially, making a career limiting move (CLM) if you turn out to be completely wrong. Or, worse, opening yourself up to potential legal trouble if the other employee found out what you had said and was willing to go to court over it.
answered Sep 3 '14 at 1:08
NotMe
20.9k55695
20.9k55695
2
having many short term jobs is quite common in some fields... It's also getting increasingly common in general here as labour law requires companies to give people a permanent position rather than a fixed term contract after 18 months (and as a result many companies automatically terminate everyone after 18 months, usually making up some reason of "unsatisfactory job performance" or "does not work well in the team" as an official excuse...).
– jwenting
Sep 3 '14 at 6:49
1
Now we all want to know what happened to the person making up the story!
– gnasher729
Sep 3 '14 at 9:44
@gnasher729: Considering they're relatively "young" (very early 20s) and they are otherwise a good employee, I elected to do a written Performance Improvement Plan that included a "nice" talk about how made up stories have a way of seriously backfiring on them. Part of the plan included an apology to the person in question. Seems to have worked out.
– NotMe
Sep 3 '14 at 13:53
suggest improvements |Â
2
having many short term jobs is quite common in some fields... It's also getting increasingly common in general here as labour law requires companies to give people a permanent position rather than a fixed term contract after 18 months (and as a result many companies automatically terminate everyone after 18 months, usually making up some reason of "unsatisfactory job performance" or "does not work well in the team" as an official excuse...).
– jwenting
Sep 3 '14 at 6:49
1
Now we all want to know what happened to the person making up the story!
– gnasher729
Sep 3 '14 at 9:44
@gnasher729: Considering they're relatively "young" (very early 20s) and they are otherwise a good employee, I elected to do a written Performance Improvement Plan that included a "nice" talk about how made up stories have a way of seriously backfiring on them. Part of the plan included an apology to the person in question. Seems to have worked out.
– NotMe
Sep 3 '14 at 13:53
2
2
having many short term jobs is quite common in some fields... It's also getting increasingly common in general here as labour law requires companies to give people a permanent position rather than a fixed term contract after 18 months (and as a result many companies automatically terminate everyone after 18 months, usually making up some reason of "unsatisfactory job performance" or "does not work well in the team" as an official excuse...).
– jwenting
Sep 3 '14 at 6:49
having many short term jobs is quite common in some fields... It's also getting increasingly common in general here as labour law requires companies to give people a permanent position rather than a fixed term contract after 18 months (and as a result many companies automatically terminate everyone after 18 months, usually making up some reason of "unsatisfactory job performance" or "does not work well in the team" as an official excuse...).
– jwenting
Sep 3 '14 at 6:49
1
1
Now we all want to know what happened to the person making up the story!
– gnasher729
Sep 3 '14 at 9:44
Now we all want to know what happened to the person making up the story!
– gnasher729
Sep 3 '14 at 9:44
@gnasher729: Considering they're relatively "young" (very early 20s) and they are otherwise a good employee, I elected to do a written Performance Improvement Plan that included a "nice" talk about how made up stories have a way of seriously backfiring on them. Part of the plan included an apology to the person in question. Seems to have worked out.
– NotMe
Sep 3 '14 at 13:53
@gnasher729: Considering they're relatively "young" (very early 20s) and they are otherwise a good employee, I elected to do a written Performance Improvement Plan that included a "nice" talk about how made up stories have a way of seriously backfiring on them. Part of the plan included an apology to the person in question. Seems to have worked out.
– NotMe
Sep 3 '14 at 13:53
suggest improvements |Â
up vote
3
down vote
Your new colleague might have been totally demotivated at his old job, for all we know. Don't pass judgment on him, let him be himself. If he is still as demotivated as ever, your management will crack down on him quickly enough.
suggest improvements |Â
up vote
3
down vote
Your new colleague might have been totally demotivated at his old job, for all we know. Don't pass judgment on him, let him be himself. If he is still as demotivated as ever, your management will crack down on him quickly enough.
suggest improvements |Â
up vote
3
down vote
up vote
3
down vote
Your new colleague might have been totally demotivated at his old job, for all we know. Don't pass judgment on him, let him be himself. If he is still as demotivated as ever, your management will crack down on him quickly enough.
Your new colleague might have been totally demotivated at his old job, for all we know. Don't pass judgment on him, let him be himself. If he is still as demotivated as ever, your management will crack down on him quickly enough.
answered Sep 2 '14 at 20:15
Vietnhi Phuvan
68.9k7118254
68.9k7118254
suggest improvements |Â
suggest improvements |Â
5
“Should I warn or tell my manager about it?†Did it ever occur to you that your manager is well aware of the new hire’s background yet hired them anyway? Also, are you sure you got the full story of what happened?
– JakeGould
Sep 3 '14 at 1:51