4 ms·

> they have kids and don't have time or energy for that I don't have a lot of sympathy for this argument. If they have time to take half a day to go to an int

> they have kids and don't have time or energy for that I don't have a lot of sympathy for this argument. If they have time to take half a day to go to an interview, then it doesn't seem like it should be much different to take half a day to work on an interviewing problem.

em-bee 4y ago
usually both are required, so now it adds up to a full day. if i interview at 10 companies suddenly a lot of vacation time is gone. so i am not going to take time off until i am reasonably certain that i want this job and can get it if i pass. likewise i'll be willing to take time off for a take home assignment only when that is the last test i need to pass. if companies want the assignment before they'll even look at my CV, then that's to much. steps should be: look at the CV to see if the candidate is basically quslified. talk to the candidate to get to know them, answer any questions, agree on salary and benefits. once that is all sorted, bring on the coding test.
jasode 4y ago
>, then it doesn't seem like it should be much different to take half a day to work on an interviewing problem. But a lot of companies use the multi-hour coding homework as a preliminary filter before asking the candidate to take the "next step" to the half-day onsite interview. The coding homework is asymmetric work because the company doesn't have to expend their existing employees time on prospective candidates. In fact, a lot of companies let recruiters coordinate the coding homework so their existing employees spend the least amount of time on it. The onsite interview is more symmetric effort because both the interviewer and the candidate have to expend time together. There's a bit more commitment on the part of the company doing the hiring. I'm not complaining. Just stating how the different perspectives play out.

em-bee 4y ago

usually both are required, so now it adds up to a full day. if i interview at 10 companies suddenly a lot of vacation time is gone. so i am not going to take time off until i am reasonably certain that i want this job and can get it if i pass. likewise i'll be willing to take time off for a take home assignment only when that is the last test i need to pass. if companies want the assignment before they'll even look at my CV, then that's to much. steps should be: look at the CV to see if the candidate is basically quslified. talk to the candidate to get to know them, answer any questions, agree on salary and benefits. once that is all sorted, bring on the coding test.

jasode 4y ago

>, then it doesn't seem like it should be much different to take half a day to work on an interviewing problem. But a lot of companies use the multi-hour coding homework as a preliminary filter before asking the candidate to take the "next step" to the half-day onsite interview. The coding homework is asymmetric work because the company doesn't have to expend their existing employees time on prospective candidates. In fact, a lot of companies let recruiters coordinate the coding homework so their existing employees spend the least amount of time on it. The onsite interview is more symmetric effort because both the interviewer and the candidate have to expend time together. There's a bit more commitment on the part of the company doing the hiring. I'm not complaining. Just stating how the different perspectives play out.