3 ms·
Here's the thing for me. I try to be in the situation of trying to find the next job while I still have the old job. That means I'm not desperate. That also
by AnimalMuppet 7y ago
Here's the thing for me. I try to be in the situation of trying to find the next job while I still have the old job. That means I'm not desperate. That also means I'm still working a full-time job while I'm in the job-hunting process. For an interview, I'm probably going to have to take a vacation day. For an out-of-town interview, I might have to take two days. That's bad enough, especially since I might go through several different companies in the process of finding a job.
Now you want me to do a 2-4 hour work-sample test? And maybe 5 other companies do, too? No. Just no. I have a job, I have a life outside my job, and you're not going to abuse it with making me jump through this hoop. If I lose your job, so be it. I don't need to work for people who will abuse me in the hiring process, no matter how valid they think their reasons are.
Your intent isn't to abuse me. Your intent is to weed out candidates who were making it past your interviews, but still couldn't code. But the effect on me is still abusive, no matter what your intent is.
- tptacek 7y agoThe whole idea is not to make you have to take the vacation day to interview --- or at the very least, not to have to take the day unless you're assured you're technically qualified, and you're not going to get teched out on site. If the choice is between taking a vacation day to come on site and code on a company laptop with someone staring over your shoulder, or doing almost nothing other than a take-home problem that you can do wherever and whenever you want, tell me how we'd be the company making it impossible for you to fit us into your schedule?
- AnimalMuppet 7y agoHere's the way interviewing used to work: You got a pile of resumes. You picked the ones that looked the best. You called them and asked them some questions. The two or three best of those, you asked to come in for an in-person interview. Note how symmetric the time is. When you do a phone interview, they're on the phone and you're on the phone. It costs you as much time as it does them. When you invite them in for an interview, it costs you time to interview them, and it costs them time to be there. So you have an incentive not to waste the time of people you're not going to hire, because it also wastes your time. But with a code assignment, you can ask 100 people to each do 2-4 hours, while you just compile their results and run some test data at it. It takes them hours, and you minutes. When you ask me to come in for an interview, I know that you're serious about me before I commit to that kind of time. You're serious enough for you to commit that kind of time. But with a code assignment, how serious are you about me? Are you giving the assignment to 100 people to fill one position? I have no way of knowing. So the problem here is that, if you call me in for an interview, I expect that I am one of a small number of people. I expect that I have at least a 30% chance of landing the job. If you ask me to do an assignment as the first step, I don't think that. I think this is your first screening step, and therefore that I've got more like a 1% chance of landing the job. Now, maybe you don't operate that way, and my expectations don't match your statistics. (On the other hand, a real jerk of a company might lie about their statistics...) So that's why I say that it's abusive. If you ask me to spend 4 hours for a 30% chance at a job, I'll accept that. If you ask me to spend 4 hours for a 1% chance at landing a job, get lost. I don't have time to jump through your hoops.
- cpach 7y agoJust a thought: Have you considered narrowing the list of companies you are most interested in working for...? Let’s say someone in your top five list are interested in hiring you and then want you to spend four hours for the work test. Maybe then it would be worth it, even if the outcome is not certain?