4 ms·
Wait, what is the difference between taking the time for an interview (no matter if via phone or in-person) and one for a gate-filter task?
by rglullis 8y ago
Wait, what is the difference between taking the time for an interview (no matter if via phone or in-person) and one for a gate-filter task?
- jclardy 8y agoThis is what I am wondering. The process at my company is a personal interview, coding challenge, then technical interview. So essentially about 4 hours of time. What makes this different from a company that wants 4 interviews from different managers, which likely takes up more time plus all of it being fixed time slots, versus having one hour of work that you can work on at your own pace?
- ldite 8y agoAn interview is a two-way process. I typically find out a lot about the company and the people I'll be working with. Even a 30 minutes phone call is as much for me to be able to filter them out.
- swish_bob 8y agoI get where you're coming from, and am in a similar position. On the other hand, I've used a coding test to drop a company before (completed the test and refused to submit it, told them the test gave me enough information to know I didn't want to work there). It gives you a hint as to what they think is important technically.
- mchannon 8y agoIn theory there shouldn’t be any, assuming it’s limited to an hour, both in description and in reality. In practice there’s a pervasive phenomenon called asymmetry of effort. The hiring manager may crib a task set either from a perfunctory google search or their own body part. The sum total of time spent on their part is often five minutes, including coming up with the problem and their review of your code. This follows no industry standard, and I can count multiple experiences where they were too inept to “grade” the homework assignment, thinking it didn’t work when it did, or that the problem set was impossible. The reason senior engineers in particular turn down homeworks is because they’ve been burned by them before, and the average hiring engineer tends to know less than they do (but as the hiring manager, can’t assess it, mistaking competence for arrogance or ineptitude). When a company is not willing to invest the same amount of time to interview as they ask of the candidate, it’s a strong signal of how serious they are as a quality employer. When job hunting as a senior, hearing about take homes (esp. early stage ones) is the young person’s dating equivalent of considering a relationship with someone divorced twice and a felony. You just get conditioned to pass up kissing frogs.
- kstenerud 8y agoSo what interview process tasks are acceptable to you in order to gauge your ability?
- mchannon 8y agoResume review, Phone screen (30 min), on-site (less than 2 hours), probationary period. Everything else is simply busy work for all parties because it doesn’t tell you anything you don’t already know, plus it scares away quality candidates.
- scarejunba 8y agoHmm, interesting. I don't know if it's legal for me to run different interview tracks for immigrant and domestic workers. If I'm hiring away an H-1B from somewhere else, probationary isn't going to work. They will not join since their residency depends on employment. But it appears that some domestic engineers prefer the shorter test series with a bigger opportunity to prove themselves. Does anyone know if having different tracks is legal?
- logfromblammo 8y agoSeconding this. Read the candidate's actual resume, spend 30 minutes trying to suss out any deception on it, then a couple of hours trying to gauge compatibility, and also sell the candidate on working for you. You don't even really need a probationary period in an "at will" state. At some point, you either trust the credentials from universities and certification bodies, and take what the resume says at face value, or you have to try to reinvent some wheels, and re-discover that eliminating the phonies and mimics is a very difficult problem that even the experts can't solve entirely. I don't know what the conversion factor is between running a fruitless job search filled with cargo-culted bozo tasks, and just randomly picking the first vaguely suitable candidate off the stack and letting them run for a few months, but I suspect that filling the position quickly and painlessly is probably worth about one month of having a 0%ile employee, or six months of a 20%ile, or keeping a 40%ile employee until they retire. This rests on the presumption that some work done right now is worth more than the same amount done some time in the future, and that higher %ile-ranked candidates will be less tolerant of any stupid hiring games.