14 ms·
One of the replies by a Googler explains the rejection succintly: "I suspect that you are awesome as a developer in a certain place, but that Google—at least a
by pavlov 9y ago
One of the replies by a Googler explains the rejection succintly:
"I suspect that you are awesome as a developer in a certain place, but that Google—at least as a software engineer—wouldn’t be the right fit for you. They really do want computer scientists. The ability to figure out what to build isn’t valued all that highly, because that’s not fundamentally the responsibility of the software engineer."
What irks me is that a lot of companies have imitated Google's hiring process without ever stopping to consider whether it's right for them. Do they want engineers who are computer scientists rather than engineers who can figure out what to build?
In Google's case they explicitly don't want the latter and hire accordingly. The company is structured to make this work -- there are product decision makers who understand software and can feed work to the CS-focused engineering teams.
My feeling is that most other companies would be much better off hiring engineers with a more user-oriented mindset, yet they end up explicitly filtering that out because they want to hire like Google.
- WalterBright 9y agoBack when I worked at Boeing, development teams were evenly split between technicians (draftsmen) and engineers. The latter had engineering degrees, the former didn't. They often did exactly the same work. A lot of the techs were very, very good and had an excellent intuition about design and how things worked. But they got paid less for the same experience level, and sometimes grumbled about that. The trouble was, sometimes intuition, experience, and high intelligence just wasn't enough - mathematics was needed, an ability to apply engineering principles to go beyond book solutions was required. And the techs were dead in the water on that, and that's where the engineers were needed. I think Boeing's brilliance was realizing that both techs and engineers were needed to make a well-rounded team. Even the seating was engineer-tech-engineer-tech-engineer-tech to ensure that we worked together side by side.
- WalterBright 9y agoAnother interesting example is Shazam, which listens to 10 seconds of music and identifies the song. When I encountered it, I knew immediately that its implementation must be based on a fourier analysis of the sound to generate a fingerprint. That's because FA was a required part of my engineering curriculum. No matter how good a programmer I was otherwise, without knowledge of FA I'd probably hack around for years with one inadequate ad-hoc solution after another. If I was really clever, I may even actually reinvent FA, badly. This is where having proper engineering/mathematical training pays off. Just being a great programmer is just not enough. For another minor example, I was given the minor job once of printing what was on the graphics screen on the printer. I knew that constructing a coordinate transform matrix was the answer, and had it running in a couple hours. A coworker, an excellent programmer, who had never heard of matrix math, was completely astonished at this and thought it was just black magic.
- pavlov 9y agoYet if you look at the engineering team at a company like Shazam, I'd bet a small minority of them actually work on song fingerprinting. Shazam is an app company. Most of the people there will be working on UIs, serving requests fast enough, integrating with partner APIs, and other standard software development where they never once need to feed audio packets into libfftw or whatever. Your other comment seemed to suggest that you feel the Boeing model should apply here, and the people who don't work on the math-heavy product core should be considered technicians. Is that the right interpretation?
- heeen2 9y agoThey also need a decent database to find the song from a five second sample occurring anywhere in the whole up to say 8 minute song, for their whole song library
- giancarlostoro 9y agoAlso in some cases have access to not well known artists altogether.
- WalterBright 9y agoI'm suggesting that a well-rounded team has a mix of skill levels and expertises.
- meheleventyone 9y agoIn my experience this is where the ability to learn from literature would really help. In this specific case you’d encounter Fourier analysis pretty damn quickly if you started to read around the subject. Likewise whilst I think my formal teaching gave me a grounding I actually value the self-learning aspect from my degree more. The hard problems are the ones you’ve not heard the solution too before. The main thing a formal education provides is a leg up and hopefully a solid set of skills to help find answers to hard problems.
- 9y ago
- csydas 9y ago> a lot of companies have imitated Google's hiring process without ever stopping to consider whether it's right for them. Truth be told, this is common across virtually all businesses, regardless of size and scope. Hiring is tough, since even the most well-meaning family oriented business doesn't want to put time+money into someone who isn't going to be a fit; at the same time, many employers aren't sure how to properly scope out what they want from an employee, and the end result is searching for "good ______ interview questions" and using those as the interview. Taking the time to find out what you actually want instead of just "...the best!" is usually a better idea, but it also means taking a lot of time to really break down your needs first. I've seen interviews get past the last interview and to the final deliberation on the results only to have people arguing over the purpose of the position, which is pretty egregious in my mind.
- brian-armstrong 9y agoIt's also a hot load of horse shit. Google has something like 40,000 engineers on staff. Do you think they're all experts at CS?
- hueving 9y agoIt sounds like a self congratulatory post rationalization of the Google hiring process. People good at algorithms are not necessary to build what a huge chunk of Google engineers work on (basic CRUD apps). Additionally, being good at CS alone without software engineering knowledge results in crappy, untestable software with a poor user experience so CS knowledge isn't enough. The best L6+ SWEs I worked with there were amazing due to their ability to distill requirements for complex products into sustainable software architectures. Other than the few groups working at the cutting edge of a CS field (<10% of SWEs), algorithms knowledge outside of complexity analysis (to avoid bad code) was essentially useless and software engineering was all that mattered. Many employees at Google just defend the hiring process because they don't want to question the system that makes them feel superior to the hundreds of thousands that have applied over the years. "Google doesn't build software, it advances computer science."
- cmiles74 9y agoThis hits on something that really bothered me in some of the Quora responses, particularly from those who had worked at Google: they smugness and superiority. In some ways, for some people, it could be well earned: someone took an idea from abstract concept to implemented algorithm and maybe even to a library or product and changed the world, to some degree. Other software engineers, performing more mundane tasks, might also change the world. Howell's product certainly made a very positive difference for me and I leveraged this to get my own work done faster. I think we can all come up with many examples of software that's impacted our lives that doesn't revolve around a unique computer science discovery but instead, like Homebrew, solves a problem in a practical and accessible way. This isn't in the text, but I am left with the feeling that software engineers who ended up (because life, etc.) working in less math-heavy roles are somehow inferior, and I just don't believe that. Working through BS level comp-sci coursework at a decent college is a significant achievement for those students, at that age, and should not be diminished. But to imply that those working in the field who have not had the good luck to have found interesting computer science problems to solve, who have instead worked at simply improving existing products or focusing on products that meet another need (i.e. accounting, communication, etc.) are not "really" software engineers is, in my opinion, going too far.
- deleted 9y ago[deleted]
- jondubois 9y agoThere are two kinds of software engineers. 1. The cautious engineer who joined a big corporation immediately after finishing university and who might change companies maybe once or twice in their whole careers. They never take risks, never get fired, achieve steady career progress, steady bonus every year, steady pay raises, steady promotions every couple of years, can spend hours learning algorithms, never having to spend any time to strategize their next negotiation or career move... 2. The risk-taking engineer who joined a startup straight after/before/during university and who went through companies like toilet paper for the first 10 years. Always directly exposed to market forces, ready to jump ship at any time; always keeping one eye on the lifeboat. Always looking for a big opportunity, willing to network hard, change countries, get exposure; do everything they can to stay independent of anyone else and completely self-reliant. After finishing university, I started with path #2 but was exhausted after the first startup I joined failed so decided to try #1; unfortunately my past experience had made the corporate environment way too depressing for me. I just couldn't relate to the other employees there so I had to go back to path #2. It was difficult and painful but I got to build up my character and my confidence.
- vonmoltke 9y agoHoly False Dichotomies Batman! For the record, I am neither of those things. In fact, I'm not even close to either description.
- jondubois 9y agoWell they're extremes so there are bound to be people who fall in between. But I think that most engineers would be closer to one side or another.
- ghrifter 9y agoBasically you stated that there are entrepreneurs and then also people who just wanna put bread on the table, just like any other discipline. There are two types of hair dressers: ones that open their own shop (startup), and others that join existing shops (corporate)
- threatofrain 9y agoI also imagine that it's certainly possible that at another time he may have been hired at a large behemoth like Google for another role, but by writing such a public letter, hiring him would be kind of silly now; the atmosphere is kind of poisoned. Luckily Apple decided to hire him.
- kcorbitt 9y ago> They really do want computer scientists. The ability to figure out what to build isn’t valued all that highly, because that’s not fundamentally the responsibility of the software engineer As a former Googler myself, I 100% endorse this analysis. Engineers at Google are well respected and have a fair amount of freedom along some axes, but UX/product decisions are not one of them. There are many engineers who enjoy working within those constraints. Ultimately, I decided that I wasn't one of them (which is why I'm no longer at Google). Also, this at the end of Max's answer: > I am often a dick, I am often difficult ...really wouldn't work well on most teams at Google. Google's culture has an allergic reaction to jerks, even brilliant jerks. On the whole I think this is a good thing, even if it selects against some highly capable people.
- ape4 9y agoWhat about the 20 percent projects. Don't some of them become real Google projects. (Of course, what to do for your 20 percent is selected by you.)
- virtualized 9y agoThat would explain why Google's products often have very obvious flaws. The developers who know that the issues are fixable are being ignored.
- saas_co_de 9y agoyeah, like gmail marking emails from people on the same business account as spam (for years) and account switching for google drive not working (for years) to name a few of my pet peeves. Google does some great work, but their products are far from perfect, and many have been canned because they failed in the marketplace.
- walshemj 9y agoHandling of robots.txt files with BOM is trivial but google does not do that so your robots.txt file my not work as expected.
- brohee 9y agoFrom https://developers.google.com/search/reference/robots_txt?hl=en https://developers.google.com/search/reference/robots_txt?hl... "An optional Unicode BOM (byte order mark) at the beginning of the robots.txt file is ignored." At least they document it.
- masto 9y agoGoogle is a big company, and there is a lot of variance between teams. I don't think this is a great generalization. I have only worked in one small area, but my intuition is that if you end up doing something that's very much a part of the public face of the company (say, a flagship mobile app), your experience will probably be similar to other product-driven app companies, where there are people who specialize in making product decisions and people who specialize in implementation. Whereas if you're down in the bowels of the infrastructure for transforming protobufs into cat videos, you may never meet a product manager for your whole career.
- IkmoIkmo 9y agoI get that, if he applied to a particular compsci-heavy function... he's just not a good fit. That's fine. But any HR department worth its salt has a good idea of the company's needs in general (i.e., the other 1000 functions that Google has), and could ascertain and recognise talents and strengths in Max, and find a fit. The notion that, as Max puts it, 90% of Google employees and a significant fraction of developers worldwide use a technology you built, but that there's no fitting function for you at a large technology company with a highly diverse set of tech initiatives, is frankly ridiculous. There's obvious talent, drive, ability-to-deliver etc there.
- clarry 9y ago> But any HR department worth its salt has a good idea of the company's needs in general (i.e., the other 1000 functions that Google has), and could ascertain and recognise talents and strengths in Max, and find a fit. The more I read stories about hiring, the more I get the feel that all too often hiring people are preoccupied with trying to come up with reason -- any reason at all -- to reject a candidate. Instead of looking for talent to cultivate, they look out for "losers" to show the way out. They must be the bad applicants, and thus anyone who makes it through must be good, right? So clever, aren't we!
- syshum 9y ago>> there are product decision makers who understand software and can feed work to the CS-focused engineering teams. Their product "decision makers" aka marketing dept, have been terrible of late. Google is really having a problem with new products, the only successful ones are one they bought that were created by software engineers not a marketing dept Maybe Google needs to start hiring engineers that have the ability to figure out what to build and allow them to build it...