2 ms·

> Also, the focus is often on how you approach the problem, not if you write up a perfect solution or not. This is a common misconception. Unfortunately, most

by zerr 12y ago

> Also, the focus is often on how you approach the problem, not if you write up a perfect solution or not. This is a common misconception. Unfortunately, most (read 99%) interviewers expect you to come up with exactly the same solution they have in mind (or in paper/screen in front of them). Even if your solution is correct but different, as soon as you start to diverge from their solution, you're red-flagged.

azakai 12y ago
I'm not sure how you can be so certain? (99% of interviewers..?) I interviewed a bunch, but not for a few years. More recently, I've been on the other side of things. In all my experience: yes, some people expect a very specific answer from you, but not most. Most people look at how you approach the problem, how you solve it, and what questions you ask about it if you need any clarifications. You can often tell someone is a good programmer even if they don't fully solve a problem, or if they happen to pick an approach that doesn't work out. Again, that's my personal experience and knowledge, so I can't be sure how common it is.
- zerr 12y ago
  99% is exaggeration (or "hyperbolation" ), but I wanted to highlight the issue. From my personal experience, and from what I hear from others. In fact, I've never experienced "wants to know how you approach the problem" moment ever.
plorkyeran 12y ago
Do you have any sort of evidence to support this claim? As far as I can tell I've never had an interviewer reject me for coming up with a solution other than the one they wanted. At worst I've had people strongly nudge me in the direction they wanted me to go. I'm certainly willing to believe that terrible interviewers are out there, but I have trouble believing that I've hit the 1% every time.
- innocentoldguy 12y ago
  I have. I once had an interviewer ask me to write CSS code that generated an American flag. I used the nth-child selector to render 13 alternating red and white stripes. The guy asked me why I did that instead of making the background white and painting red stripes over the top of it. I didn't get the job and the reason the recruiter told me I was rejected was because my CSS code was wrong.

by zerr 12y ago

azakai 12y ago

I'm not sure how you can be so certain? (99% of interviewers..?) I interviewed a bunch, but not for a few years. More recently, I've been on the other side of things. In all my experience: yes, some people expect a very specific answer from you, but not most. Most people look at how you approach the problem, how you solve it, and what questions you ask about it if you need any clarifications. You can often tell someone is a good programmer even if they don't fully solve a problem, or if they happen to pick an approach that doesn't work out. Again, that's my personal experience and knowledge, so I can't be sure how common it is.

zerr 12y ago
99% is exaggeration (or "hyperbolation" ), but I wanted to highlight the issue. From my personal experience, and from what I hear from others. In fact, I've never experienced "wants to know how you approach the problem" moment ever.

plorkyeran 12y ago

Do you have any sort of evidence to support this claim? As far as I can tell I've never had an interviewer reject me for coming up with a solution other than the one they wanted. At worst I've had people strongly nudge me in the direction they wanted me to go. I'm certainly willing to believe that terrible interviewers are out there, but I have trouble believing that I've hit the 1% every time.

innocentoldguy 12y ago
I have. I once had an interviewer ask me to write CSS code that generated an American flag. I used the nth-child selector to render 13 alternating red and white stripes. The guy asked me why I did that instead of making the background white and painting red stripes over the top of it. I didn't get the job and the reason the recruiter told me I was rejected was because my CSS code was wrong.