3 ms·
I wasn't around Google 8 years ago. But I can verify that today Google is perfectly fine for older workers. The guy who sits next to me is in his 50s. Absolu
by btilly 17y ago
I wasn't around Google 8 years ago. But I can verify that today Google is perfectly fine for older workers. The guy who sits next to me is in his 50s. Absolutely nobody doubts his abilities. Nor does he have any complains about how he is treated. And the last guy I helped interview who got hired (I'm not sure for what team, hopefully for ours), is of similar vintage and I believe will work out well.
The one warning I'll give to older programmers who want to come to Google is that everyone codes here. There is an attitude that some people get after decades in the working world. That attitude is, "I'm so senior and experienced that it makes no sense for me to actually do something so menial as write code." If you have that attitude, then Google won't have a place for you. There is no such thing as a non-coding software architect here.
But if you have experience, ability, understand algorithms, and are willing to code, then Google can be a very friendly place indeed. People here are very aware of the difference between one year of experience 10 times, and 10 years of experience. The former has no place here. The latter is highly valued. And 20 years of experience is even more highly valued.
(Disclaimer: I'm only 40, and have only been in the software world a dozen years.)
- mhansen 17y agoCan you elaborate on the difference between 1 years of experience 10 times, and 10 years of experience? I don't follow. Do you mean 10 separate one-year projects in different technologies?
- philk 17y agoWhat he means is the difference between someone who's been a programmer for ten years but has learned very little (and done the same easy stuff over and over) and someone who's been a programmer for ten years and has done really impressive stuff and learned a lot.
- nailer 17y agoWhen I was involved in the Unix world I used to see this a lot: someone with 'x years of experience' who knew the 5-10% of the system they work with day to day really well, with no understanding, no interest, and no awareness of the rest of the system.
- btilly 17y agoExactly. If you are content to do the same thing over and over again, you won't improve no matter how many years of experience are on your resume. On the flip side there are some aspects of the profession that you just aren't going to learn without putting in serious time. People who do the first thing can be OK if you only need easy stuff done in a routine way, and have someone to give them direction. People who do the latter are invaluable resources.
- brg 17y agoMaybe it differs by location, but it is not true that everyone codes. Within engineering, about 1/3 of tech leads do not code beyond mocks, and no one in engineering management codes. Staff and above also have diminishing coding activity; which is necessitated by the requirements of group leadership and planning. You can speak to SRE coding activity. But to continue, many in test only manage contractors and their coding is no more than small python scripts for tool automation. And most importantly, Program Management is the single quickest growing group in terms of influence and employee percentage. I do no believe most even remember how to code.
- btilly 17y agoI know that in my corner, everyone codes unless their job is clearly a non-coding position. For instance managers don't code, but you're not going to get an engineering interview as a manager. You likely know the broader organization better than I do, so I'll take your word that there are non-coding people out there. But that said, I'd be very, very surprised if anyone got through the engineering interview process without being asked to write code. Multiple times. So even if you did wind up not writing much code, you're not getting the job unless you're both willing and able.