Live data from Hacker News

Ask HN: Joining Big Tech in One’s 40s

news.ycombinator.com

11–20 of 203 posts

Re: Ask HN: Joining Big Tech in One’s 40s

#11

in your 40s your big picture management skill would be more valuable than technical skill. you need to disclose what was your role in these startups. if you want to go back to coding at FANG there would be less ageism but it will still be there. Be sure to brush up your algo, data structure. I would suggest finishing a book of programming interview and you should be set.

> in your 40s your big picture management skill would be more valuable than technical skill.

I don't like this assumption: Some of the older engineers & architects I know are incredibly more adept at developing than management, and speaking with a lot of them, most are pushed into management roles instead of desiring them.

Re: Ask HN: Joining Big Tech in One’s 40s

#12
I was 37 when I joined Google in a senior IC role in 2008, so nearly my entire 40's. It's still work, there are still issues with coworkers and there's still stress compared to the startups I used to work at. The company isn't going to go out of business but you can still get a manager who doesn't communicate well and gives you bad performance reviews as a result. Google turns over more employees in a month than the entire headcount of some of my previous companies. And GOOG is a huge company - if anyone says it's either great or horrible that's probably true for them, but it doesn't mean much for what your experience is going to be. I honestly don't think that being young is really much of an advantage one way or other here - there are successful people in the 40's here, even ICs, there are a lot of new grads who wash out after a year or two and go elsewhere. Big companies have much more idiosyncratic tech stacks so knowing any particular technical skill isn't that huge a deal as we probably don't use it anyway. Know the basics, know how to write, know how to manage up.

edit: reading some other comments I think it's easier to be an older IC at big companies than startups/small companies. But whether you should pursue a management track is a completely different question.

Re: Ask HN: Joining Big Tech in One’s 40s

#13
I'm in a similar position. I think if you have experience they really try to interview you for senior positions where you are defining technical architectural standards and teaching others. That makes it tough if you just want to code, but maybe suits you.

At least in the initial stages it seems FAANG companies at least are very good at ignoring age for applicants, later stages though are tougher when most people interviewing you are half your age.

Re: Ask HN: Joining Big Tech in One’s 40s

#14
I'm not quite as old, but I struggle with this question too. Programming and building shit is my passion, and I'd probably be a terrible manager, but I've been conditioned to believe management is the wise path for aging software engineers.

Re: Ask HN: Joining Big Tech in One’s 40s

#15
post #14

I'm not quite as old, but I struggle with this question too. Programming and building shit is my passion, and I'd probably be a terrible manager, but I've been conditioned to believe management is the wise path for aging software engineers.

Same and same except I have more management than programming time but I enjoy mentoring so that side is fun, if I want to scratch my own itch I have side projects for that when I want.

It's a trade-off though, by choice I'd be programming most of the time.

Re: Ask HN: Joining Big Tech in One’s 40s

#16
Broadly, you will experience significant ageism trying to come in as a coder/technical type. Probably less of this as a manager.

That said, you should do what you want, especially if you have your nut already. Look for an outfit that really needs someone and is willing to look past age (or even sees it as an advantage).

Re: Ask HN: Joining Big Tech in One’s 40s

#17

in your 40s your big picture management skill would be more valuable than technical skill. you need to disclose what was your role in these startups. if you want to go back to coding at FANG there would be less ageism but it will still be there. Be sure to brush up your algo, data structure. I would suggest finishing a book of programming interview and you should be set.

Big picture yes, but in tech management:

Big picture infrastructure

Big picture domain knowledge

Big picture risk management

Big picture release management

Big picture languages

Big picture frameworks

Big picture architecture

Big picture maintainability

Big picture knowledge sharing

Big picture build infrastructure

Big picture etc

If you have a GOOD senior, you will safe a lot of time on bs, and will make your junior devs shine like rockstars.

Re: Ask HN: Joining Big Tech in One’s 40s

#18
Your mileage may vary, but I think management role is hard to come by at bigger companies, unless you have a connection with existing management who already work there. So I would hit up your existing connections.

Also, you may already know this, but big companies have their own problems. Unlike at smaller companies, these are deep structural or cultural issues you will not be solve. Instead, you have to learn to make the best of it and not let it get to you.

Re: Ask HN: Joining Big Tech in One’s 40s

#19
Yes, I did exactly this. Stayed a dev, moved to the west coast, got a big pay bump, job stability, and benefits. There are plenty of 40+ devs here. So much of the work at big companies is learning their huge custom domain, don't worry about any particular tech.

Only regret is that I absolutely under leveled myself (msft L64), and after a couple years getting dragged through a couple of reorgs, I still feel like promotion is a ways off. Most of my peer group is 10 years younger, and most ICs of my age group are at least two levels up. So wait for an opportunity at the level you think you should be. Don't let imposter syndrome talk you out of it or think you can make it up after you join.

But even still, I'm doing way better now than I was back in Michigan working for startups, even accounting for cost of living.

Also note the most challenging change for me was getting used to how little control of anything you have is. I really miss being able to basically decide my design and implement it against public well-known technologies. Now so much of it is calling around, trying to figure out how other teams are doing things, coordinating with them, ensuring backward compatibility with a million old things, blah blah blah, it's much slower and less interesting. But, still worth it....I guess. (second-guessing myself now?)

Re: Ask HN: Joining Big Tech in One’s 40s

#20
Same age, I recently interviewed at two FAANG companies.

Mostly algorithms and system design interviews. I thought I did pretty well (something like 3 very good interviews, 1 good, and 1 ok). In both cases, the conclusion was that my results were good enough for an L4 position, but they wouldn't hire me for less than L5. (Why not, I'd be happy as an L4...). Also, I found the interview process pretty random and arbitrary. One company praised my algorithmic skills, while the other said that I did very well on system design). They encouraged me to re-apply.

I'm not concerned about the actual job, I don't feel less capable than my 30 year old self. I'm more knowledgeable, and I have more experience with human interactions.

The interviewers all told me that you don't have to be a manager if you don't want to, and that good developers were always valued, regardless of their age. I don't know how much of this is true though. I can't help thinking that my age had played against me in the final decision.

The interview process is a pain. It's very random, it takes a lot of time preparing (some people literally spend months working full time). The things they ask you have very little value besides getting you a job. At least, it's kind of fun to work on these leetcode problems, but after 200 hundred variations of BST and dynamic programming exercices it starts to get old. Also, if you already have a demanding job (and maybe a family), it's hard to find the time to practice.

If you spend enough time preparing AND if you aren't stressed out during the actual interview, I think you can pass with reasonable probability the algorithm interviews. I found system designs a little more random. My question wasn't in the "syllabus" they provided me. Also, as an older programmer, there may be many things that you knew a few years back. You're disadvantaged compared to a younger graduate.

Post reply on HN