Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Get that job at Facebook (2012)

facebook.com

Post reply on HN
Print view View original

11–20 of 174 posts

Re: Get that job at Facebook (2012)

#11

Post by tezka »

strandev wrote: post #6
jamesaguilar wrote: post #5

One thing I have seen repeatedly in interviews for engineering positions of all levels is people who have not gone back and reviewed the basic algorithms they learned in second year. I know coding questions as posed in interviews are not the best measure of job performance, but they are also one of the few we have that is guaranteed to be sourced from the candidate in question. To perform well at these sorts of quest…

If you agree that these types of questions are not a good measure of job performance, why encourage this line of questioning? Wouldn't it be better for the industry as a whole to discover better ways to determine future job performance?

knowing these are not going to guarantee good performance. But not knowing them is a clear indication of incompetence. A programmer who doesn't know basic algorithms and data structure is a bad programmer.

Re: Get that job at Facebook (2012)

#12

Post by paolovictor »

jamesaguilar wrote: post #5

One thing I have seen repeatedly in interviews for engineering positions of all levels is people who have not gone back and reviewed the basic algorithms they learned in second year. I know coding questions as posed in interviews are not the best measure of job performance, but they are also one of the few we have that is guaranteed to be sourced from the candidate in question. To perform well at these sorts of quest…

Agreed. Even though some interview coding questions are a bit absurd, having a good grasp of basic algorithms and data structures shows that you at least care a little bit about _how_ things work.

Re: Get that job at Facebook (2012)

#13

Post by jmspring »

jamesaguilar wrote: post #5

One thing I have seen repeatedly in interviews for engineering positions of all levels is people who have not gone back and reviewed the basic algorithms they learned in second year. I know coding questions as posed in interviews are not the best measure of job performance, but they are also one of the few we have that is guaranteed to be sourced from the candidate in question. To perform well at these sorts of quest…

Basic data structures and algorithms are worth noting, but most of these formulaic interviews seem too focus on an academic base rather than an experience base -- probably good for someone who is only a few years experience.

I've turned down a couple of companies that take the formulaic approach. In most cases, I've not been looking. So, if you reach out to me, there is something in my background that is interesting, and I expect contact to be based around that.

As a counter, when I interview a candidate, I mostly avoid typical questions and try and ask questions intersecting the candidate background and what we are up to. If that is a stretch, I prefer focusing in on a passion or project and talking about the design/implementation challenges there.

Google and Facebook seem to have similar approaches, and because of the number of resumes they get have set up a formulaic system. It probably gets a certain level of quality, but probably also puts artificial caps at the high end.

Re: Get that job at Facebook (2012)

#15

Post by jonathanjaeger »

coldcode wrote: post #4

Why? Work 70 hours a week finding new ways to put more ads in people's lives.

Don't trivialize Facebook. There's no other place online that so easily melds chat, messaging, wall posts, and general keeping up with those closest to you (even when they're not close to you physically). Despite its problems, Facebook provides a lot of utility for many people without having to be cynical about it. I'll put up with all the ads that are somewhat relevant and are not so obtrusive to the extent that they are popups.

Re: Get that job at Facebook (2012)

#18

Post by jamesaguilar »

strandev wrote: post #6
jamesaguilar wrote: post #5

One thing I have seen repeatedly in interviews for engineering positions of all levels is people who have not gone back and reviewed the basic algorithms they learned in second year. I know coding questions as posed in interviews are not the best measure of job performance, but they are also one of the few we have that is guaranteed to be sourced from the candidate in question. To perform well at these sorts of quest…

If you agree that these types of questions are not a good measure of job performance, why encourage this line of questioning? Wouldn't it be better for the industry as a whole to discover better ways to determine future job performance?

I don't set interviewing policy at my company, and anyway I'm unfamiliar with any technique that provides better results. I suppose finding it is a direction of research that would be interesting, but I have a full time job just being an engineer.

My comment is only meant as practical advice to candidates. It is not normative.

Re: Get that job at Facebook (2012)

#19

Post by losethos »

Come to work for God on His temple. Vow of poverty. God is your inheritance.

God says... outer Catastrophic_Success forgot Romania speaks shape meanly Contain take_the_day_off assigned amazing failure_to_communicate buyers glowing procured enmity lungs long bitter Since -the amidst foolish Very perceiveth everything impatient walking foresignify Here fathers' do_you_have_a_problem beholder //promo soaring hey_Mikey_he_likes_it gnawing stiffneckedness shineth curest hour poet divisions allow Love Switzerland unhealthiness ornamenting baggage contact seek inflamed do_it goal folded comprehending follow modes masters

----

Sisteen chapel, anyone? Artists needed.

----

God says...

16:43 And all the people departed every man to his house: and David returned to bless his house.

17:1 Now it came to pass, as David sat in his house, that David said to Nathan the prophet, Lo, I dwell in an house of cedars, but the ark of the covenant of the LORD remaineth under curtains.

17:2 Then Nathan said unto David, Do all that is in thine heart; for God is with thee.

17:3 And it came to pass the same night, that the word of God came to Nathan, saying, 17:4 Go and tell David my servant, Thus saith the LORD, Thou shalt not build me an house to dwell in: 17:5 For I have not dwelt in an house since the day that I brought up Israel unto this day; but have gone from tent to tent, and from one tabernacle to another.

-----

We're going to have a pet elephant.

God says... delete pangs resting-place lined Print attaining After Beauty venerable ARE flashes Ridiculous gulf closes watch_it_buddy telling Bouverie opened reformed plot IX endure boyish constitute Catholic Archive

okay, no pet elephant.

Re: Get that job at Facebook (2012)

#20

Post by robryan »

jamesaguilar wrote: post #5

One thing I have seen repeatedly in interviews for engineering positions of all levels is people who have not gone back and reviewed the basic algorithms they learned in second year. I know coding questions as posed in interviews are not the best measure of job performance, but they are also one of the few we have that is guaranteed to be sourced from the candidate in question. To perform well at these sorts of quest…

If someone doesn't know how to approach an algorithms problem why not get them to show you how they would google around and puts the pieces together.

If they have no idea, they are likely going to google and follow the wrong advice. If they have an idea but have forgotten the specifics they will know where to go and which advice to take.

Post reply on HN