4 ms·
The biggest problem I see with this isn't even that the questions are too onerous (which they are), it is that I know there is absolutely zero chance anyone on
by paxys 5y ago
The biggest problem I see with this isn't even that the questions are too onerous (which they are), it is that I know there is absolutely zero chance anyone on the other end is going to take the time to actually read and evaluate each of them.
My personal rule for the interviews process is – no matter how pointless it may seem, the company has to waste at least the same amount of time on it as they require me to. So 1:1 phone screens are fine. Onsite interviews are fine, even if it is like 6 rounds. Coding exercises are not, and this one is definitely not.
- TheChaplain 5y agoUhm... I've rejected numerous applicants because they simply couldn't code, despite what was written in their CV, and this through whiteboard or side by side. And I'm not talking complicated stuff, but simple things like reverse a string or implement the hashCode/equals-methods. I'm all for giving people a chance, but requiring at least some basic knowledge for a coding position is fair IMHO.
- freedomben 5y agoGiving people a take-home test that takes them hours, especially before you even invest 30 minutes on a phone call to make sure they actually have a shot, is not the only way to make sure they can code. You can easily do that in a 15 to 30 min pair session. It's a selfish way to make sure your company wastes minimal of the their own time, at the expense of the candidate's time. My days of working for companies that think that way (especially if they are in denial about it) are over.
- johntiger1 5y agoThe number of candidates far outstrips the time employees have to interview them
- harry8 5y agoIt's very simple. Don't pay placement agents tens of thousands of dollars for placing an advert and passing on cvs (at best - at worst biasing you the wrong way). Use that budget to pay the many candidates for their time. Short list of 30 candidates, you can pay each one $1k for time spent jumping through your hoops. Everything is better for everyone doing something like that, the company, the candidates who don't get hired and quality of candidates willing to go through the process. Just a straight up win.
- manholio 5y agoThat sounds good in theory until the company that does this is swamped by very strong applicants that have no intention in taking the job. The right balance is equality: I spend an hour, you spend an hour. Rapid CV filtering and coding quiz, then 30 minutes Skype interview to verify claimed abilities: coding, technologies etc. This will filter out 90% of applications and give you a pool of "real candidates" that you should treat with utmost respect. After this, if you need a 2 day coding test with production data, than you should call the candidate on site and pair them with one of your engineers full time for those 2 days.
- harry8 5y agoThis is nonsense. No strong applicant wants to waste time applying for a job that they don't want to earn less money than they'd get consulting. You'd get a few more who don't "know" they've always wanted to work for you since forever (ha) and instead want to find out about you, which is a win for you. Applying isn't a dead loss if you don't take it, allows you to be but more adventurous in your applications. "We want to hire Jill who is amazing but couldn't get the incentive to get her across the line is good information. There's still the barrier of applying with a cover letter etc which is a hoop applicants are not getting paid for. Paying applicants for their time once you know you want to talk to them at length is the right thing to do and a huge win for your company. Paying placement agents is just an expensive, dead loss providing zero value to anyone.
- manholio 5y ago
- sdeframond 5y agoThe number of companies hiring developers far outstrips the time any competent developer has to interview with them.
- freedomben 5y agoI've experienced this too, and after some experimentation I realized this is sometimes the result of a poorly written job description in the req. You'll still get crap applicants, but 30 seconds of resume looking usually gets you a decent way through it.
- zeckalpha 5y agoThere’s a distinction between a take home and a pair programming exercise. I am against the former but for the latter.
- paxys 5y agoIf you place an undue burden on applicants, just know that you are filtering away both the ones at the bottom who don't know how to code and have faked their resume, and the ones at the top who can't be bothered with jumping through your hoops because they have enough other options.
- freedomben 5y agoExactly. Years back when I was more naive about how things work, I would do the 4 to 8 hour challenges they would send me. After a few of those and getting responses like, "we're sorry but this position is now filled" (an hour after I submit) or "we're sorry but we've decided not to fill this position" I realized that a complete lack of respect for my time is actually an important and powerful signal about what it will be like to work for them. They don't mind stealing my weekend from me in bad faith (when they already had someone they wanted to hire), so I doubt they would mind working me into the ground. Once I started looking at the interview as a two way process (I'm evaluating them as much as they're evaluating me) things got a lot better.
- kybernetikos 5y ago> the company has to waste at least the same amount of time on it as they require me to If you are good, you will most likely get a job within a relatively few interviews. For the roles I'm trying to hire at the moment, we need to screen many tens of candidates, sometimes into the hundreds to find people who meet the basic competence level needed. As long as you are getting the outcome you desire and the market is as hot as it is, your rule is fine for you, but I think proposing it as a general principle doesn't work, because the scale of jobs you are considering is so much smaller than the scale of candidates we have to consider to find someone appropriate. I don't know what the answer is, but there has always been a shocking number of people with totally legitimate looking CVs and university credentials who apply for software development jobs without being able to read a line of code, let alone produce any.
- michaelt 5y agoIf you're having hundreds of resumes pass resume screening for every hire you make, have you considered your resume screening might not be working very well?
- kybernetikos 5y agoOf course! That's the exact problem we're talking about here. Résumés screens don't work very well - they provide much less information about whether or not someone can actually solve problems with code than almost anyone would expect. That's the entire reason that a simple programming task like 'fizzbuzz' has value. It's the reason people want candidates to do something in addition to providing their résumé.
- benhoyt 5y ago> there is absolutely zero chance anyone on the other end is going to take the time to actually read and evaluate each of them This is understandable to think, but is simply wrong -- I know because I'm a software engineer at Canonical who helps review these written submissions. They're sometimes read and reviewed by our CEO, though often he delegates that out to a pool of us reviewers. I always read mine thoroughly, whether they're 3 pages or 30. I don't have exact stats, but from where I sit maybe 80% of them are quality submissions. I'm not defending our interview process here: I agree with many that it's too long and could use improvement. But it's definitely unique and thorough.
- dennis_jeeves1 5y ago>I always read mine thoroughly, whether they're 3 pages or 30. I don't have exact stats, but from where I sit maybe 80% of them are quality submissions. Even if both candidates and the Canonical did this diligently, it is still ridiculous in my eyes, it's religion.
- manholio 5y agoRegardless, the asymmetry is offensively wide: it takes at least an order of magnitude more time to write a text than to read it. The candidate is also under pressure to create a well crafted and professional response, essentially a sample of his best writing. You on the other hand, can do a half-ass job reading it, stop for your lunch break and skip the questions you are not interested in - there is absolutely no written record or evaluation of your reading performance. You might read it but others might send it in the bin after the first paragraph. Why would a company put such a large onus on the candidate, and little to none on itself, while the same could be achieved in a 1 hour skype call, where all these questions could be explored in depth in a symmetrical fashion? The only rational answer is that the company has complete disregard for the candidates and actively seeks out submissive people that lend themselves to easy abuse.
- ggeorgovassilis 5y agoIn the process of an interview I'd also like to learn something about the company and the job. Such practices require a substantial upfront effort from the candidate without them learning anything about the job they are applying to.
- glenngillen 5y agoIn the early days of Heroku, the founders had the same equitable investment from all participants approach to interviewing. I loved it. It really forced me to reconsider a lot of very standard hiring practices. It didn’t prevent take home coding challenges. But your never, as a hiring manager, going to spend 4 hours reviewing each submission. How much are you going to spend? 30mins? Ok, then the assignment can only be expected to take at most 30mins to complete. The hiring process we had there had its own problems and biases. I did love this simple heuristic for quickly assessing what was fair though.