4 ms·
(Article author here -- I'm one of the interviewers here as well.) Our technical interview is really designed to look for your strengths, such as being producti
by compumike 9y ago
(Article author here -- I'm one of the interviewers here as well.) Our technical interview is really designed to look for your strengths, such as being productive while writing clean, correct code in any language/environment of your choice. If you do well at that (or excel in other sections of the interview such as system design or knowledge questions), we're going to work with you as a candidate, regardless of the language you choose to interview in.
- jorgemf 9y agoStill is irrelevant. If you have 1 java position and 10000 Ruby positions, you are going to interview more Ruby developers, your data is going to match more closely the reality. For the 1 java position you are going to be more picky and discard more candidates. But even with the same number of candidates and positions your test are going to have bias, how do you know the java test is as difficult as the ruby test, it could be more or less difficult. You can do a proper analysis fixing some of the variables. For example you can fix the language and compare how the different editors affect the selection process. But still you have to show other variables as the years of experience in the language. And finally you have outlayers like who did an interview with you but was discarded because of living in a different country. But I guess I might have enter into the statistics.