Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

In an earlier node, I outlined a few of my experiences with being laid off. It took me some time to get over it emotionally. In doing so (and in working at other companies since then), I've learned a few things:

  • Learn how to learn new tools quickly. Also, give yourself a grounding in several tools, not just a single one. Be able to articulate why, for example, you prefer Perl over alternate technologies. Be able to do so with experience in the tools you don't like. You will be able to speak with more authority during technical interviews and who knows, you might also learn something in the process.

  • Learn tools, yes, but focus on learning the underlying skills. While there are differences between all programming languages, certain skills can be applied to any language. Yes, each language has idioms that must be mastered, but there are broader design skills as well. I'm thinking of things like good class design, well-crafted database structures, security issues for distributed applications, and so on. In other words, don't be so attached to a language that you're unwilling to learn a new one. In my experience, many companies will train you in their tools--if you can demonstrate that you've mastered the skills to use those tools well.

  • No matter how good you are, there's always someone better or more knowledgeable. By this, I mean that some of these underlying skills include listening to your users, your managers, and your sponsors. Eveyone you work with can teach you something. Negotiation and diplomacy are just as important as mastering arcane syntactic details. No matter who you work for, it's still a business.

  • No matter how successful you are in your current position, you are (sadly) expendable in today's business environment--even if you own your own company.

  • Regardless of your current job satisfaction level, do not allow your personal identity to be defined by who you work for or what you work on. Doing so will only increase the shock and subsequent recovery time when you are laid off.

  • Participate in your local community. Go to user groups, post on message boards, write articles and so on. Not only will this expose you to new problems and ways of doing things, it will also give you the chance to meet and network with other people in your local area. Collect business cards, chat with other people at various events. You'll never know when a random encounter could lead to a new offer or a safety net.

  • Keep your resumé current, preferably on your home computer. Keep personal files backed up and ready to pull. Manage the amount of clutter at the office so that you're able to depart quickly and with little fuss.

  • Also, develop a portfolio and keep your references up to date. Most agencies want at least three references; cultivate at least twice that many (preferably from different companies). Certain jobs want certain references and if you have several to choose from, you can provide a tailored list to your respective clients/employers.

  • Stay aware of positions available in your local area. Take time to scan the Help Wanted and the online postings. Again, this will provide a sense of where you might look should the axe fall.

  • Above all else: be nice (and honest) to your co-workers, your managers, and your clients/users. Do not mouth off, do not get overly antagonistic nor overly uppity. You never know when you might be working for that person you, er, don't really care for.

  • Keep your career options open. You may be a code monkey now, but a prospective employer might (if you've demonstrated these skills) want you as a business analyst, a technical writer, a tester, or even (horror of horrors) a manager.

    Case in point: When I was looking for a new position after my lay off experience, I was offered a very nice sum to test medical equipment. I eventually chose not to accept the offer, but it was nice to see that my skills were adaptable to other businesses and positions.

  • Learn who the local--and good--recruitment agencies are. For example, I asked my HR people who they use to fill IT positions and gave that short list to my wife. In turn, she was able to find a new position very quickly. It's a slightly different position and uses different tools...however, she believe it's the right fit and they're willing to train her because of her experience.

    In addition, I have a copy of that list in case the axe falls on me.

  • Proactively manage your recruitment. In many cases, it's obvious that a company will need to do something. You know when layoffs are looming. If you're suspicious that one in the offing, then be proactive and start looking before the cuts fall. Indeed, a couple of friends of mine were able to lay themselves off and negotiate better departure packages in doing so.

  • Attend job fairs and go on interviews. It's good practice and you just might find something new.

  • Don't job-hop. If you take a position and it's not working out, then you need to leave (of course). However, if you do that repeatedly, then hiring folks are going to start wondering why. My rule of thumb is ~3 years, though if I do find the perfect, dream job...I'll happily stay planted until they cart my ashes away.

  • When interviewing, don't bad mouth your current (former) employer. There are problems at any job and part of the interview process is designed to see how you respond to certain chalenges.

  • Also, do not lie about your skills or your experience. People are checking up and word gets around. Nuff' said.

Finally, if (when?) you are laid off...DON'T take it personally--even if they try to make it so. Yes, it'll hurt. You'll need to vent and you'll need to recover. However, if you accept the decision with as much grace as possible and depart without burning bridges, you may possibly a) get called back or b) be able to form a strategic relationship with your former employer later.

Also, if you are fortunate to find a new position right away and have a bit of your severance left, you might consider taking a few days before you start your new position. You can let go the pain and allow yourself to start the next step of grief recovery. (Note: In some US companies, you can "manage" the size of your severance by building up your vacation time to the maximum you can carry over from year to year. It's not much, but an extra two weeks' pay never hurts.)

Getting laid off is no picnic, but in the end...it's just business and it is *just* a job. Your ability to survive losing it will depend strictly on your flexibility. Take pride in your work, do your best possible work for each project, and keep reality in mind. Everyone is expendable. Accept that and move on.

--f


In reply to Re: Surviving Layoffs by footpad
in thread Surviving Layoffs by seeker

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others romping around the Monastery: (2)
As of 2024-04-25 21:11 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found