Computer Jobs -- How to Resign Professionally?
MikeDawg asks: "I submitted a letter of resignation yesterday, and today I'm at home posting stories to my weblog and Slashdot. I gave my employer two weeks notice, and almost immediately, I had my accounts disabled, and my permissions revoked on all the computers at my work, which makes me unable to do anything in my position of being a 'Systems Analyst/Systems Administrator'. I spoke with the HR rep, and gave her my notice yesterday, then I spoke with her today about what had happened to my access, and they honored my resignation... 2 weeks early. (Luckily, I'm compensated in pay for the next two weeks). What I want to know is, how do you computer and IT professionals out there put in your notice of resignation (if you are with a permanent employer, and not contractual), and not get immediately shutdown, and shunned away from the computers? The CIO immediately thought I was going to do something terrible to the system, and destroy accounts, and any other activity that I have access to, but I was giving him notice that I was leaving. What is the professional thing to do?"
You're a liability. You got paid. Be happy.
Umm... what's the question again? You did resign in a professional manner. Is this the first real IT job that you've had? What you experienced is standard operating procedure for any organization with even a half-assed security policy. They aren't your computers. Why are you taking it so personally, esp. since they've paid you for those two extra weeks? ::rolls eyes::
What I'd like to know is what didn't make the front page because this got posted instead?
Entrepreneur : (noun), French for "unemployed"
Up front Disclaimer: I am a disgruntled former employee of a Telco... laid off after 21 years
You, kind sir, proffered as professional a resignation as necessary. There are no reciprocal gaurantees, and in the IT field it is more typical than not for you to be treated nearly as if you were a criminal.
Systems you once managed for your employers now are at risk. Former peers are now potential spies. Do not be surprised to be treated like you have some sort of exotic, deadly, contagious disease. Don't expect anything for references other than affirmation you actually did work there.
This is the fine world of trust we have achieved as a civilised and evolved society. Trust not.
I will still always give professional courtesy (e.g., sufficient lead time for resignation) but I've left the corporate world with a sour aftertaste.... It sucks, that's just the way it is.
Based on how you described it, you probably did nothing wrong, and they probably did the right thing.
Companies are rightfully paranoid that a departing employee -- particulalrly one with root access -- may decide to do something nasty on the way out the door. This doesn't mean that *you* would do this, just that they can't take a chance. Of course, if you had intended to do something nasty, you could easily have set it up before tendering your resignation. The best thing to do is act like a professional and understand that what is in your best interest and in the company's best interest are no longer related.
If you got an extra two weeks of vacation, enjoy it.
When I quit HP, they paid me to stay at home for two weeks, and my unused vacation. 6 weeks of pay for 2 weeks at home. Time to recover and prepare for my new job, buy new clothes, and figure out the bus schedule.
The professional way to handle it is to stop whining and enjoy.
That's why I've been a consultant for, oh, just about the past 12 years (more or less). Even then, I've tried to be good and give 2-4 weeks notice when I saw things going south, but management never seems to appreciate it, even when you offer to document your work, make yourself available for a brief period after you leave, etc...
Fact is, the moment you resign, you're a pariah. But if you do all the "right things" you can at least leave with a good conscience, and not have anything come back to haunt you.
Nothing is inexplicable; only unexplained -Tom Baker, Doctor Who
From what it sounds like, you did everything right. Two weeks is an excellent time period to offer notice. You aren't dropping out of the company like a light, but you also aren't creating an awkward, 'lame-duck' position where the company has to keep the thought in the back of thier head that you're leaving in say, 6 months.
Also, unless you're leaving for competition, the CIO probably didn't think you were going to 'do something malicious'. It's probably just company protocol, and in fact, I would consider the quick removal of accounts to be 'lite'. I've worked at companies where as the minute strikes your time of non-employment, 2 security guards immedietally escort you out of the building.
In lieu of keeping you there during your resignation period. Why risk liability over a couple of weeks of sysadmin pay?
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
If it were me I would approach my boss and let them know that if they won't give access, there is no need to be around, but you'll be happy to answer any questions that they might have. However tell them that you'd be more than happy to twiddle your thumbs (in a more polite way) for a couple weeks until you've given them their time. I'd guess that they'd be willing to let you go with pay. If not, Worst case you can try to improve your solitaire skills for a couple weeks and get paid to do it.
In any case, both sides have fulfilled their obligations to each other in a completely professional way.
Scott
The places I have worked at and turned in a two week notice, it is usually a 2 week scramble to document everything I did and get some poor unqualified individual up to speed. On the last day I make sure that the new person in charge either disables all accounts I had access to or make sure that they changed the passwords.
You want to eliminate any possibility of doubt if something goes wrong after you leave.
So while their actions may be seem extreme, it really is for your protection as much as it is for theirs. I would not take it so personally.
This is EXACTLY how is should be handled. Do NOT let a leaving Sys Admin on you system. You did nothing wrong. They did nothing wrong. Enjoy your end of the year festivities.
This
You did everything professionally, it's the company that is acting immature.
The company isn't 'acting immature', they're acting to limit their security liability. This is Standard Operating Procedure in pretty much every large organization I've worked for, especially if you're high enough up the corporate ziggurat to be privy to confidential information or sensitive software/data.
Take the money, enjoy your two weeks paid vacation, and don't sweat it. It's not personal, it's business!
The gift of death metal does not smile on the good looking.
The next time you resign from an IT job, there are things you should do before you resign if you want them to be done --
-- take your personal computer hardware, books, papers, etc. home. Before you resign. If you wait to do it after, you may not even get the chance (as they show you the door), and you'll have to argue with them about it. And if you do get the chance, they may be watching you like a hawk and you'll have to justify it.
-- same goes for your personal files and stuff you want to save. Save it off the network and computers BEFORE you resign. Some companys are cool about this sort of thing, some aren't. Don't take the risk. This is also a good thing to do if you get wind of layoffs coming up that you might be involved in.
-- If there are any projects you want to see completed before you leave, complete them before you resign.
He made a professional resignation, they said no thanks but paid him for two weeks anyways. This is standard business practice and was financially beneficial for him. (two weeks free pay?)
What he's probably dealing with is the feeling of rejection: if they could drop him on a days notice was he really needed? He'll just have to be honest with himself about that but he will just have to get over that himself. Again its a standard business practice in many places and not a reflection of his character.
-everphilski-
I think the reason this is done, even though it seems illogical on the surface, is because of the company's responsibility to act with "due diligence" in regards to security.
If you as an employee compromise the system or act as some sort of mole or corporate spy, after you're busted when the shareholders come down on your boss, he can say "Well, hey we had no way of knowing he was bent, we had no warning that this was about to happen. It could happen to anybody."
But let's say you put in your resignation, then backdoored their network on your way out because they didn't cut off your access until two weeks later. This time when the Powers That Be come looking for blood, your boss is SOL: he could try saying "well, we had no idea he was bent..." but the shareholders are just going to respond "He had just turned in his resignation! He was on his way out the door! Why did he still have access?" And your boss becomes the next one on the chopping block, and depending on the nature of the business possibly liable for fines as well.
So really your boss, and your boss' boss, and probably their boss' boss, all the way up the CoC, are just covering their asses by pulling your access as soon as they get a hint that you're not going to be a career employee.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Honestly, it could be worse. There are shitheads that would have cut off his access and demanded that he come in for two weeks anyway.
The cake is a pie
Unfortunately, they have insurance liability if they don't lock you out and something bad happens.
Because someone, somewhere gave notice and then got mad during the last 2 weeks and did something nasty.
She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
One guy I worked with wrote a three page letter detailing the company and all senior management's flaws. Depending on how big the pond you live in is, this is not a good idea ...
C
If they expect you to remain for those last 2 weeks with no access to the systems, break out a pad and pen and start writing down all of the things you know you have access too, and work with your co-workers to ensure you no longer have access to anything.
On top of that, spend some time to pass along info on those systems you are the only one that knows anything about.
Beyond that it's not bad to sit around and make it known your available to answer questions before your time is up.
Face it, the more professional you are, the better your former employer and co workers will feel about you later. That never hurts when looking for references.
Eschew Obfuscation
Of course, the master's response to the effervescent personality of the nearly-parted is to respond, "Why, yes, it's GREAT that you'll be gone so soon! I only wish we could make it faster!"
;)
That should at least deflate their sails a bit
I Browse at +4 Flamebait
Open Source Sysadmin
It's a matter of perspective.
The employer is doing themselves, but more importantly YOU a favor with this behaviour.
Why? Well besides the nice paid two weeks off, you are now officially not responsible.
If they didn't do this you are vulnerable to accusations at a later date if something goes wrong with a server that is traced to a point in time you were on your two weeks to bail.
Yes it's possible you could have sabotaged something before giving notice, and tough luck if they catch you at it. However you can't be held responsible for anything from the point of resignation onwards if removed as he described.
--- I've completed diagnosis of your problem and can classify it as a YOYO...You're On Your Own
I have seen those 2 weeks you longed for turn into a living hell. You are a lame duck in those 2 weeks. No wants to speak to you, except to talk about the weather, or how some dimwit in purchasing just ordered a ton of toilet paper. No one gives you any constructive work to do, just 'write down everything you know about anything this company does, and that you had a hand in programming, over say, the last 99 years...' You were saved from someones timetabled exit startegy that would have had you doing 35 debriefings, none of which would have been attended, and seven planning for the future meetings, none of which you could care a hoot about.
That 2 week notice, and its subsequent conversion into personal TV time, saved you from a whole lot of really boring nothing. Now, go home, get in the car, switch off the GPS and head in which ever direction you see a hawk flying, and don't stop for anything other than gas for 500 miles.
Live a little; the new job is just as likely to suck the life out of you as the old one did.
Resignation letters should never be more than:
No more need be stated. As a new person was starting the following Monday, it would have been smarter for me to stay those 2 weeks training the new guy. As it was, they get to do it themselves.It is almost impossible to actually explain fully and honestly why you're leaving without sounding bitter or nasty. Gee, Mr BossMan, I'm getting a 50% pay raise, 75% shorter commute, working with new technology, doing interesting (very not-boring) stuff, and the new place uses source code control too!
At least most places are not as bad as banks: if they overhear you talking about leaving, that will be your last day at work.
You forgot to mention that South Australia has one of the highest numbers in the world of serial killers per capita. I never really understood why that was so until I read your post.
Ho! Haha! Guard! Turn! Parry! Dodge! Spin! Ha! Thrust!
"Don't have a cow, man."
:) But since I'm a manager, I probably wouldn't get that lucky. If you were a sysadmin on my staff, I'd pull your access immediately and put you on leave, too. It wouldn't be personal, or any kind of reflection on your work. It's business, and it's good security policy.
I've been in the sysadmin and security fields for a number of years. As many others have written, this is SOP in many shops and is exactly what they *should* do. Yes, it's also true that a really nefarious person would have already planted all of his/her backdoors, trojans, whatever, well before resigning, but not all nefarious people are that smart, and some people just get a bug up their ass at the last minute and do something foolish (it's not common, but neither is it non-existent). Plus, if you think they might be a bad actor, or you just have really stringent security policies, you can put the person on leave and immediately start a security audit of everything they touched or might have touched.
If I gave notice tomorrow,I would not only expect to be immediately placed on administrative leave, I would hope for it. Beats showing up for work those two weeks
As far as how to resign professionally, speaking as a person who was rank and file for a long time and who currently managages a security staff of eight people, a letter of resignation should contain just the facts, and the bare minimum at that. It should state that you are resigning, and the effective date. That's it. And it should be written in polite and professional language. It doesn't need to say why (that's none of anyone's business), and really shouldn't. If you just can't help yourself, "To pursue other opportunities" is the best thing to say.
Whether you have another job or not, or where, or why (really) you're quitting is not any of anyone's business. If people ask, you can tell them, or you can politely respond that you'd rather not say. Or tell a small lie and say you're going to pursue other opportunities, but aren't yet sure what shape they will take. Even if one of my staff resigned and told me that, and I later found out they had another job with our competition, I wouldn't be angry (OK, maybe I'm not your average boss, either); they don't owe me that truth. Why you're resigning and what you're going to do next is your business. All you owe your company apart from a letter of resignation as described above is a final two weeks of work up to your usual standard, if they do choose to have you work rather than put you on administrative leave.
This is their problem, not yours. You have been professional, they have not. Move on.
Seriously. Only in America does one assume that an employee who quits or is terminated would try to do sabotage if there has been no animosity before. Really, why would anyone sabotage stuff after they hand in their resignation? There was plenty of time before. People who routinely revoke employees privileges before the last day of employment should have their heads examined. They are a bit more paranoid than what is healthy. (Paranoia and believing in conspiracies seems to be a major culturar trait in the US, so it might be difficult to find a shrink to actually cure you, but still.)
I run a small = 100 person consulting firm and for the most part, when people resign, we let all positions (including systems) work out their notice, with 1 exception. We rarely let sales people remain around because once they've resigned, their interests and efforts are generally oriented towards their new job and not towards laying the foundations for sales they'll never finish. I almost always let them go immediately, with a couple of exceptions. Retirement is one and spousal transfer is another. In those cases, it is a transition planned over several months and generally involves a smooth and gradual handoff of accounts.
When my Systems guys resign, we generally involve them in the interviewing of successors process and we have them help up phase them out of our systems.
When consultants resign and they don't currently have accounts that they are managing, we take them up on the offer to leave anytime in the 2 weeks and let them leave for their new job immediately. They generally give 'up to 2 weeks notice.'
Once piece of advice to anyone resigning. Unless you detest the organization and would never return, don't burn any bridges. Remain helpful and cordial or you will have insured that you never return.
Suppose you were an idiot. And suppose you were a member of congress. But then I repeat myself. -- Mark Twain
Otherwise I can't imagine why you would care. And let me sharpen that point by stating that for the vast majority of you out there, the old saw to not burn your bridges is in fact nonsense. The likelihood of you returning to an ex employer except in the circumstances of immediately returning as a contractor, are near zero. You want to leave and they don't want you back.
So, get over the hurt feelings stage, take your 2 week sabbatical to lay whatever prep work with your new employer you can. In fact, I make it rule to never state whether I'm actually taking a new job or not. That's not your old employer's information to chew on. If they ask, politely be vague about 'a few options cooking right now'. This helps avoid the discussion of non competes, etc. Basically it's not their business.
Next, if you're locked out then you are also free to refuse to help them in any other way as well. If some soon to be ex coworker comes to you with a question related to your former duties you should answer them in only the most general terms or not at all. Otherwise you're warranting a system you have no control over and may have already been changed in some way. I would also send a note to HR stating that since you have been locked out you cannot be held responsible for the condition, failure, state of any device from that date forward, for any reason. If you have to do it in a hardcopy letter because you're locked out, all the better.
Also remember to tell them to change your voicemail password on a given date.
Google DoD STD 5220.22-M and get a piece of freeware that can wipe your disks per that standard. Tell your soon to be ex employer you are doing that unless of course there are published rules that forbid you from wiping your disk.
Throw the card keys, swipe cards and cable locks over your shoulder, wave buh bye to the square badge and leave.
I used to work at an executive outplacement firm where we'd basically help people who got laid off, usually en masse (a service their former employer paid for). My job was mainly resume and cover letter-centric, but our consultants actually went to the locations and helped with the big, 'So long and thanks for all the fish" meetings.
Most people are just depressed and angry, but some people will try to get revenge. One of our consultants was meeting with an exec, told him he was being laid off, and he basically ran out of the room and started making lots of phone calls to cancel a big event he had coordinated for his company. So while it's not fair to most people and I do think it's generally like pouring salt in a fresh wound, some people will strike back as hard as they can, and those edge cases are the reason the 'good' ones get the same shaft.
1) Morale of other staff - There is nothing worse than hearing somebody tell you that grass is greener where they're going.
I think there's nothing worse for the other staff than seeing how shabby a company treats someone who has worked hard helping the company meet its goals. I've been at three companies where someone on my team was disappeared by HR. In all cases the person leaving wanted to do the right thing to minimize the effect of their departure. It was a depressing blow to the entire team when the company acted on the assumption that the person -- and by extention, any member of the team -- was an immanent threat, despite the person's history of loyal professionalism and service.
I've always included on my resignation letter a list of tasks I need to complete before leaving. That tells them that you haven't lost your work ethic, you're just moving, and it shows them that they still need you.
I resigned from a job last year, and my boss honored my two week notice because he could see he still needed me to finish up my projects. This is a guy with a reputation for showing people the door.
Of course it's also important to communicate a positive reason that you are leaving. For instance, I left my job in California because I couldn't afford a house in that state. Yeah I had some beefs, but I didn't mention them. I made them clearly understand I was not leaving out of dislike for the job. It's to your advantage to do this even if you actually do dislike your job.
It turns out that the company I'm with now has entered a partnership with my old company and I find myself working with my old boss as a peer. Leaving on a good note has allowed us to get along pretty well. You never know how the leaf is going to turn so be careful what you say.