Live data from Hacker News

Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

haufler.org

71–80 of 123 posts

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#71

" Simultaneously, I quickly Googled ‘how to use bitwise operators in C’ and found this wonderful code snippet on StackOverflow that made the problem easy to solve. I wrote a solution with time to spare, and the interviewer seemed content with my answer." Wow. NB to all interviewers: this guy's a cheat.

I would have to disagree that what I did was "cheating". Software engineers are given problems to solve, and their job is to solve these problems efficiently. You don't always have the solution to every problem off of the top of your head. That's why programmers use Google, StackOverflow, and documentation as resources. The primary skill employers are looking for is learning how to learn new things quickly. And I bel…

> Also, I declined to mention this in the article, but after I finished that UTF encoding problem in my interview, the interviewer asked where I got the check-bit macro (he saw me paste it in). I told him I got it from StackOverflow. It didn't seem to concern him.

That's a pretty important part of the story, and makes the situation very different. It also makes the interviewer seem a lot more competent. Trivia questions are useless in interviews, and the fact that you were able to quickly google it, recognize it as a relevant solution, and apply it correctly actually is demonstrating that you know how to learn things quickly (and that you have at least some familiarity with binary representations and manipulations). The average charlatan would just start copying and pasting in panic, which is usually pretty easy to pick up on.

Meanwhile, you can't pretend what you described in your post is really a moral position if you had not said anything. It might not have been strictly immoral as you really owe them nothing, but there's no shining principle demonstrated there.

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#72

My girlfriend is in the medical profession. She's gotten job offers after 1 hour conversations. The last job interview process I went through had 3 separate phone interviews (each with coding questions) before they were to fly me over for a full day interview. She was pretty surprised at how intensive the process was. I have a CS degree from a top-10 school and have 5+ years of work experience. This is the kind of st…

I can't believe the general attitude programmers are putting forward. Here is a person in the medical field that requires at least twice the schooling, huge entry barriers etc getting an hour interview.

We are subjected to full day flights, multiple phone interviews etc.

She deals with life, not code.

This tells me one of two things. Either our hiring practices are severally broken, or its harder to program then be a doctor.

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#73
post #3

everytime I try the link I get a timeout request!

Cache: http://webcache.googleusercontent.com/search?hl=en&biw=1...

Text-only is teh quickness: http://webcache.googleusercontent.com/search?q=cache:haufler...

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#74
post #13

Great overview of the different interview styles being used. I cannot say I am convinced you always get the best people through. I don't have any aspirations to interview at Google, but did stumble across an 'Google Interview' book at the local bookstore. It makes great reading. WSJ did an article on Google interviews late last year, including answers. Here are the questions (click the link below if you want answers)…

The explanation given in wsj for problem 2 is totally wrong. The balloon will do the same as a person in the car (nod backwards), only less pronounced due to air resistance.

Actually, the WSJ is correct. Helium has a lower density than air, while a head has a higher density. Hence, they will move in opposite directions.

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#75
post #13

Great overview of the different interview styles being used. I cannot say I am convinced you always get the best people through. I don't have any aspirations to interview at Google, but did stumble across an 'Google Interview' book at the local bookstore. It makes great reading. WSJ did an article on Google interviews late last year, including answers. Here are the questions (click the link below if you want answers)…

The explanation given in wsj for problem 2 is totally wrong. The balloon will do the same as a person in the car (nod backwards), only less pronounced due to air resistance.

Have you tried it? I have. It's quite startling the first time you put a bunch of helium balloons in your car, accelerate away from a stoplight, and have them all crowd up against the windshield.

In an accelerating car, the air sloshes toward the back, producing a pressure gradient. The helium balloons, being ligher than air, will be crowded out by the sloshing air and will drift toward the area of lowest density, which is in the front.

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#76
post #36

Bizarre. Yes, Googling an answer to a Google interview question from SO is in fact verboten. A seasoned interview can normally pick that up anyway. But a note to potential Google interviewees: if you're caught doing this it will pretty much disqualify your application. We're interested in how you think and how you solve problems, not what you can pass off as knowing. Interestingly, he mentions the NDA and then goes o…

Some bit-twiddling questions are a fair game to ask even for folks who haven't done low-level C and C++. Asking esoterica from Hacker's Delight (an excellent book, by the way, but in no way a source of interview questions), is not, but I doubt Google does this.

Bitwise operators are just as available in Java. I've done bit-twiddling in production Java code, it's something you need to do if you ever, e.g., work on a serialization library.

Understand, words, bits, bytes, and bitwise operators (big part of How Computers Work (TM)(R)) is something worth knowing (and not just to pass an interview).

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#77
post #36

Bizarre. Yes, Googling an answer to a Google interview question from SO is in fact verboten. A seasoned interview can normally pick that up anyway. But a note to potential Google interviewees: if you're caught doing this it will pretty much disqualify your application. We're interested in how you think and how you solve problems, not what you can pass off as knowing. Interestingly, he mentions the NDA and then goes o…

[deleted]

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#78
The best coders I've ever worked with rarely memorized the nuance little algorithms that they want you to regurgitate during these interviews. The ones that I know that are capable of this are terrible coworkers because they lack other necessary skills to function in an organization or team environment. This is anecdotal but sort of sticks with me.

The interview processes used by these software giants weeds out the kinds of people that have made the biggest differences in the companies I've worked for/with. From my experience they weigh their judgement much more heavily on the actual implementation of code instead of the understanding of code, decisions and overall design.

Knowing how to code a mergesort is not as important to understanding the wider uses of mergesort and when an altered algorithm would suit the problem best or when it would struggle to provide you the right performance at all.

Maybe these companies want code monkeys that can put down exactly as the design is given to them and the process works grand for them, but from an outsider looking in it seems like they miss out on a lot of great talent due to the rigorous screening process.

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#79

Earlier quoted context omitted.

That's fair, but that's not the sort of position Google is hiring for. We value general computer science more highly than specific Javascript (for example) experience. I can't offer an explanation or analysis of that, but that's how it is. (But if you do have specific experience and know the basic CS, that's ideal.) Other companies do the opposite, so there's plenty of jobs for either type of person.

> We value general computer science more highly than specific Java[S]cript (for example) experience. Perhaps this is why Google's JavaScript is so notoriously poor.

What metrics do you use to declare it "notoriously poor"?

Re: Interviewing at Google, Facebook, Foursquare, Dropbox, Fog Creek, etc

#80
post #13

Great overview of the different interview styles being used. I cannot say I am convinced you always get the best people through. I don't have any aspirations to interview at Google, but did stumble across an 'Google Interview' book at the local bookstore. It makes great reading. WSJ did an article on Google interviews late last year, including answers. Here are the questions (click the link below if you want answers)…

The explanation given in wsj for problem 2 is totally wrong. The balloon will do the same as a person in the car (nod backwards), only less pronounced due to air resistance.

I can assure you that the wsj is correct! I've been transporting balloons a bit lately* and having fun watching them 'lean in' to turns, 'leaning back' while braking, and 'leaning forward' while accelerating.

*transporting balloons correlates strongly with transporting kids

Post reply on HN