4 ms·
Although I complained about the lack of feedback in another thread here[1], I was pretty surprised by the number of people who hated take-homes and refused to d
by solardev 3y ago
Although I complained about the lack of feedback in another thread here[1], I was pretty surprised by the number of people who hated take-homes and refused to do them at all.
Why is that? Personally, even though I spent two days working on it and ultimately failing it, it was one of my favorite interview processes ever... way more efficient use of time for both parties, IMHO, and a better way to measure the actual skill set. And it was fast! I did the assignment in a couple days and then heard back from them in another day. That's way better than the other interview gauntlets I've had to run, which usually included 3-4 rounds of talking to a bunch of people, with weeks or sometimes months in between, and most of those folks are people I will never see again after the interview cycle.
And there's also not the absurd pressure and ambiguities of real-time whiteboarding or live coding, which is not at all representative of how people normally work (with access to the internet, their preferred workstation and IDE, etc.). Having gone through one of those sessions, THAT feels way more like a "dance, monkey, dance" bullet dodged vs the casual take-home.
By contrast, a take-home gives me a "just pretend it's a normal work day and show us how you work" situation and I can focus on the problem at hand instead of the politics of hiring. Isn't that a good thing...? What am I missing?
[1]: My complaint was about the lack of feedback after a take-home, not the take-home itself (which was actually illuminating and fun): https://news.ycombinator.com/item?id=36446949 https://news.ycombinator.com/item?id=36446949
- shakes_mcjunkie 3y agoI largely agree that take home assignments are better than the alternative.
- MathMonkeyMan 3y agoThe problem with take-home assignments, I suspect, is that nobody reads them. You don't read somebody's github portfolio, you don't really read their resume, and you certainly don't read their exquisitely written, commented, documented, and tested take-home project. If you even skimmed it, you're not going to sit down and summarize your impression. I'm not saying that all interviewers are lazy or bad, but most of the ones I've worked with are. Hell, maybe even I am. Time spent interviewing is time not spent working on things that you might actually be incentivized to do well.
- thesnide 3y agoTime spent on interviews is time invested. Now, it is up to you to ensure that you give an accurate filter to HR, so you can do focused investments. And interviews investment is like financial ones. You invest in multiple promising parties and expect one to outperform the others enough to make a great overall return. Long story short, hiring is your most important activity. As if you don't hire, or worse, hire badly, you won't have the firepower when you'll need it. And if you won't need the firepower, why are you interviewing candidates?
- MathMonkeyMan 3y agoI'm taking the "just following orders" perspective of an engineer in a large organization. I've heard that in FAANG, giving interviews was an unspoken prerequisite to promotion -- that's at least incentive to _do_ interviews. In the places where I've worked, I'm not sure there was much incentive to do interviews, and there was _no_ incentive to do them well. So, few interviews were done well. Maybe somebody further up the ownership ladder would recognize that a company is just a group of people, and hiring well makes the company. But those owners do not participate in the interviews. edit: Those owners delegate hiring to others, reasonably, but every layer of delegation changes the incentives.
- kayodelycaon 3y agoPersonally, I have more enjoyable things to do with my time than spend a day doing something no one else will spend more than 5 minutes on before deleting it. I’d rather spend a day preparing a D&D game for 6 people who will have fun for 4 hours. Once the game is over, we’ll have memories of a time we spent together. Alternatively, I’ve spent a lot of time playing with Home Assistant. The end result has been automation I use on a daily basis. That’s why I don’t like them.
- majormajor 3y agoI've never seen a takehome that wasn't just one step out of 5 or 6 calls/panels. I've gone through 4 or 5 at this point and they've been anywhere from 30 minutes to 6 hours for a single step (one takehome I had was fizzbuzz, another was super complicated) instead of a 45min-to-1-hr phone call. A "takehome and debrief" call wouldn't be too bad as an alternative to a full day of panels, but I've never personally come across it.
- Aeolun 3y ago> the absurd pressure and ambiguities of real-time whiteboarding or live coding, which is not at all representative of how people normally work How do you qualify “build us a full system with tests and everything in 6hr plx”?
- solardev 3y agoThat sounds like a good one to nope out of lol
- paulcole 3y agoI love it when people who are smarter and more qualified than me refuse to do take home assignments. Gives me a better chance to get the job!
- colechristensen 3y agoIf you want two days of my time I’m going to invoice you for $4,000, a fair rate for a short no notice job. I don’t have two days to give away for free to potentially multiple prospective employers. Why? That’s none of anybody’s business.
- solardev 3y agoYou probably value your time more :) As someone currently unemployed, my time isn't worth much, and I look forward to having something productive to actually work on. Even when I was employed full time, my skill set definitely wasn't worth anywhere near $2000 a day lol.