3 ms·

I usually give his answer (but in Python), and every now and then the interviewer will make your same mistake (if if, not if else if) Delightfully awkward, the

I usually give his answer (but in Python), and every now and then the interviewer will make your same mistake (if if, not if else if) Delightfully awkward, the worst was the guy who didn't believe me and popped up a shell to test it. What's the appropriate social response when someone trips over their own weed-out question?

camperman 10y ago
Something like: do I really want to work with you? :)
- daveguy 10y ago
  Nah. Something like: It's ok, don't let it get to you. Technical interviews are hard.
  - camperman 10y ago
    True. I interviewed a guy once who found a bug in my example code so I hired him on the spot.
animal531 10y ago
If I were asked I might just go verbally, well; for i from 0 to 100, if i mod print fizz, else if etc. Followed by test it, check loop conditions, edge cases, representative number of ifs and prints for each type; put a header on the code with a description and we're done. For me it's not about getting it 100% correct, its about showing that you can do basic programming and know how computers work, followed by the simple breaking down of a concept into a program. The rest I consider details. Even if you implemented it 100%, its so simple that it doesn't nearly guarantee that you will do the same for a large program. And if you don't get it 100% correct, as long as you roughly indicate some fields where you're going to test for issues I'd be more than happy about it. Thereafter the human factor/generics, for example did it take you 30 minutes to think this up or was it pretty much rapid-fire? How learned of a response is programming to you? But as to your question; people don't really like being showed up, but that works well for filtering for you as well. If he hated it then it might very well not be a place/person you want to work with.
fucknode 10y ago
you leave the interview and say you're not interested in the company anymore :P

camperman 10y ago

Something like: do I really want to work with you? :)

daveguy 10y ago
Nah. Something like: It's ok, don't let it get to you. Technical interviews are hard.
- camperman 10y ago
  True. I interviewed a guy once who found a bug in my example code so I hired him on the spot.

animal531 10y ago

If I were asked I might just go verbally, well; for i from 0 to 100, if i mod print fizz, else if etc. Followed by test it, check loop conditions, edge cases, representative number of ifs and prints for each type; put a header on the code with a description and we're done. For me it's not about getting it 100% correct, its about showing that you can do basic programming and know how computers work, followed by the simple breaking down of a concept into a program. The rest I consider details. Even if you implemented it 100%, its so simple that it doesn't nearly guarantee that you will do the same for a large program. And if you don't get it 100% correct, as long as you roughly indicate some fields where you're going to test for issues I'd be more than happy about it. Thereafter the human factor/generics, for example did it take you 30 minutes to think this up or was it pretty much rapid-fire? How learned of a response is programming to you? But as to your question; people don't really like being showed up, but that works well for filtering for you as well. If he hated it then it might very well not be a place/person you want to work with.

fucknode 10y ago

you leave the interview and say you're not interested in the company anymore :P