20 ways to survive a layoff
Tips for getting back on your feet and into the IT job market from someone who's been there and back
By
Ron Nutter
,
Network World
, 08/25/2008
- Share/Email
- Tweet This
- Print
Editor's note: On Feb. 20, IT manager and Network World columnist Ron Nutter was called into his boss's office and told he was being let go — that day. Once the initial shock wore
off, Nutter launched an aggressive search for new employment in the Kansas City area. Over the next 76 days, Nutter applied
for 85 jobs, and had 16 interviews before landing a new position. He chronicled the job search in a daily blog. Now that he has had some time to reflect on the experience, Nutter offers these 20 tips for surviving a layoff.
Podcast: Ups and downs of the IT job search
Ron Nutter discusses the highs and lows of his IT job search with Keith Shaw
1. As you're getting laid off, be sure to take notes
This can be difficult to do, since losing a job can be a very emotional experience. But while everything is still fresh in
your mind, write down all the details that you can remember. For example, I was told that I would be paid for the full two-week
pay period, plus my remaining vacation and sick time. When my last check arrived, there were discrepancies. Having written
notes helped me when I went back and reminded my former boss and the HR folks of their commitment.
2. Take some time for yourself
Take a few days for yourself. A traumatic event has just happened to you and you need to get over the initial shock before
jumping into the fray to search for a new job.
3. Review the papers from the company that laid you off
Several important things need to be attended to rather quickly. One is how to file for unemployment. Another is how long your
company-paid health insurance will be in force before you have to consider paying for COBRA.
4. Update your resume
This is something that we should all do, but it doesn't always get the attention that it should. I was told a long time ago
that your resume should be more than two pages with a max of three bullet points per employer. That may work in some cases
but not all.
I have found that some recruiters/employers use software that does a "word count" to look for how many times a particular
word, such as Cisco, or a word describing a certain type of experience is listed. I can attest that this is happening to a degree. When I was
looking for a prior job, a recruiter had me just about totally rewrite my resume to specifically list all the different Cisco
hardware that I had worked with. It was interesting to note how the callbacks increased after I did that.
You may find that it may be necessary to keep more than one type of resume depending on the type(s) of jobs you are looking
for, so that the resume is specifically tailored to the type of job you are pursuing.
5. Get a handle on monthly bills
Even though I had a little money put back for a "rainy" day, I went through all my recurring bills to see if there was any
room for saving money. One area I looked at was car and home insurance. I found that by shopping around, I was able to keep
the same level of auto and homeowners coverage while reducing the amount of both bills. I had been thinking about doing it
for a variety of reasons, but being unemployed helped push it to the top of the list.
Partner Content
Blue Stripe Software
www.bluestripe.com/
Improving Application Performance Troubleshooting
Diagnosing why an application is slow is hard, at times taking days or weeks to isolate and resolve. This paper explains the challenges involved using current management tools, provides a 'wish list' for application management and analysis, and explains the need for an application system-wide approach that monitors entire applications, not components.
Download Whitepaper
Virtual Vigilance: Managing Application Performance in Virtual Environments
This paper highlights the impact of virtualization on application performance. "Managing Application Performance in Virtual Environments" states: "Best-in-Class organizations are predominately taking actions around improving visibility across both physical and virtual systems, assessing the business impact of application performance and understanding interdependencies of applications in virtualized environments."
Download Whitepaper
Application Service Requests: The Missing Link for Pragmatic ITSM
Forrester Research analyst Glenn O'Donnell and BlueStripe co-founder Vic Nyman discuss a breakthrough approach to application problem management. Learn the new approach for ITSM problem management, which provides: Rapid isolation of application slow-downs to specific components for quick problem resolution, 24/7 monitoring for proactive notification of potential issues before end users are impacted and much more.
Register for Webcast
Comments (14)
20 tips to survive a layoffBy doward on August 25, 2008, 4:02 pmIt has been awhile since I was unemployed, but I believe the 20 tips are relevant not just to IT jobs, but to all job searches. Good job!
Reply | Read entire comment
Rolodex ContactsBy Anonymous on August 25, 2008, 4:28 pmAlthough subtly mentioned in the article, an important step to do is cold-call all your contacts from that Class of '96 or '01 and see if they have anything on offer? Also,...
Reply | Read entire comment
Tip 19By Anonymous on August 25, 2008, 4:30 pmWhat happened to tip 19. Is that the tip that mentions the importance of attention to detail?
Reply | Read entire comment
Tip 19By Anonymous on August 25, 2008, 4:47 pmShut your face, Pinhead. "19" was intentionally left out to illustrate the importance of detail, but not for you to try and embarass me with. Just pay attention...
Reply | Read entire comment
Surviving a layoff?By Schratboy on August 25, 2008, 4:58 pmMost IT organizations are over-staffed and under-perform. They should all be very very weary! If only the C-level execs really knew what was going on rather than...
Reply | Read entire comment
Tip 19By Anonymous on August 25, 2008, 5:18 pmIt was there. You just did not see it because it was not highlighted like the rest. What a picker.
Reply | Read entire comment
View all comments