Live data from Hacker News

How to get a job at Google, interview questions & process

dondodge.typepad.com

91–100 of 130 posts

Re: How to get a job at Google, interview questions & process

#91
post #70

Earlier quoted context omitted.

Are those interviews so frustrating that you are willing to take 2 low-paying jobs instead?

As a bartender and a valet, I've easily averaged $15-25 an hour. Right now I'm making $25 an hour when I'm billing, and once I get home I'm not in the mood to do much computer work. Additionally, you can find service jobs anywhere, and start up very quickly. I'd rather have the flexibility to move anywhere, the stimulation of constantly meeting new people, and some leftover desire for personal projects when I get hom…

Fair enough. Note that I'm not looking down on your choice of jobs (recently I've been thinking it would be cool to get a part time job as bartender but it's not feasible now) but I suppose they inevitably come with some hassle and that will be worse over time than the one-time hassle of the interviews. Besides I assumed your programming job would pay much more (well, it should).

Re: How to get a job at Google, interview questions & process

#92

Earlier quoted context omitted.

Want to work in Chicago? Our interview process mostly consists of asking you questions you should know the answer to. If your answers make sense and you seem pleasant, welcome to the team. Oh, did I mention you'll probably make twice as much here than at Google? Incidentally, more people want to work at Google than want to work at Bank of America, even though there is plenty of interesting code to write at the Bank,…

What language(s), tech, framework is used for the software (web-apps? desktop? etc) at BoA?

There are something like 70,000 developers and 300,000 total employees, so it's hard to say anything other than "all of the above".

I mostly use Haskell and Perl. The rest of the department is mostly Perl. Sometimes I do C. Other groups are Python-heavy. There is a big Java and C# presence, and of course a lot of people that think C++ is the only real programming language.

There is some initiative to standardize on C++ and Python, but I doubt that is ever actually going to happen.

Re: How to get a job at Google, interview questions & process

#93

I interviewed with Google for a SRE position earlier this year and their screening process sure is tedious: Lots of grilling on obscure UNIX trivia and data structures/algorithms but nothing on the broader picture, like how to write good, maintainable software. I like nerding about graph traversal algos as much as the next guy, but not for 90 minutes on the phone after a long day of work. I'm sure the screening proce…

When I interviewed with them for the SRE position I was extremely nervous (I was right out of college, and Google had contacted me rather than me submitting my resume) and the guy on the other end of the phone for my first interview seemed uninterested, had a really bad quality phone (I could hardly hear his questions), and kept asking the same questions over and over in different terms, and I really couldn't figure out what he was looking for as the "right" answer.

The Unix trivia was not nearly as bad, that was easy as I had done a lot of reading on it, however some of the data structures I was asked about I had never learned in school and had just read about on Wikipedia so I didn't really understand them well enough.

The second interviewer was absolutely fantastic, and was genuinely interested in me as a person, had checked out my resume and looked at some of the previous projects I had done (Near Space balloon launches were discussed). I felt much more at ease, but I did seem to have somehow mixed many of the different programming languages I know (C++, C, Python, Java, F#, Scheme) thus my code was less than clean.

Ultimately after 5 different phone interviews I was unfortunately told that I was not a fit, that they would keep my resume on file and that I could try for another position when I had gained some more professional experience.

The Google interview did help me get through many other interviews I had the pleasure of going to. I was less likely to be caught off guard, especially since it was my first MAJOR interview with an extremely large company. I do wish that Google had not been my first interview as maybe then I would have gotten further into the hiring process and maybe just maybe I would have been working at Google.

That is an awful lot of maybes and it is not worth brooding on what could have been. I am extremely happy with my current job, I love what I do and the people I work with at a small new startup. I feel with a small company I can make more of a difference.

Re: How to get a job at Google, interview questions & process

#94
post #68
post #48

Earlier quoted context omitted.

Well, if they made Ken Thompson do a C programming test before letting him check in... ( http://www.theregister.co.uk/2010/04/21/ken_thompson_take_ou... )

Um, that is readability. Everyone goes through it. Basically, "Do you know the Google style guide, and can you be trusted to know when code does or does not follow it?" In a large code base it is important to have a consistent style. There are a million reasonable style choices. And knowing a tremendous amount about the C programming language tells us squat about whether you know what style choices Google has settled…

I know. I imagine a similar argument for why no one bypasses the interview requirements. You have to be able to conform to the culture.

Re: How to get a job at Google, interview questions & process

#95
post #24

Earlier quoted context omitted.

They've actually said as much. They understand that their process generates false negatives but they don't want any "crud."

Lots of grilling on obscure UNIX trivia and data structures/algorithms but nothing on the broader picture They understand that their process generates false negatives but they don't want any "crud." But quizzing on random trivia is irrelevant to the process of eliminating crud. It's quite likely that a cruddy performer will be able to rattle off all known sorting algorithms or all the option flags for GNU grep -- tha…

Ah, but this is not your normal unix trivia, the questions I were asked were stuff like what is an inode, where are inodes stored, what is a scheduler, what is the difference between /dev/mem and /dev/kmem and other questions along those lines.

This is not just flags to give to a process to make it do something, this is system internals. When I mentioned that I knew FreeBSD fairly well I was asked questions specifically about UFS and the likes.

I never did get asked about flags to grep and other UNIX tools.

Re: How to get a job at Google, interview questions & process

#96
post #67
post #49

Earlier quoted context omitted.

Perhaps the position they were interviewing you for actually involved writing efficient software, and thus required thorough knowledge of the fundamentals of computer science (data structures and algorithms &c) and systems programming?

SRE (Site Reliability Engineers) according to Tom Limoncelli (a Google's SRE) is a kind of sysadmin, I doubt that this would ever be the case.

Not entirely true. There are two sides to the SRE positions. The sysadmin side is indeed what you say they are, they work on the systems keep them running and do hardware related tasks as well as UNIX level tasks.

The software engineering SRE's work on products to make sure they are ready to scale or if something fails to fix the point of failure. They work alongside the product development teams to make sure the product is stable in production.

The two positions require two different skill-sets (I was interviewed for both sides of SRE). One requires very much computer science, data structures, programming languages, and all of those, the other sysadmin requires more knowledge about Linux, its internals, and the command line interface.

Re: How to get a job at Google, interview questions & process

#97
post #32

Earlier quoted context omitted.

They've actually said as much. They understand that their process generates false negatives but they don't want any "crud."

Exactly. They've also said that their high false negative rate is why they clear out their records every couple of years. If you got rejected a couple years ago you can apply again and they won't be looking at your previous attempt's performance.

Not to mention that in a couple years you can become a much stronger hire anyway, especially early in your career going from 0 experience to 2 years. Experience = Time * Density [1]

[1] http://stevehanov.ca/blog/index.php?id=105

Re: How to get a job at Google, interview questions & process

#98
post #27

I've heard several claims about Google: 1) They hire less than 0.5% of applicants. 2) Their interview process is extremely time-consuming. 3) They pay below-market salaries in many cases. 4) They're a reasonably nice place to work, by big-company standards. The current article supports (1) and (2), disagrees with (3), and supplies no data about (4). For a talented engineer, what's the expected payoff of actually goin…

I recently interviewed with Google and I'd dispute (2). I have a friend at Google who vouched for me, so they didn't bother with a phone screen. The interview process consisted of two half-days where I spoke with 5 interviewers in total. That seems about the norm for tech companies. I certainly prefer splitting it across two half days rather than having one giant wall of interviewing from 9 to 5. Also, your payoff/co…

Having an in is always nice, for those of us on the outside the interview process is tedious and does take a while. Various different phone interviews, talking to recruiters, emailing back and forth. It is all rather time consuming.

Re: How to get a job at Google, interview questions & process

#99
post #35

Why would anyone want to work at Google at this point? They can't hold onto their people, have very high churn and dissatisfaction rates, etc. I could see maybe wanting to put in a year to learn the google stack, or if you have a particular area you've been researching and they will pay you to do exactly what you want, but beyond that... there are lots of companies offering better salaries and options with serious va…

They can't hold onto their people, have very high churn and dissatisfaction rates, etc. Do you have citations for this?

What better way than to link you to google? :) http://www.google.com/search?sourceid=chrome&ie=UTF-8&#3...

And specifically http://techcrunch.com/2010/09/01/google-making-extraordinary...

More generally, this is common knowledge around the valley.

Re: How to get a job at Google, interview questions & process

#100
post #35

Why would anyone want to work at Google at this point? They can't hold onto their people, have very high churn and dissatisfaction rates, etc. I could see maybe wanting to put in a year to learn the google stack, or if you have a particular area you've been researching and they will pay you to do exactly what you want, but beyond that... there are lots of companies offering better salaries and options with serious va…

> there are lots of companies offering better salaries and options with serious value, with similar challenges, that are going places Genuinely curious. What companies are you talking about?

Facebook, LinkedIn, Twitter, Zynga, etc.
Post reply on HN