I failed a Twitter interview
qandwhat.apps.runkite.com
I failed a Twitter interview
1–10 of 86 posts
Re: I failed a Twitter interview
#2Cheer up, kid. That Justin probably didn't even know what you were talking about. Calculus is not for everybody. :-j
Re: I failed a Twitter interview
#3This question involves an "a-ha" moment (for the linear-time solution) and was thus banned from interviews at Google last year.
Don't use questions involving eureka moments. They reveal nothing about the candidate.
Edit: It should be noted that this question was used for a long time at Google, Microsoft, and many other places. It's a terrible question.
Re: I failed a Twitter interview
#4Did they actually call you back with a rejection? Sorry if I missed that in the article. Anyway, at the end of the day, what matters is that you solved it on your own :)
Re: I failed a Twitter interview
#5Twitter failed you with that interview. Unless the job actually does involve performing computational parlour tricks.
Re: I failed a Twitter interview
#6Google cache: http://webcache.googleusercontent.com/search?client=ubuntu&c...
It's off-line for me and asking something about installing a server.
Re: I failed a Twitter interview
#7[deleted]
Re: I failed a Twitter interview
#8I wonder if Jack Dorsey could solve rhat right.
Re: I failed a Twitter interview
#9you could solve this with a simple state machine; there's no reason to resort to parlour tricks...
Re: I failed a Twitter interview
#10This question involves an "a-ha" moment (for the linear-time solution) and was thus banned from interviews at Google last year. Don't use questions involving eureka moments. They reveal nothing about the candidate. Edit: It should be noted that this question was used for a long time at Google, Microsoft, and many other places. It's a terrible question.
I find it's best to ask easy questions (like fizzbuzz) and very hard questions. For easy questions you gauge fundamental competence, those should be things that decent devs can solve as fast as they can write, it makes it easy to weed out the folks who are clueless and somehow have trumped up resumes. For hard questions you go in with the expectation that you're not going to get a solution to the problem, so you concentrate on observing the process the candidate uses, their problem solving skills, communication, the sort of problems they're comfortable with tackling, and so on.