Slashdot Mirror
Is it Possible to Age Yourself Out of a Job?
An anonymous reader asks: "I'm a programmer with more than twelve years of experience. In all that time, I've never been a 'senior' developer. I'm competent and I work hard, but I don't think I am quite a senior developer in terms of technical or people skills. More and more I feel that I'm aging myself out a job. By this time, employers expect someone with my experience to have advanced some, and they may not be willing to even talk to me now, thinking that my pay requirements have grown while I have not. Even if I did get hired someplace new, my peers would likely be much younger than me. What do you do when you have an applicant like that? Are my fears legitimate?"
As somebody who hires people at startups and small companies, my take is "maybe". Programmers are a quirky lot, and I try to take each one individually. Although the arrogant ones get the press, there are quite a number that are ridiculously modest, and you might be one of those.
Even if you aren't, there are advantages to age. The biggest one is maturity. There are mistakes that every novice makes that are (I hope!) behind you. Instead of a drama generator, you are probably a drama shock absorber. Even if your people skills aren't as great as you like, they're probably a lot better than 12 years ago. And best of all, you can see that with age comes some self-awareness. Everybody has problems, but in hiring one of the things I really look for is an awareness of your limitations and the ability to manage them yourself.
When evaluating somebody in your situation, one of the big questions I'd have aside from the usual ones (e.g, can you do the work) is whether you are still like the work and are eager to improve. For example, I feel like every programmer should learn a new language once a year. That doesn't mean that you become expert in it, just that you are stretching your brain. Or you might have a side project you're excited about. Or you might be studying software architecture patterns. Anything that proves you aren't a clock-puncher who just isn't sure what else to do.
So I'd say as long as you are doing work you want to do and doing it well, don't sweat it much. You may have to work harder to find a job than some young hotshot, but there are plenty of employers who value a steady producer who won't be a pain in the ass.
be just pay. Younger people tend not to have families and, lacking experience, will often be coerced into working longer hours etc. They could be afraid that you would not put up with such conditions and bolt as soon as you got the chance.
I'm 26, but I am saving like hell because I know that age discrimination is rife in this industry, and the more I save for retirement right now, the less I have to worry about such things.
Monstar L
Good advice.
you can still be the guy everyone goes to when something has to be done right.You're not going to get that from the books.
http://outcampaign.org/
Advanced users are users too!
I hate to say it, but yes. When reviewing a resume, I look for things like growth & ambition. At 12 years experience, I've seen very good architects. If one wasn't even Senior, I'd wonder why that is. Lack of ability? Lack of desire? Clock puncher?
In most cases, I'll never know or have the chance to ask the candidate. Instead, I'll just move to the next 99 resumes in the stack.
I know this isn't what you want to hear, but hopefully honesty will help.
I can't speak from experience about your situation, but I think you might have a number of very good options.
There are probably unlimited more things we could think about. You shouldn't underestimate your 12 years of experience, especially if you are a hard worker, and have a reputation of getting things done.
One last thing, I get the feeling from reading your question that you might have the problem where you keep your head down and work hard, and as a result people forget who you are, and then forget you are even there. The squeaky wheel gets the grease, pardon the cliche. As I pointed out above, it is in your best interest to maintain some level of connection to people around you and above you in your company. The more they see you and talk to you, the more they feel they know you, and the more likely you are to be presented with opportunities for advancement.
I've been a software engineer for 25 years. No issues. There is no expectation that you should move to management at some point. The main expectation is that you are able to keep up with technology as it changes. I've moved from COBOL to C to Java to perl to php. I've used more scripting languages than I can remember. You have to keep moving forward. You never stop reading. Provide mentoring to less experienced engineers. Never hide what you know. It is not good being the curmudgeon that keeps his knowledge to himself. You become a teacher. Understand where projects you have participated in have succeeded or failed. Bring that experience to that table. Most of us have seen more product the never made it to market than have made it. Your experience in knowing why projects succeed is something import you bring to the table. Plus you are the senior guy you get more opportunities to take lead on the cool projects. So I would not worry. I am seeing more people with some gray and missing hair. So as long as you produce, people will continue to hire you.
*sigh* This is part of the problem with programming. This is rarely an issue in any other career (except maybe medicine). For just about any other occupation, candidates who are married with children are more desirable because even though they may have commitments outside of work, other people are relying on them, and they are less likely to make haphazard career decisions. Simply put, they are better long term employees -- they are already committed to their families and are therefore more committed to their employer. Yet, somehow, in IT, a family is often a liability. Something about that is not right in my book.
I'm 26, but I am saving like hell because I know that age discrimination is rife in this industry, and the more I save for retirement right now, the less I have to worry about such things.I'm 28 and I'm out of the programming game. Enron's collapse did me in. I'm going back to school to do something more rewarding with my life, probably major in mathematics and then either teach or maybe try engineering. If the IT industry wasn't so abusive maybe I'd still be in it, but I'm just not that interested in programming anymore (for a living, anyway - I still program in my spare time). You know, if there was ever an industry in the last 50 years that needed to unionize, it's IT...
If you look and compare to other industries, I don't think age in itself could be a disadvantage, as long as you have many successful projects on your CV. On the other side of the coin, however, I think anyone with under 5 years experience is immediately suspect.
There is such a shortage of programmers right now (I have lived in Europe and USA) and most of the available ones are available for a reason. I know a 60 year old who is programming COBOL and earning very good money and happy. I know ASP/XHTML guys who have been unemployed for years. Until programs start writing themselves or there is a massive influx of competetent programmers to college you will be alright.
In my opinion, a Senior Developer role is more a skill related thing than an age related thing. Old people need to work too. You shouldn't worry too much, especially if you are well liked.
I spent a lot of time early on walking through HR and sitting in on interview processes and their aftermaths to let HR understand beyond any uncertain terms where I stand as their manager and what I expect out of them.
I have a simple rule that I demand they abide be. Pay is proportional to proven skill level. Age can kiss my ass. A 14 year old coder of the newest and greatest Firefox or a middle aged old hand, or someone who's been in my organization for x years and who has been lukewarm and suddenly caught on fire, it's all the same. When the light comes on it must shine on a hill and not be stuffed under a rug.
--- Grow a pair, liberals... stop letting the Republicans bully you!
Yet, somehow, in IT, a family is often a liability. Something about that is not right in my book.
The main reason why family is considered a liability in IT is because IT is an industry where sweatshop labour is considered the holy grail.
Families have a tendency to get in the way of Dad working 18 hours a day, and the sorts of demoniacs at the top of the IT management pile don't want that. They want people who are willing to work for as long as possible at a stretch, for as little money as possible, in as poor conditions as possible. It's the entire reason why importing people from India has become so popular.
India at least used to be a third world country, and so you can import someone from there, pay them south of $250 a week without any other sorts of benefits, and expect to get 18 or so hour workdays out of them, and they'll still think they've died and gone to heaven. An American rank and file employee on the other hand is never going to put up with that, but American managers crave being able to treat their staff like that, because it keeps overhead to a bare minimum, which means more money in their pockets...which is also the *only* thing they care about.
That is the reason why IT managers don't want workers having families...it's because they don't want to treat IT workers like human beings. They don't want to *acknowledge* that IT workers are human beings, because doing so means they lose more money than they're comfortable with. The "money is more important than life itself," crowd don't care about anything else...in the end they don't even care about their own lives. All they care about is the size of their bank balance.
Life's not fair - deal with it. Each profession has pros and cons. Quit whining and start learning something new. It's nothing to do with unions, and I've never found it abusive. At least, I don't take any crap. You need to try working in a few places until you find something you like - perhaps contracting.
Wow. What great advice! I almost wish I'd said something about "going back to school to do something more rewarding with my life, probably major in mathematics and then either teach or maybe try engineering" in my original post! You know, assuming you don't have Asperger's Syndrome, I think you'd be terrific management material. Again, thanks for the wonderful advice! Cheers.
Hooters?
Disclaimer: I only read the article title. Please mod me down!
Vehicle Stars used car search is my current project
Good, now after you have vented your spleen let me correct some of your facts and reasoning:
First, based on my experience other countries lead in the "slaverunner" routine. In fact, I would prefer to work for all of the American bosses I have worked for in my career any day compared to some of the British ones I have encountered. With nearly all of Americans the result was the most important item and how many hours did you clock on it was irrelevant. Similarly, most of them defined sane and achieveable deadlines instead of a UK-style deadline which is known to be blown beforehand. There is a reason why Britain is the only EU country to start throwing toys out of the pram every time the EU working time directive is discussed. And you can guess what it is.
Second, any IT person complaining about antisocial working conditions should look at the BioTech industry. They have take the leaf out of the IT book and have gone where no IT PHB Slaver has dreamed to go before. IT is a family friendly calm 9-5 desk job by comparison.
Baker's Law: Misery no longer loves company. Nowadays it insists on it
http://www.sigsegv.cx/
Wow, get me a job with your former or current employers. Every project I've been on since 1999 has been behind schedule before the first line of code had even been thought of. Most were delivered early or on time with the last 5 years all being based on face time only, even if telecommuting or flex time were given lip service.
/. community reads /. during work hours.... ;)
If you take those two statements together, you'll see something had to give, and it was working hours. Only in the past 2 years have I forced the issue of the 40 hour work week back into my life. I'm now somewhere between 40-45 hours a week instead of 70-95, and I still manage to deliver those ridiculous deadlines. What I have noticed is that I am now working 6-8 straight hours a day (as compared to the estimated 3 hours of value add work in some government survey I'm too lazy to pull up - that's due to email, phone calls, meetings, people interrupting you, the web, bathroom breaks, coffee breaks, etc) If you think about it, that makes a lot of sense, as most of the
But, I'll make this comment, after many years in IT, my upward career swing is stalling. Does that have to do with my attitude? Undoubtedly, as traveling more than 10% is out of the question for the next couple of years (kids can have that effect). It also has to do with the realization that I'm already at an apex of sorts, and there's really no opportunities for advancement without career development of the sort that involves major changes (sr architect (technical) -> technical director (mgmt)). Unfortunately, the particular type job I'm looking for typically involves geographically spread out operations and 25%+ travel. This causes a conundrum where I have to decide whether to travel, or work below my level. Pick your evil.
I'm sure I'm not the only "older programmer" out there that's realized this.
The cesspool just got a check and balance.
Unionizing IT is not the answer. A couple of years ago I did a contract in a unionized IT shop and it was a nightmare! Incompetent, unqualified, downright lazy people in critical support positions, and protected by the union. Unions cater to the lowest common denominator and cause quality and productivity to suffer. Individuals have as much power as a union, they just need to stand up for it!
I have been in IT for 20+ years, I have worked in a lot of different shops, and you only get abused if you accept it. I have worked in shops that expected long hours, and I only did it if I felt like it. If the situation got too bad, i.e. they start demanding that I spend extra hours, I walked. The beauty of IT is that there is ALWAYS another job out there. In 20+ years I have only been out of work ~2 months total, and yes, I have changed jobs twice in the last 5 years. Outsourcing is completely overblown, computers are here to stay and only getting more integrated into our lives and businesses, there is going to be IT work for a very long time.
Keep on keepin' on. Get new languages as you need them. Be flexible. Number one, above, probably has an awful lot to do with it.
When I started using the Internet there was almost nothing out there but Nix or Mainframe command lines. If you couldn't handle those you were SOL. I started reading /. very early on when it and the web were new. Still read it almost every day. Good going, Taco.
What is true is that salaries top out quickly...so if you want to keep getting more than nominal salary increases, you eventually have to go into management. What is also true is that as you age, you have to stay on top of the technology. Too many people get themselves in trouble by attaching themselves to a technology. I remember when the Defense industry died in the late eighties, lots of Cobol programmers hit the streets and started screaming "age discrimination!!!" because no one would teach them C++. This is why I've made damn sure I have things like "XML" and "Python" and "Javascript" on my resume now. If you're good, you can stay in this career as long as you want, but it takes work, and it takes planning. Be prepared to quit jobs that are decent, but use outdated technology.
The cake is a pie