The only place I sensed age discrimination were the places I wouldn't work anyway, the crazy "we expect 65 hours a week" shops.
In fact, older LTU workers could learn from the tech strategy of consulting and freelancing when "gaps" in their careers emerge. So long as you have something to show for it, such as a new skill or someone in your network that can raise their hand and say, "Oh yeah, she mentored me through this big project my company is working on" then you can help yourself out a bit.
I want to know how much of this is HR's fault. What the hell are they looking for, and why? Everyone admits this is a problem, but HR goes on as if they're oblivious to it. And then you read about how they're dismissing candidates that don't have an adequate social media presence, and you begin to wonder why on earth these goons run hiring.
It's bad in VC-istan but I don't think it's bad in technology as a whole. There are plenty of 50+ programmers at places like Google who are well-regarded.
The fear that many of us who are in our 20s and 30s is that the culture of age discrimination-- one that we, although young, really don't support, but that is inflicted upon us by the VCs-- will get worse in the next decade or two. Right now, it's not apocalyptic and most good programmers will be fine. The concern is that if VC-istan becomes the new normal in employment, ageism will be more of a problem when we get to 40+. Right now there are still a lot of good jobs for 40+ programmers at the Staff+ SWE level at places like Google and Amazon, but that won't be true if VCs acquire more power.
Everyone admits this is a problem, but HR goes on as if they're oblivious to it. And then you read about how they're dismissing candidates that don't have an adequate social media presence, and you begin to wonder why on earth these goons run hiring.
HR looks for reasons to reject people. They have to, because they get so many junk resumes. They cut for too old or too young or too long at the last job or too short at the last job. You need, whenever possible, to engage with people who are looking for reasons to accept people.
I'm a good developer at a good job and not that old. A few years ago I was in transition between a several-year volunteering engagement and work in the private sector, and the job search took a while. I got very few interviews at the time. I would have been an asset to any decent employer that hired me. I do not think the resumes I submitted were junk.
There appear to be structural changes underway that are making the job market volatile for a range of people, especially the long-term unemployed. I am not sure where it is all heading.
Not all rejected resumes are junk, but there's a flood of resumes from unqualified people who send out 100 per day.
It's like dating. The more damaged people engage in more activity, so you encounter a biased sample. If the good people send out 5 resumes per job search, targeted toward specific employers fitting their skills, while the unqualified send out 200 (in the hope of getting lucky) then you'll have a 40:1 overrepresentation of the bad.
You were probably a victim of the junk, because when there are so many junk resumes flying around, good people get lost in the shuffle.
There appear to be structural changes underway that are making the job market volatile for a range of people, especially the long-term unemployed. I am not sure where it is all heading.
Yes, that is very true. I don't know, either. In the next 30 years, society will need to establish a basic income just to be marginally stable, because there's no other way to pay for the periodic retraining people need as one job ends and another begins.
Companies used to train people. I'm actually a basic income proponent for similar reasons, among others. But when you put it like that, why should the taxpayers foot that bill and not the companies that reap the value?
The companies won't foot the bill. They'll just hire very young people with the relevant training or send the work overseas.
Technology is more about job replacement than destruction. The problem is that few companies are willing to train people up. The world is unfortunately too big for there to ever be a real labor shortage (at least, in the next 30 years).
Is this a real thing? I'd like to know more.
My sister did just that and landed a job immediately upon returning.
I can deal with not being hired for lack of fit, but at my age being offered a junior position is an insult. There are plenty of reasons someone might not hire me and many are neutral (position filled, bad day on my end or theirs) but a crappy offer at least feels like a statement.
Or am I just assuming programmer, and you're actually something else?
If you're told your boss manager will be a 23 year old who was BFFs with the founders all growing up, and you are 35 with 15 years of experience, that's kinda degrading.
If you're a 30 year old with 10 years of experience and you're being offered less than what an undergrad gets entreating into facebook or apple or google ($30k sign on, $50k+ worth of 4-year options to start out with (which will easily be added to so you can cash out $500k to $1M within 6-8 years)), that's kinda degrading too.
Sometimes your specific experience doesn't match the outside world anymore. Maybe you have eight years experience using Custom Designed Internal Framework that's of no use to the outside world. So, there you sit, being judged along side people with eight years less experience than you because all your experience is "hidden" to the new company, their interview process, and your social peers.
There are many ways jobs and the interview process can make you feel less than stellar.
Of your examples, the one with less money is just less money. I understand issues with a drop in salary, but the reference to "junior position" above seemed to imply more than salary.
On the first, I've been older than my managers for years now. Who cares? I don't want to be a manager, I enjoy programming. I care deeply whether that 23-year-old is a good or bad manager, but that has nothing to do with how old she is.
If you're a professional, your rate is market or pro bono. Anything in-between just gets horrible. Your salary is what it costs the company for management to waste your time. If your salary's low, your time will be wasted.
In the sense of "meaning of life stuff" (fulfillment, meaning, purpose, etc). Your salary is what you charge someone to make you do things you wouldn't normally do. Sometimes, especially in "tech," jobs and natural interests align. In the normal world, that isn't always so.
At Google, if you attended Stanford and landed in the Mt. View office (the office being more important than the school) there was, even when I was there, a decent chance of getting a legit SWE-2/SWE-3 experience that would train you to make more of yourself, and make promotions (up to Staff) basically ensured so you could focus your energy on actually learning and becoming a great engineer.
But as it is now, I see a lot of companies seeking Junior-level positions, but with big expectations and knowledge requirements. Everything except wanting to pay a proper salary.
I'm 30 with 7 years of experience. I wouldn't say I'm a top-1% programmer (probably top 5%, possibly 2%) yet but I'm a really good data scientist and I've seen a lot of different corporate environments. Also, being a Lisper (but also knowing well the virtue of static typing, having worked on production Ocaml systems) I have good taste. There are still some holes in my knowledge (I was a math major, not CS) but I'm filling them pretty quick.
I wouldn't take a job where my day consists of being handed bugs or small features in some large project where the decisions were already made. Someone else can churn tickets, I'm past that point in my career. I'm not a prima donna. In the short term (say, two weeks) I'll do what is required no matter how unglamorous. But in the long term (3+ months) I'm not going to work in a role that's incoherent with my career objectives.
I only work in roles where I get to make some of the technical decisions, because if I'm purely in an implementation role, I won't learn anything. I generate ideas and implement them; if I'm only doing the second of these, then the work is meaningless to me. If the project is big and complicated-- say, 2.1 to 2.3 in difficulty on this scale: http://michaelochurch.wordpress.com/2012/01/26/the-trajector... I'd probably be doing that under light supervision and that's fine, but if I'm not engaging in a learning process and in control of what I work on, then I'm wasting my time at this age.
Is it that you want to be more of an architect and were being offered programming positions?
Senior programming is different from junior programming. As with writing, there are varying forms of it and they have different flavors that might not be obvious to those who don't do it on a daily basis.
A junior programmer fixes bugs and implements features that come downstream from executives, product management, and more senior programmers. There's a lot of value in that experience, if it comes with mentorship, when you're starting out. But when you get to my level, the quickest way to learn is to do things and find out directly what works and what doesn't.
A senior programmer gets to set priorities, generally has a lot of autonomy over what he works on, and has input (and, often, final say) in product and architectural decisions.
It's not about title, as it were. There are plenty of people with "Senior" in their title who are junior in terms of how they work, and there are others without fancy titles who are de facto senior.
But, you know, in context, there's a huge difference between not finding a job and not being able to easily make the next step up in your career.
At 7 years, you just don't have much senior experience (that's a comment about years, not knowledge or talent). 7 years is a lot of programming experience, it's just not a lot of senior dev or team lead experience.
It's a good career move to insist on this in your next position, and I'm not doubting that you're capable of it, but that puts you in a completely different category than somebody who can't find work at all or somebody who's been a senior dev for 20 years and can't find a position.
One thing to be aware of is that a lot of shops, myself included, almost never hire senior/leads directly. I'll pay your salary request, but no matter who you are, you're going to spend a couple of months on somebody else's project before you lead your own, just to understand the code base, the team, the tracking and VCS systems, the culture in general. We may have an understanding that you'll lead the next big project if you don't flame out, but you're still going to have to spend some time down in the code trenches.
In the traditional world, yes. But what about our wacky tech world where the 22 year old is a founder/ceo/manager of the entire company? Are you less experienced and knowledgeable that that person?
I agree with your part about not hiring externally for new internal projects though (unless all your other internal projects are horrible and you need new blood to get out of institutional brain damage).
I also think this is more a problem for non-tech jobs. In today's world, if a software-engineer wanted to travel the world for 8 months I suspect she could easily get a job when she's done. She'd probably be getting recruiter-calls while on vacation.