QuoteOriginally posted by: GamalQuoteOriginally posted by: katastrofaThen I (or my team, to be more precise) got burned a few times.Sorry about it.Do you edit your cv in a similar way that you edit forum posts of you opponents?

QuoteOriginally posted by: katastrofaQuoteOriginally posted by: CluelessCppQuoteIf you're any good as a programmer, you can write FizzBuzz or a function to reverse an array in-place on a piece of paper. If you can't, go back to school.And what does that tell you?It tells me that they're not one of the 90% or so candidates who claim to be able to program but aren't.Aehh, ok then (but what if the candidate can write FizzBuzz?). I still think that FizzBuzz is too trivial to be useful and anything more complex is not suitable for a white-board.

It's like triaging the victims of a car crash. If they can do FizzBuzz, they pass to the next stage. And I disagree about more complex algorithmic problems not being suitable for paper coding. You can also do pair programming during interviews. But you don't want to do it with every candidate - it takes too much time. So first you test them on simpler stuff to weed out the losers.

QuoteOriginally posted by: katastrofaYou can also do pair programming during interviews.Do you also regularly do pair programming on the job or is this just something you would do for the interview?

A couple of times I was marked as "overqualified" and didn't get any offer. So if I was less brilliant in the tests, their approach would be more positive.Interview tests have no sense.

QuoteOriginally posted by: GamalA couple of times I was marked as "overqualified" and didn't get any offer. So if I was less brilliant in the tests, their approach would be more positive.Interview tests have no sense.Was it an euphemism? A euphemism is a generally innocuous word or expression used in place of one that may be found offensive or suggest something unpleasant.[1] Some euphemisms are intended to amuse; while others use bland, inoffensive, and often misleading terms for things the user wishes to dissimulate or downplay. Non-native speakers of English can have difficulty 'translating' the ephemism to the real intent.

QuoteOriginally posted by: GamalA couple of times I was marked as "overqualified" and didn't get any offer. So if I was less brilliant in the tests, their approach would be more positive.They probably had another reason why they didn't want you.

QuoteOriginally posted by: CluelessCppQuoteOriginally posted by: katastrofaYou can also do pair programming during interviews.Do you also regularly do pair programming on the job or is this just something you would do for the interview?On the job? Rarely. But it's a good way of interviewing a programmer.

QuoteOriginally posted by: CuchulainnQuoteOriginally posted by: GamalA couple of times I was marked as "overqualified" and didn't get any offer. So if I was less brilliant in the tests, their approach would be more positive.Interview tests have no sense.Was it an euphemism? A euphemism is a generally innocuous word or expression used in place of one that may be found offensive or suggest something unpleasant.[1] Some euphemisms are intended to amuse; while others use bland, inoffensive, and often misleading terms for things the user wishes to dissimulate or downplay. Non-native speakers of English can have difficulty 'translating' the ephemism to the real intent.It often simply means "too expensive" or "likely to be bored out of his/her mind doing the job", which are both legitimate concerns. It occasionally means "too old", which is not, at least in the US.

QuoteOriginally posted by: bearishQuoteOriginally posted by: CuchulainnQuoteOriginally posted by: GamalA couple of times I was marked as "overqualified" and didn't get any offer. So if I was less brilliant in the tests, their approach would be more positive.Interview tests have no sense.Was it an euphemism? A euphemism is a generally innocuous word or expression used in place of one that may be found offensive or suggest something unpleasant.[1] Some euphemisms are intended to amuse; while others use bland, inoffensive, and often misleading terms for things the user wishes to dissimulate or downplay. Non-native speakers of English can have difficulty 'translating' the ephemism to the real intent.It often simply means "too expensive" or "likely to be bored out of his/her mind doing the job", which are both legitimate concerns. It occasionally means "too old", which is not, at least in the US."candidate has answers for which we don't even have questions"?

QuoteOriginally posted by: CuchulainnQuoteOriginally posted by: bearishQuoteOriginally posted by: CuchulainnQuoteOriginally posted by: GamalA couple of times I was marked as "overqualified" and didn't get any offer. So if I was less brilliant in the tests, their approach would be more positive.Interview tests have no sense.Was it an euphemism? A euphemism is a generally innocuous word or expression used in place of one that may be found offensive or suggest something unpleasant.[1] Some euphemisms are intended to amuse; while others use bland, inoffensive, and often misleading terms for things the user wishes to dissimulate or downplay. Non-native speakers of English can have difficulty 'translating' the ephemism to the real intent.It often simply means "too expensive" or "likely to be bored out of his/her mind doing the job", which are both legitimate concerns. It occasionally means "too old", which is not, at least in the US."candidate has answers for which we don't even have questions"?42

QuoteOriginally posted by: katastrofaQuoteOriginally posted by: CluelessCppDo you also regularly do pair programming on the job or is this just something you would do for the interview?On the job? Rarely. But it's a good way of interviewing a programmer.Really? That programmer gets a completely different impression of how you do actually work and you will likely have no idea how that programmer will actually perform on the real job.

QuoteOriginally posted by: katastrofaQuoteOriginally posted by: GamalA couple of times I was marked as "overqualified" and didn't get any offer. So if I was less brilliant in the tests, their approach would be more positive.They probably had another reason why they didn't want you.Maybe yes, maybe no. I know only words of other people, not their thought.

QuoteOriginally posted by: CluelessCppQuoteOriginally posted by: katastrofaQuoteOriginally posted by: CluelessCppDo you also regularly do pair programming on the job or is this just something you would do for the interview?On the job? Rarely. But it's a good way of interviewing a programmer.Really? That programmer gets a completely different impression of how you do actually work and you will likely have no idea how that programmer will actually perform on the real job.It's not a 100% solution, I agree. But it beats relying solely on CVs.

Brain teasers! What is this? Second grade?lol.I remember one interview where the guy asked me some silly nonsense about balls in a hat, or cards in a pack or some such nonsense. I flatly told him 'sorry don't know that answer' without listening. The look on his face was hilariouos. "can you just try". "nope sorry".They still ended up calling me for later rounds though. go figure.In the end though it did not work out at the final hurdle. About a year later the fund shut down that group i think. lol.Another time I interviewed at F.A.S.T at that famous IB. The girl asked me to write some code which printed out "*" in a certain pattern.Hilarious. She gave me 5 minutes alone to do it, which I used to check my messages. Never got called back for that though. About 6 months later Bear was done.I love that pattern.