(Replying to PARENT post)
Startups need cheap workers who will work long hours. And honestly, for every one Google (who legitimately needed genius level scientists), you have 10 WhatsApps (which are glorified simple CRUD apps).
Now how are you going to get a guy (who sort of knows what he's doing) to work 15 hours a day for pizza?
You've got to trick him "Change the world", " we're the next Google ", " you get to use any stack you want"
When your a 20 year old kid, with no responsibilities and a future ahead of you, this sounds perfect. When you're 30 (and all the more so 40), you go to work to 1. Feed your family 2. If you want to "change the world", you work for a non-profit.
And all the skills don't matter. Your knowledge how to save RAM? Useless. Just spin up another VM.
So for the CEO of a startup, a 30 year old is simply too expensive for what he needs - a cheep code monkey. All the excuses are just that.
(Replying to PARENT post)
(Replying to PARENT post)
I'm a 40+ years old life-long programmer with some academic science background, and it's not possible for me to actually get a job. A few years back I thought I'd try to get a full time position, to no avail. The only work that happens for me is freelance work with clients who already know me. It's not an uncomfortable life, but there's also a very distinct ceiling I'm always aware of.
I was instrumental, and often also the de-facto project lead, in launching several multi-million websites and other software, but as a freelancer I'm not really benefitting from these successes. In most cases I can't even legally advertise it. I'm stuck at a medium income level that I feel could dry up very quickly if bad luck strikes.
The job market appears saturated with programmers, and to make matters worse for everyone involved, companies lack the tools and the will to even select applicants properly - I suspect this is partly due to the fact that programming is considered such a low-value skill. At times it feels like it's the corporate equivalent of working as a burger flipper. It's not really considered a dignified position to be in when you're 30. Yet, perversely, the world is built on software.
There is a fundamental misunderstanding - even inside tech companies and SV startups - what the nature of programming-as-a-profession is. In my opinion it should not be some menial work that should only be performed by unskilled youth looking to advance to a "real" job as soon as possible. It's a skilled trade that takes time to develop.
(Replying to PARENT post)
However I also started programming when I was close to 30. I'm now near 50 and I'm still programming. I have to justify what I've learned. On the other hand I actually have learned. And it doesn't take too many rounds of, "Here is what I learned from X ... and so I suggest Y" working out in spades to demonstrate my value.
It is easy to work yourself into a career dead end. It is also easy to not stretch and find yourself with skills that were once great but no longer applicable. I have seen these happen to very good people.
But being unemployed because you are old is far from inevitable.
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
I'd gladly head that way. Pure software engineering is gradually becoming less interesting to me over the course of my career - the people problems are the ones I like.
However... I'm older than you and have never gotten a "you're too old" vibe from anyone. In fact, if I have a complaint it's the opposite, it's that some companies want to treat me the same as someone 10 years younger - i.e. they don't see much difference between 2 and 10 years of experience, and you're a "Software Engineer" either way.
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
Wait, how are you supposed to be a senior level developer without at least 10 years experience?
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
I am not even that strong with the latest whiz bang JavaScript framework of the week but I can architect anything with my chosen stack and I know what I know on a very deep level.
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
Those roles carry various titles - Principals, Architects, etc., but basically it is the non-management track.
In my team it's architects, senior programmers in both age and skill. Use them for code reviews, query tuning, investigating infrastructure/code improvements, etc.
Invaluable help, true multipliers.
(Replying to PARENT post)
Yea, 32 years old programmer is just too old, 32 years old surgeon is usually too young to work alone.
I keep on learning, I have accumulated lots of knowledge working in different areas of programming like system administration, database administration, programming etc. I have been payed to program using over a dozen of programming languages... At interviews I still hear "oh, you know, I'd love to have experience like yours"...
And I still hear "you are too old". What's more funny - people are not embarrassed saying that. Even though that's illegal where I live. Writing "we want to hire a woman/man only" is also illegal, but people still write that, and no one reacts.
I'm afraid I will be totally unemployable in a couple of years, just after my 40, which will come too soon. And I don't want to get into management only position (which is also hard, as I cannot get a management job "because you haven't worked on such a position, and you are too old to start that".
That's hilarious, but on the other hand that explains a couple of things like a-brand-new-hyped-technology, which is just a rewrite of what we had 20 years ago.