Ask HN: Where to Work After 40?

That's interesting, are you based in Asia? I've found companies similar to what you're mentioning but they're all based in America while I wanna stay in Asia.

> Is grinding code at a FAANG really that different?

It probably depends on where you're coming from. I was an Engineering manager at a FAANG, and roughly 80% of my 1:1's with my team revolved around their performance, or lack thereof, with 5% devoted to supporting mental health, and 15% around general topics such as what they were working on.

I had 3 managers in two years, and with one we mostly talked about strategy, goals, and what we're working on. With the other two, it was always about my performance and that of my team.

It was a very high-pressure environment. The types of people who succeed long term are those that are good at playing the game or who naturally will do the required things to get good ratings.

In return, you get fantastic pay. I didn't quite hit 7 figures in compensation, but if I'd stayed another year to ride more of the run-up, I would have come close to $2M for a year.

All that said, there was some really interesting work and great teams. While it sucked as a manager, I think 30 year old me would have loved it as an IC.

Is there still age-ism in tech? Bc I see plenty of people in IC roles working into their 40s, and even some in their 50s with kids in college.

Could be the industry I work with has less age-ism: financial services.

It's not just the UK. As someone who is themselves in the same age range, as a hiring manager it's been eye opening to see the clusters of resumes from older candidates.

It continues to boggle my mind how many resumes out there are people who have spent the last 20+ years working on the same set of problems, using the same tech. The reason a lot of these people aren't getting jobs is not that they're old. It's that they've stagnated to a degree I would not have thought possible. Meanwhile there are people out there who are staying relevant *and* bringing extra wisdom to the table. Those people get hired.

The short version is I got lucky. The slightly longer version is that at the small company I was doing tech lead things because I learned I could get more done to help people by helping organize the other engineers. Then when my boss quit to go sail around the world I was offered his job. I was now a "manager" but initially I still acted like a tech lead, writing a little code, taking care of the database, that sort of thing. The nice thing about the small company was they gave me space to learn and lots of mentorship. I got to see all the numbers on the business side and changed from being the "Let's write something new in Rust!" kind of developer to being the "But what's the simplest thing we can do to help our customers now" kind of manager.

Then I got a call from a friend I had worked with many years agi who was staffing up a new org. He needed people and had a very big budget. This is where the "career" part came in. I had a job with people I really liked, making okay money and could probably work there until normal retirement age. The new job offer was much more risky for much more money and I was always bad about taking risks. So I took a lot of long walks with my wife and we talked about the upsides and the downsides (upside: _so_ much money. Downside: What if I'm no good at the job?) and in the end I took the job. The job was in another state and my son only had two more years at one of the best high schools around so I got a small apartment and flew home every three weeks.

It was an incredibly learning experience. My new manager jokingly explained to me that my new job was people and if I was looking at code I wasn't doing my job. I took that to heart. I met some amazing people. I went to an insane number of meetings. I also got paged awake at 2:00am to be low-key yelled at by a group of Irish people because a computer in India wasn't getting enough network traffic and had run out of entropy. I think I helped some junior engineers with stories like "Ha! You think that was a screw up, let me tell you about my friend who turned off amazon.com for 6 minutes many years ago." And I learned the trick of going toe to toe with a senior architect in a design review meeting by asking "Okay, but what if these two things I'm picking at random happen at the same time?"

In the end it worked out for me. I saw other people go from SDE to SDM and then go back to SDE after a year because it wasn't a good fit for them. They were better engineers for having spent a year in management, but they didn't like it at all. Also I'm typing all this with the benefit of hindsight and probably making it sound easier than it was. I made lots of mistakes in my career, but going into management turned out okay for me.

And now I'm trying to write a Smalltalk VM in Rust and no one in Ireland is waking me up at 2:00am. I got lucky.