Co-worker looking for job 8

[controlnovice]

I lent my company laptop to a co-worker while at a remote site, so he could check his email. No big deal.

In the evening, I log on, and go straight to my Yahoo! email account and blindly click on the first email.

It stated that "...my application was recieved and an offer would be made...". I then realized that my co-worker didn't log out and I just read his email about a job offer at a new company. I quickly logged off of Yahoo!.

I believe this is between him and our manager. However, we have an important milestone in my project in 6 weeks, and I don't want to have to train a new engineer in the 5th week when he leaves (I don't know if it will be the 5th week, or the 12th week, or anywhere in between).

His leaving will really affect my project and goals. My manager will be understanding of this, but it also means that a milestone lasting 3 weeks will extend to 6 weeks, if I can't get someone trained.

When we return, I would like to request my manager assign another engineer, but I don't have the 'ammo' to really make the request without bringing this up. He's a good engineer, but we have 3 others that are just as good, if not better, but not familiar with this project or process.

Any ideas?

______________________________________________________________________________
This is normally the space where people post something insightful.

 

[MadMango]

I would talk to the co-worker that borrowed the laptop and tell him that you saw the email since he didn't log-out of his account. Try to gage how serious he is in leaving, then use that information to talk with your manager (or another engineer you have in mind) to get another body to work with your co-worker for a smoother turn-over before he leaves.

"Art without engineering is dreaming; Engineering without art is calculating."

Have you read faq731-376 to make the best use of Eng-Tips Forums?

 

[TheTick]

You didn't come by this information by any inappropriate means. It's yours to use. Your coworker is either an idiot or he wants you to know (or both).

Since you know, you may as well act in your own best interests. Make sure you have proper support for your project.

 

[SomptingGuy]

TheTick might have put his finger on it. Many engineers are too introverted to march into the boss and make demands. One alternative is to "leak" the information to a colleague who will suffer if you leave and hope he/she will tell the boss. I've had unsolicited offers from a cometitor recently and talked them through with some of the guys over too many beers. One asked me if I minded him telling my director. The other put on his size nines and did it without asking. So the boss knows I'm not too happy and I've been spared the embarrasment of looking like a whinger.

- Steve

 

[swertel]

Conversely, he's just seeing what the market is like to know if he's making what he's worth. He has no intentions of leaving your company and you going in to talk to the boss may put a black mark on his future, forcing him to leave.

I would talk to your coworker about what you found. Personally, I wouldn't start out mentioning that you read his email, but that you heard he was looking for other opportunities and want to know what his schedule is to determine the impact on the project.

If you get him talking about the impact to the project rather than defending yourself from snooping (even though you weren't) or have him defensive about keeping this a secret, he'll probably give you less partial truths.

--Scott

http://wertel.eng.pro

 

[EddyC]

controlnovice,

I'm not religious, but I refer you to "The Golden Rule" (I can amplify if you are not familiar with it.)

 

[Gymmeh]

I dont know about you guys/girls....

I have my resume posted on monster and careerbuilders, and get some calls and emails about jobs all the time.


for awhile I had them posted when I was not looking for a job and I was still getting phone calls and emails. There is also the possibility he is checking his value for an upcoming review or something.

... There are enough odds that I could be nothing... and there is a old saying about assuming

You may want to confront him first, before making a big deal out of it.

Star to Eddy

 

[GregLamberson]

The best time to look for a job is when you have one. How can you blame a guy for looking, but do understand your concern. Most companies will request references, such as the last job (yours). I would take MadMango's advice, talk to the guy - he may be interested in something else but be the kind that won't leave you in a bind and had no intention of leaving until after your milestone is met. Who knows, but if he is planning to leave sooner, then go to the manager and request a new engineer.

Greg Lamberson, BS, MBA
Consultant - Upstream Energy
Website:

http://www.oil-gas-consulting.com

 

[aspearin1]

I would come completely clean with your coworker. Ask him directly what his plans are. More than likely he's just fishing... and sometimes it takes a lot of fishing to catch what you want, so he may very well be with you for the duration. To be careful, though, rather than replace your coworker, I would request an additional body, perhaps in the form of a tech, a little less qualified than the engineer, but capable of learning the basics. Between the two of you, you may be able to learn what your coworker knows and cover your bases if he decides to jump ship.

In a way, you're lucky. Most people don't get such warning before hammer falls.

Aaron A. Spearin
ASQ CSSBB
Engineering Six-S'$

http://www.Engineering6ss.com

"The only constant in life is change." -Bruce Lee

 

[melone]

Butt out.... It's his/her business. You management gets paid to deal with these situations when the arise. Jumping the gun, and tattling on your co-worker will only end badly for everyone.

 

[GregLamberson]

melone

I don't think anyone recommended tattling on the co-worker, only having a discussion with him to find out what his plans are.

If you are the one responsible and know of a potential situation where your project could be hurt, you have an obligation as a professional not to butt out. You need to manage situations not bury your head.

Greg Lamberson, BS, MBA
Consultant - Upstream Energy
Website:

http://www.oil-gas-consulting.com

 

[SylvestreW]

How close are you to your co-worker. What's wrong with sitting down and talking off-the-record. If he's serious, explain that you'd be screwed and try to work out with him how to phase him out of the project while not bringing up his impending departure.

I don't see the need to involve anyone else until after you've talked with him.

-
Aercoustics.com

 

[RossABQ]

Please note that the co-worker used a company laptop, therefore he has no expectation of privacy.

 

[josephv]

Why worry about something that might not happen? For example, the co-worker may get the offer and not accept. Or his new job might not start in months. Or the manager could have a great job offer and will be leaving in 3 weeks. Or one of you could win the lottery tomorrow.

In general, worrying about the future does not work, since you have about zero control.

Also, I liked the tip about the golden rule.

 

[GregLamberson]

josephv

Why worry about something that nmight not happen? Why plan, why do risk assessments?

If someone worked for me and an issue came up that may have a negative effect on his project, I would ask the question - what are you doing about it? And if the answer is - I'm not worrying about it because it may not happen - bang you are gone.

Greg Lamberson, BS, MBA
Consultant - Upstream Energy
Website:

http://www.oil-gas-consulting.com

 

[BJC]

"In general, worrying about the future does not work, since you have about zero control."
Good point.
In general you should only worry about things you can do something about.
If you can do something, do it.
So do it and don't worry- It makes Alfred E Newman pretty smart after all.

 

[josephv]

Hi Greg, your point on risk assessment is well taken. Just a few additional thoughts.

People leave companies all the time (no one can control this), and many times it happens in the middle of important projects. It is the responsibility of managers and engineers to be ready when and if this happens. Even if no one ever saw the e-mail about the job offer, they should be prepared. I distinguish this from worrying (which generally means to torment one self with thoughts), and interferes with finding a solution to a problem.

 

[jeebusmn]

I am with the golden rule on this one.

 

[vc66]

GregLamberson wrote,"... bang you are gone."

Man, you'd shoot your employee? Tough boss...

In all seriousness though--I agree with Greg. You need to figure out what you do, and don't have control over. Then you need to remedy, as best you can, what you do control. Otherwise, it's your own fault.

Good luck, and I hope it doesn't affect anything.

Regards,

V

Mechanical Engineer
"When I am working on a problem, I do not think of beauty, but when I've finished, if the solution is not beautiful, I know it is wrong."

- R. Buckminster Fuller

 

[Gymmeh]

I just talked to a project manager I work with from another company and got a good lesson on this.

Depending on the rules of the state, it may be more benifitial for your boss to fire him on the spot before he has a chance to "quit", so the company does not have to pay for unemployment benifits.

The project manager i work with was like your "co-worker" and just checking jobs, his boss got wind of it some how, and fired him on the next day.

Reason being, the losses as a result of firing the employee are less then paying the unemployment benifits, and it keeps managment on top of the other employees.