Ask HN: I'm turning 50. Do I still have a career in IT as IC?
My 50th birthday is near now and I'm enjoying my career in IT as an individual contributor (IC) as much as the first day. I love learning and love problem solving. I love creating systems with a group of intelligent fellow devs.
But can I still jump companies easily ? Will startups take me in? Do FAANGs hire such old ICs?
I'll try anyways, but I'm curious about your perception and experience.
Thanks.
48 comments
[ 3.3 ms ] story [ 102 ms ] threadI am almost exactly your age. For the last 10 years I've often been the oldest employee at a startup but always felt and believed that people respected my experience. (They told me so)
(There was that time I worked at a place where we had all staff meetings all the time and I frequently talked like and acted like a leader more than the CEO did... Initially I was seen as being supportive because I communicated my belief in the vision of the company more consistently than management did but being critical of management not sticking to that vision led to me being driven out. If we hadn't had the "all staff" culture I wouldn't have been dragged into playing that role...)
I personally think, you make your money in tech 'at the ends' - you either want to be far enough ahead or behind that your abilities matter more then anything else. Figuring on COBOL financing my retirement :-P
I would think there are lots of niche and non faang stuff out there but nobody is bothering to look. Or, they’re all in it for the $$ alone.
It's not the number itself
In seriousness, I’m in my mid 40’s and a literal gray beard, and I haven’t yet encountered anything I could recognize as age discrimination. I seem to be in more demand for higher-profile IC jobs than ever.
I could only wish I was being approached in this way in my 20s.
I was a 30 year old hiring manager, once guilty of ageism.
In spite of my gut instincts, we hired a gray haired ‘old guy’ well into his 50’s.
I had concerns, could he keep up with us? Would he have the energy and stamina required?
But we needed someone urgently and my colleagues felt he was a good fit. So, I went along willing to give him a trial.
Turns out, I was a total dope.
He quickly became an informal team lead, amazingly efficient in managing people and projects.
And above all, well respected in our company.
Over the years— he turned down multiple manager promotion offers. Quite insistent, he didn’t want the headaches… smart guy!
Keeping your head down doing the work leaves you unprepared if/when the axe comes.
I sent off resumes all over NA, but only got four interviews and two engagements. Networking got more than that and produced better quality engagements.
(Edit: My comment is terse and I still stand by it, but one more note: Don't let age affect your ability to do good work. Do today's work in the fashion of our day—not complaining about how things were done better in the past. It's similar to a new hire saying "at X company we did it Y way and it was soooo much better" incessantly. As long as you don't do that, then, why would it ever be a problem?)
Just read the first comment by JSeymourATL in this thread.
IT is desktop support, fixing servers, printers, computers, setting up new employee laptops, handling networking, fixing WiFi issues, etc.
https://en.wikipedia.org/wiki/Information_technology
It sounds like you're getting your definition from what people think an "IT department" is in a regular business. IT is an old-school name that encompasses far more than you describe.
There is zero value attached to experience if you are IC in this industry. Do not be fooled by words, look at the actions of the recruiters, hiring managers and interviewers.
BTW, you had better grind leetcode. Even ops jobs are asking people to do algorithmic problem solving type questions nowadays.
You can still do leetcode if you think that doing so helps you practice, and will help you do well in the face of "No plan survives contact with the enemy" type situations. But don't bet your career on leetcode.
What I have found is that you need to have good relationships with other people in the business, and you need to talk to the right people inside the hiring organizations. It is entirely possible to still fail to get hired by them, but the hiring process remains one that is still mostly driven by personal contacts.
I've been a sysadmin and DevOps guy my entire career, and now I'm moving into Support Engineering. In a way, I've been L3 tech support most of my career, because whenever the help desk has been unable to resolve problems, they would come to us on the operations side to try to help them figure out what went wrong and how it needs to be fixed for this customer.
So, now that I'm a Support Engineer at AWS, Customer Obsession is my top leadership principle that I'm paying attention to.
And yes, our team is hiring.
I do projects that last from 6 to 18 months, and in each one I learn about a new business, and often learn about a new technology. it keeps things fresh and interesting.
I can do this because my skill set is pretty broad and I have spent time building and maintaining a big network over my career - not necessarily attributes that can be acquired quickly.
I guess the only actionable advice is to consider working out side FAANG, and be open to consulting vs. employee. There's plenty of reward and plenty of interesting work out here.
So we're out here, and we have a bias for senior talent. It's pretty easy to find junior people, but the good series A/B startups that are trying to build out their org don't really want more junior people and need folks like you.
I don't want to doxx myself here but there were two notable cases I can think of where in one, the code assignment saved us from a bad hire and another where we didn't do enough and we made a bad hire. Both individuals ostensibly had deep experience, but they weren't a good fit for our organization. Everyone has to contribute code directly, we can't have a pipeline where some folks are doing high level architecting and delegating the coding/impl details to juniors yet.
Edit: I think I just found my new BS company test. If rationality, sanity, and pragmatism doesn't prevail, I don't want to work there.
I think that can work for plenty of orgs, but I'm not sure about my team. I've already worked with two people who had great references and decades of experience who couldn't contribute to what we are building due to their weak technical skills. That doesn't mean there isn't an org out there that they will fit in with better, but the current process we use was derived from experience. It's not hazing, like Google.
I don't know if they hire them, but they at least humor you with an interview. I'm older than you and prepping for my virtual onsite now and had made it to the onsite previously in a couple FAANGS.
I can only talk about one of the letters in FAANG. Just my observation.
We definitely hire 50+ or even 60+ people. In my experience, all of the internal processes are designed to remove individual bias. You can get hired and be successful.
The problem arises when there's a mismatch in expectation. Suppose you look at your years of experience and shoot for IC7+. The bar for IC7 is _high_. From and IC7, they expect to see org-wide impact in your current role. An org is 1000+ people. Most ICs can spend an entire lifetime and not have that level of impact.
Basically, experience has little to do with level or comp. If you can lead a small team with a few people, are willing to come in at IC5, and fine with making 450k+, I don't see a problem with age.