12 ms·
Hah! Reminds me of https://twitter.com/mxcl/status/608682016205344768 https://twitter.com/mxcl/status/608682016205344768. Cynical answer though — Google does n
by paxys 7y ago
Hah! Reminds me of https://twitter.com/mxcl/status/608682016205344768 https://twitter.com/mxcl/status/608682016205344768.
Cynical answer though — Google does not want people like you. They don't want to hire entrepreneurs or inventors. They want people who can churn out code when given specific instructions, and that is what their interview process optimizes for.
- simonebrunozzi 7y agoAnd it reminds me of this one too: https://twitter.com/brianacton/status/3109544383 https://twitter.com/brianacton/status/3109544383 Brian Acton, rejected by Facebook in 2009. Then in 2014 FB acquired his company for $19B...
- phkahler 7y ago>> They want people who can churn out code when given specific instructions, and that is what their interview process optimizes for. Somehow I doubt that. Can anyone who actually works at google comment on what it's like? Do people come to you with specific requirement and expect you to crank out code like the interview problems? I've never worked somewhere where the software folks were actually just coding machines.
- mwest217 7y agoNot at all. I've been at Google for a bit over two years, and my experience has been at the far other end of the spectrum: a lot of autonomy, gathering requirements, designing & implementing. Also I have a fair amount of agency to see something that would make people's lives better and pitch it as a thing I'd like to work on. If it's less than a day or two of work I can generally just go do it.
- rekabis 7y ago> Also I have a fair amount of agency to see something that would make people's lives better and pitch it as a thing I'd like to work on. You’re clearly not working on their military-contract Terminator-drone program… …Unless “better” means “stone cold dead”.
- alok-g 7y agoHow much of interview-style coding is involved in your work? More broadly, would you agree to the OP that interviewing for software developers is broken?
- peterebailey 7y agoGathering and defining requirements is very much a part of the job. It is entirely unsustainable to rely on others to tell you what to implement in Google.
- danbmil99 7y agoHow many interviews involve asking the prospective hire if they know how to gather and define requirements?
- tsukikage 7y agoThis is implicit in a coding interview, though. I, the interviewer, take a couple of sentences to describe a problem. What next? Way too often, rather than ask more questions - gather and define requirements - a candidate will launch straight into solving a problem different from the one I am describing.
- hanswesterbeek 7y agoAKA "rush to keyboard" syndrome.
- adamsea 7y agoRequirements gathering in reality can often require more soft skills or political skills, which doesn’t seem to be the primary focus of these interviews. Which isn’t to say the skills you mention aren’t important.
- username90 7y agoMost engineers at Google never talk to non-engineers, the requirements gathering comes instead from looking at code, reading design docs and talking to other engineers.
- phkahler 7y ago>> Gathering and defining requirements is very much a part of the job. It is entirely unsustainable to rely on others to tell you what to implement in Google. It's like that everywhere. Nobody comes to you with complete requirements. People/customers come with problems they need solved. Sometimes an outline of a specific solution is specified, but there's always a lot of detail missing.
- ddalex 7y agoWorking at Google. My opinion is my own, etc etc What you get told is What needs to be accomplished, but not How, if that makes sense. E.G. IF you choose to accept this challenge, this platform is running at XX% availability and we need to run it at YY% availability. HOW you get to do that, it's up to you. Some folks don't accept these challenges and they go and find and fix their own interesting problems. But that's harder because you have to get buy-in from managers in order to get resources for that. There is space and need for everyone.
- smueller1234 7y agoGoogle's big enough that no one person could possibly speak confidently for all of engineering in this regard. For what it's worth, this doesn't match my experience at all. In the area I work in (SRE in technical infrastructure, but the same seems to be true for our dev partners), I see a lot of expectation for bottom up ownership. I could totally understand if somebody with a different mindset and perspective (I'm a manager, so I can see pretty clearly what's valued at evaluation time) arrived at a different conclusion.
- kohtatsu 7y agoFalse; Google wants everyone like them to keep them away from the competition. Edit: it's unfair to single Google out. It's unfortunately the correct game theory and impossible to regulate.
- kortilla 7y agoThat’s a lie they tell employees to make them feel good about themselves. If they actually cared about keeping competent engineers away from competitors, their interview process would be tuned to look for engineering skills, not leetcode.
- crimsonalucard 7y agoStraight from the horses mouth I once asked Gayle Lackman on quora: does their exist engineers who no matter how hard they study can NEVER make it through the google interview process? She said yes. She said that this is because Google optimizes their interviews for IQ. Not just raw knowledge.
- kortilla 7y agoThat’s incorrect. An interview process with true negatives doesn’t mean it isn’t loaded with tons of other false positives. Being good at leetcode has no relation to engineering skills, despite it being a skill in itself.
- crimsonalucard 7y agoWhere in my comment do I talk about leetcode or false positives? Not only are you incorrect, but you are completely off topic. I am saying Gayle Lackman, the author of Cracking the coding interview and, in the past, one of the board members who decide on candidates in the google interview literally told me word for word that the interview optimizes for IQ. Meaning that there are tons of engineers who can spend a life time studying and never get into google because they are genetically not intelligent enough. Understand?
- throwaway5283 7y agoThis is absolutely true. I work at Giant Search and Advertising Company, and joining was a huge mistake. I thought I would be working interesting technical problems with a high degree of autonomy — instead the work is extremely boring, and you get ahead by playing political games rather than by innovating. I’m one of the rare few here who managed to get through the interview without really preparing. Before joining, I had endless enthusiasm for computer science and programming. Now I feel so unenthusiastic that I question my future in this industry.
- jonathankoren 7y agoYou joined a giant megacorp. They’re all like that. There’s very little difference between Google and Oracle in this regard.
- AlexCoventry 7y agoFrom what I've read, Google is a much more humane and pleasant environment to develop software in.
- monoideism 7y agoThat's what I hear, but then I see comments from folks like User5283 above. I have the impression it may be changing into something much more similar to a typical corporation after years of avoiding that fate.
- hutzlibu 7y agoBeware though, that he or she used a throwaway. Comments can be made by anyone, also a marketing company contracted by oracle who still want talent and have to shame competitors with better image. (but the comment did seem legit and it is obvious for posting that anonymous)
- monoideism 7y ago
- Retric 7y agoReading posts like that make the process seem stupid, but it has utility for the interviewers. All of this silliness is creating an artificial talent shortage which drives up salaries at FANG companies. It’s far from universal, but the incentives between managers, workers, and shareholders never really align that well.
- pjdemers 7y agoRight. Coding tests are designed to find people who are happy in a job where their only responsibility is: "Here's your coding assignment. Go do it." Technology companies are overfull of engineers who want more responsibility than that. They don't need any more.
- LeftHandPath 7y ago> Cynical answer though Honestly I don't think it's that cynical - it just makes sense. There are the people who can and will do that stuff - and do it happily - and they would presumably be the easiest to hire as junior devs. Google views it as a stepping stone towards their next product launch, and the programmers see it as a stepping stone to a more enjoyable job. And then the inventors and entrepreneurs create their own projects, and typically both produce and earn more than they would've at the company. It kind of works out in everyone's best interest (although I'm sure the Google hiring managers sometimes regret missing out on the guy who invented New Cool Thing, and the guy that invented New Cool Thing is probably still a bit miffed that he couldn't land or get through an interview for a job he/she was clearly qualified for).
- monoideism 7y ago> and typically both produce and earn more than they would've at the company. Eh, there's a lot of us who haven't done great financially but who have written a lot of open source code being run at bigcos. Being an entrepreneur requires another skill set altogether. One that I seem to lack, although I finally have come up with a solid idea in the last year that might get me somewhere whenever I'm ready to make the move. I'm sure if I spent significant time preparing, I could do well at Google's interview process, and other FAANG companies have tried multiple times to get me to interview (oddly, never Google), but I'm not convinced it's a good idea for me. I've been much happier working for smaller companies. The one time I worked for a large corporation years ago, I was miserable. People say Google is different, but I'm not convinced. I would like that sweet compensation, though.
- danzig13 7y agoDon’t forget a lot of entrepreneurs fail until they don’t.
- ampdepolymerase 7y agoIt is actually pretty well known that the second way into FAANGs is through acquisition.
- monoideism 7y agoI've heard of at least some of the FAANGs do the typical interview process for acquisitions.
- ampdepolymerase 7y agoThat sounds terrible, can you elaborate?
- monoideism 7y agoI've read from blog posts and even from conversations that companies require acquihires, particularly non-founder employees, to go through an interview process. It may be shortened, but they still often have to do the typical algorithmic interviews. I'll see if I can find one of the blog posts I've read about the process. Note: to be clear, I'm describing the process for acquihires, not founders just wanting to sell their company and walk away with some cash (which actually seems to be somewhat unusual). Edit: this was discussed in a similar thread on HN just last year: https://news.ycombinator.com/item?id=18943500 https://news.ycombinator.com/item?id=18943500
- gambiting 7y agoIs that a uniquely American thing? I'm 100% certain that even if the company I work for was acquired, my current contract would still apply. So I would need to be given at least 3 months notice, and couldn't be discharged without a good reason - failing some internal interview wouldn't be such a reason.
- hansvm 7y agoPerhaps. Most places in the US an employment contract can be terminated at will for almost any reason or without any specific reason.
- neilk 7y agoI don’t think there’s any intention to it at all. Unless one takes extraordinary steps to examine what brings truly brings value, most people interview for clones of themselves. Or worse: their idealized self-image. Google started off with very mathy people, and highly competitive people, and interviewing this way has always worked for them, so why change? Some people have done internal studies showing how wildly counterproductive their interview process is, and yet it does not change. I suspect psychological factors are the main reason why this process persists.
- thewhitetulip 7y ago> Unearned privilege? I agree that the interview process looks for self clones. I've been in interviews where interviewer was like "why you used Dictionary to do this? Nobody uses dict in prod code" But unearned privilege seems a little harsh doesn't it?
- neilk 7y agoI took that part out. I don’t really know what is in other people’s minds.
- paganel 7y agoNow I’m curious why they didn’t use dicts, I love dicts. I’ve been writing Python for a living for almost 15 years now and dictionaries and (reasonable) list comprehensions still attract me like they did the first day I “met” them.
- thewhitetulip 7y agoI don't know. It was bizzare to hear it. To be honest the lady taking the interview didn't understand my code, at least that's what I got. The guy with her definitely didn't understand a line I had written. Maybe that was her way of protecting herself or something else But I've never come across any real reason to not use dicts
- numpad0 7y ago
- austincheney 7y agoYou could have saved a lot of space just saying button pressers. This is most large companies and why I am burnt out on writing software professionally. The reasoning for this is the commoditization of software hiring. The idea is to target the median of the bell curve, to lower risks and costs associated with hiring. This targets the greatest quantity of developers in a moment, but it also means the people who play it safe, follow popular trends, and don’t take any risks on product improvements. To think about it another way the idea is to create mediocre software with mediocre developers because the software is thought to cost less than finding, hiring, and retaining top quality people.
- ozim 7y agoNow connect the dots with: How much customers are willing to pay for software developer work? They don't want to pay anything. They don't deserve best software written by best developers. Take for example GIT, which is extraordinary piece of software, saves a lot of problems and time. If it was not free, most software shops would just keep copies of folders with dates or whatever insane ways they had (SVN is for me insane way as well :) and big paid VCS were popular at big co's. not even one became close to "industry standard" as GIT).
- evidencepi 7y agoAgree, they want smart workers (well you have to be smart at some degree to do software). And they don't care if they will miss some genius, they just let other companies help the selection process, and if you turn out to be gold, they will pay a big money to get you.
- shaan1 7y agoMakes perfect sense. Thats when you know you need to short the stock in the LONG RUN. Because all they know is taking orders from someone and running it. This is the same with all companies. If Mark Zuckerberg steps down from Facebook, you can pretty much know, it's going to go down.
- ernst_klim 7y ago> They want people who can churn out code when given specific instructions, and that is what their interview process optimizes for. I think the reason is a bit different. Google is a search engine. It's a company whose success was due to one (or several) but very good algorithm. That explains everything: why they are so obsessed with algorithms, why they hire so much olympics winners, why they don't care about anything else. Their code is pretty bad most of the time, they've took beautiful Webkit and turned it into Blink mess. They are all about algorithms, they don't care about code. And that's a pity that people are copying Google's methodology without understanding why Google is doing so. If you are developing an OS, you'd be better copying Microsoft, which had much of a different approach, nearly without any algorithm questions.
- hanswesterbeek 7y agoIndeed! This cultural / historical angle of looking at the issue hits the nail on the head.