3 ms·

I disagree with the author that this is a "puzzle question" that requires an "a-ha" moment. Quite the opposite, it is an easily solvable algorithmic question (m

I disagree with the author that this is a "puzzle question" that requires an "a-ha" moment. Quite the opposite, it is an easily solvable algorithmic question (maybe with a little guidance after the candidate suggest suboptimal solution). Also, the good thing from the candidate point of view is that it is the sort of questions you can prepare for.

sergiotapia 12y ago
>sort of questions you can prepare for. The point is why do you need to prepare for and regurgitate these silly answers that you will almost assuredly never ever ever use in your day to day job?
- eweise 12y ago
  +1 to that. Most programming jobs are about integrating a bunch of different technologies together to solve a business problem. In 20 years I've never written a linked-list or sorting algorithm for work yet interviews are increasingly narrowly scoped to algorithm questions. I've found that these questions are usually asked by young people because they are fresh out of school and have been led to believe that knowledge of algorithms is the most important consideration. Give them a decade of creating products based on css, html, node.js, nosql, yessql, etc and they will come to realize that programming is more about understanding what a customer needs and finding the most efficient way of delivering a solution. Ability to work with other, lead a team, write clearly, explain to customers the tradeoffs and costs of different solutions are actually way more important than knowing how to find a cycle in a linked list.
  - twistedpair 12y ago
    But how do I test all of that in 30min or less? Do I have to actually get to know the person, their work history and their strengths? Does that mean I have to read the resume before I enter the room?
Marazan 12y ago
Did you miss the part where it took 12 years to come up with this solution?
joesmo 12y ago
Well one can prepare by memorizing a ton of algorithms and hope to get lucky and get asked the questions about those they happened to study or by actually studying up on what's relevant to the job, which random algorithms that can be looked up on Google most certainly is not. It's impossible to do both--it's difficult enough concentrating on one area. I know which engineer I'd hire. Then again, I wouldn't ask such useless questions in the first place.

sergiotapia 12y ago

>sort of questions you can prepare for. The point is why do you need to prepare for and regurgitate these silly answers that you will almost assuredly never ever ever use in your day to day job?

eweise 12y ago
+1 to that. Most programming jobs are about integrating a bunch of different technologies together to solve a business problem. In 20 years I've never written a linked-list or sorting algorithm for work yet interviews are increasingly narrowly scoped to algorithm questions. I've found that these questions are usually asked by young people because they are fresh out of school and have been led to believe that knowledge of algorithms is the most important consideration. Give them a decade of creating products based on css, html, node.js, nosql, yessql, etc and they will come to realize that programming is more about understanding what a customer needs and finding the most efficient way of delivering a solution. Ability to work with other, lead a team, write clearly, explain to customers the tradeoffs and costs of different solutions are actually way more important than knowing how to find a cycle in a linked list.
- twistedpair 12y ago
  But how do I test all of that in 30min or less? Do I have to actually get to know the person, their work history and their strengths? Does that mean I have to read the resume before I enter the room?

Marazan 12y ago

Did you miss the part where it took 12 years to come up with this solution?

joesmo 12y ago

Well one can prepare by memorizing a ton of algorithms and hope to get lucky and get asked the questions about those they happened to study or by actually studying up on what's relevant to the job, which random algorithms that can be looked up on Google most certainly is not. It's impossible to do both--it's difficult enough concentrating on one area. I know which engineer I'd hire. Then again, I wouldn't ask such useless questions in the first place.