5 ms·

Would you say the questions that fund asked you are relevant to the work you do (or would be doing) there? I think that's the core criticism most people levy ag

Would you say the questions that fund asked you are relevant to the work you do (or would be doing) there? I think that's the core criticism most people levy against the "high tech" interview questions.

segmondy 8y ago
People that don't get the offer tend to complain about such things. They are asking questions to measure how you think, to measure your potential, to see how you handle stress. If you are stressing over an interview, what will you do when you lose $1 million in 10 seconds?
- throwawaymath 8y ago
  Sure I get the gist, I've heard this reasoning quite a lot and I'm not condoning or condemning it. I was specifically interested in hearing if the OP thought the math they asked him about was relevant to the math actually done on the job. In my experience, it isn't really (except insofar as it might be the same field, from a 30,000 foot view).
- Timmah 8y ago
  I think it's more about measuring enthusiasm for problem solving. If you sulk and roll your eyes at a difficult math problem, what will your demeanor be like every day in the office when your job involves quant analysis?
  - emodendroket 8y ago
    I'm suspicious of any practice whose proponents offer multiple, incompatible rationales.
- emodendroket 8y ago
  Yes, people who get the job are less likely to complain about the process. I don't see that that vindicates the way it was performed.
- kanelbullar 8y ago
  If you are stressing over an interview, what will you do when you lose $1 million in 10 seconds? Beats me - but the "skills" demonstrated in the interview process you're defending -- "suck up; just keep going online until you memorize enough canned answers to most of these dang questions; suck up, suck up, suck up" -- certainly aren't going to help. If anything, they're basically orthogonal to the set of competencies needed to deal with that kind of a situation.
  - stcredzero 8y ago
    Beats me - but the "skills" demonstrated in the interview process you're defending -- "suck up; just keep going online until you memorize enough canned answers to most of these dang questions; suck up, suck up, suck up" -- certainly aren't going to help. Right. People who don't think of Comp Sci knowledge as a set of substantive first principles, just as meaningless tokens they need to memorize and regurgitate to get the job -- those are precisely the people who should be weeded out. Each one of those questions is not merely a chance to "collect" an arbitrary thing. It's also an opportunity to practice applying basic knowledge and techniques. If anything, they're basically orthogonal to the set of competencies needed to deal with that kind of a situation. You may well need to spot a deadlock or a race condition in code. You may well need to spot code that is inefficient by construction, in precisely that kind of situation.
    - pmiller2 8y ago
      > You may well need to spot a deadlock or a race condition in code. You may well need to spot code that is inefficient by construction, in precisely that kind of situation. How is that relevant to the practice of "memorizing enough canned answers to most of these dang questions"?
      - stcredzero 8y ago
        How is that relevant to the practice of "memorizing enough canned answers to most of these dang questions"? It's not. Instead, ask something not particular tricky, a bit open ended, and just a little bit involved (at least 3 things interacting) with the purpose of seeing if basic skills can be applied. Instead of looking for an answer that can be memorized, you're looking for evidence to see if people have actually designed, implemented, and debugged something at a level beyond gluing libraries together.
- s73v3r_ 8y ago
  That answer doesn't really hold up because the people coding the system aren't the ones doing the trading, and most jobs that use similar "stressful" interviews don't have anything like that anyways.
- make3 8y ago
  that doesn't justify asking questions that are extremely poor predictors of work performance
- sangnoir 8y ago
  > They are asking questions [...] to see how you handle stress. I've got a time-saving suggestion - instead of asking questions, measure how long interviewee holds up while being waterboarded. If they can handle that stress, they can handle losing $100 million in 10 seconds, easy.

segmondy 8y ago

People that don't get the offer tend to complain about such things. They are asking questions to measure how you think, to measure your potential, to see how you handle stress. If you are stressing over an interview, what will you do when you lose $1 million in 10 seconds?

throwawaymath 8y ago
Sure I get the gist, I've heard this reasoning quite a lot and I'm not condoning or condemning it. I was specifically interested in hearing if the OP thought the math they asked him about was relevant to the math actually done on the job. In my experience, it isn't really (except insofar as it might be the same field, from a 30,000 foot view).
Timmah 8y ago
I think it's more about measuring enthusiasm for problem solving. If you sulk and roll your eyes at a difficult math problem, what will your demeanor be like every day in the office when your job involves quant analysis?
- emodendroket 8y ago
  I'm suspicious of any practice whose proponents offer multiple, incompatible rationales.
emodendroket 8y ago
Yes, people who get the job are less likely to complain about the process. I don't see that that vindicates the way it was performed.
kanelbullar 8y ago
If you are stressing over an interview, what will you do when you lose $1 million in 10 seconds? Beats me - but the "skills" demonstrated in the interview process you're defending -- "suck up; just keep going online until you memorize enough canned answers to most of these dang questions; suck up, suck up, suck up" -- certainly aren't going to help. If anything, they're basically orthogonal to the set of competencies needed to deal with that kind of a situation.
- stcredzero 8y ago
  Beats me - but the "skills" demonstrated in the interview process you're defending -- "suck up; just keep going online until you memorize enough canned answers to most of these dang questions; suck up, suck up, suck up" -- certainly aren't going to help. Right. People who don't think of Comp Sci knowledge as a set of substantive first principles, just as meaningless tokens they need to memorize and regurgitate to get the job -- those are precisely the people who should be weeded out. Each one of those questions is not merely a chance to "collect" an arbitrary thing. It's also an opportunity to practice applying basic knowledge and techniques. If anything, they're basically orthogonal to the set of competencies needed to deal with that kind of a situation. You may well need to spot a deadlock or a race condition in code. You may well need to spot code that is inefficient by construction, in precisely that kind of situation.
  - pmiller2 8y ago
    > You may well need to spot a deadlock or a race condition in code. You may well need to spot code that is inefficient by construction, in precisely that kind of situation. How is that relevant to the practice of "memorizing enough canned answers to most of these dang questions"?
    - stcredzero 8y ago
      How is that relevant to the practice of "memorizing enough canned answers to most of these dang questions"? It's not. Instead, ask something not particular tricky, a bit open ended, and just a little bit involved (at least 3 things interacting) with the purpose of seeing if basic skills can be applied. Instead of looking for an answer that can be memorized, you're looking for evidence to see if people have actually designed, implemented, and debugged something at a level beyond gluing libraries together.
s73v3r_ 8y ago
That answer doesn't really hold up because the people coding the system aren't the ones doing the trading, and most jobs that use similar "stressful" interviews don't have anything like that anyways.
make3 8y ago
that doesn't justify asking questions that are extremely poor predictors of work performance
sangnoir 8y ago
> They are asking questions [...] to see how you handle stress. I've got a time-saving suggestion - instead of asking questions, measure how long interviewee holds up while being waterboarded. If they can handle that stress, they can handle losing $100 million in 10 seconds, easy.