Live data from Hacker News

Facebook Lost a Great Engineer

medium.com

11–20 of 64 posts

Re: Facebook Lost a Great Engineer

#11
"At my current company, we hire based on provable real-world experience."

That is also a pretty bad hiring schema, you are leaving out a great deal of potential great programmers that are just starting, so, which strategy is better? I guess you always leave people behind, if it works for you, it's the right choice, and it has been working for facebook.

Re: Facebook Lost a Great Engineer

#12

Writing an article to bash a company for not hiring him doesn't seem like what a great engineer would do.

Why not? I don't think it's healthful for a culture to impose a wide penalty on criticism.

Criticism, if constructive, is not 100% negative. The post indeed criticizes Facebook, but also lays down an explanation of why Facebook's hiring practices are wrong. It contains useful information.

Re: Facebook Lost a Great Engineer

#13

Yeah these sort of questions are pretty ridiculous. Though I wonder what the intent is here, say for the first question - "What is the pattern here ?" After looking up the solution on wikipedia - http://en.wikipedia.org/wiki/Look-and-say_sequence I would have to admit there is no way I'd figure that out without knowing the concept ahead of time. So are they looking for someone that knows the 'look and say sequence' e…

It looked like it was a simple L-system to me...

V : 1 2

ω : 1

P : (11 -> 21) (2 -> 12) (1 -> 11)

I think that matches the information given in the question. Would that be an "incorrect answer"?

Re: Facebook Lost a Great Engineer

#15

Yeah these sort of questions are pretty ridiculous. Though I wonder what the intent is here, say for the first question - "What is the pattern here ?" After looking up the solution on wikipedia - http://en.wikipedia.org/wiki/Look-and-say_sequence I would have to admit there is no way I'd figure that out without knowing the concept ahead of time. So are they looking for someone that knows the 'look and say sequence' e…

> Or did they actually expect someone to work it out on the spot ?

I just figured it out on my own, from the comfort of my home, while having breakfast. In an interview with a top notch company that'll be a totally different story.

Re: Facebook Lost a Great Engineer

#16

Writing an article to bash a company for not hiring him doesn't seem like what a great engineer would do.

I'm not sure it's really a bashing. I read it as he's glad after all that facebook didn't hire him, so it's more like a message for those who already "lost" or will "lose" in puzzle-based hiring process. A message that states it's not necessarily their (i.e. prospective employees) loss in the end, and the more important part that it's not a reason they should feel bad about themselves after such "loss", because solving riddles is about solving riddles and not about finding good programmers (being one doesn't necessarily exclude having puzzle-solving ability, but it's not like a symmetric difference of these sets is empty, really, more like quite voluminous, I would say).

Re: Facebook Lost a Great Engineer

#19

Yeah these sort of questions are pretty ridiculous. Though I wonder what the intent is here, say for the first question - "What is the pattern here ?" After looking up the solution on wikipedia - http://en.wikipedia.org/wiki/Look-and-say_sequence I would have to admit there is no way I'd figure that out without knowing the concept ahead of time. So are they looking for someone that knows the 'look and say sequence' e…

While I also doubt the value of this kind of questions in interviews, I don't think that figuring out this sequence is impossible. I figured it out by myself too when I saw it the first time. Of course that doesn't count for the increased stress levels in an interview situation.

Re: Facebook Lost a Great Engineer

#20
I understand that these questions can be ridiculous at times. But I think it is worth pointing out 2 things:

1) They may work well for a subset of applicants for a subset of companies. This, to some, is verification that these sorts of problems are a good way of narrowing down the applicant pool. Hence why they're used.

2) From Facebook (or any other employer)'s perspective, it's an incredibly hard job determining who will fit a given job specification. You may be great on paper, but be a total mismatch with regards to company ethos (I'm not saying you are, I'm just citing this as an example). The way (and that's assuming there is a particular way) of differentiating applicants and determining their suitability is not perfect. Different companies do it different ways, and all of this is constantly evolving. The fact that Facebook is using developers to conduct their interviews could be seen as progress to some compared to what there was x years ago in y company. It's never going to be perfect.

The fact that you've moved on from this and done a bunch of great stuff is fantastic. It's Facebook's loss. But instead of just commenting on why their system sucks, and why it didn't work for you, why not make some constructive suggestions on how it might be improved.

Post reply on HN