4 ms·
> a take home technical exercise > prove to me you can (do the work) A take home exercise only proves they can get the work done elsewhere. It doesn't prove t
by stronglikedan 9y ago
> a take home technical exercise
> prove to me you can (do the work)
A take home exercise only proves they can get the work done elsewhere. It doesn't prove that they actually did it.
- phendrenad2 9y agoThis whole thing misses the point. We need WhiteboardFreeAndAlsoTakeHomeFree. In other industries, my resume and a quick discussion verifying that I actually did the work I said I did is suffficient
- mkohlmyr 9y agoI really don't buy that a resume alone can sufficiently put across your actual level of ability as a Software Engineer. And there are plenty of people who are better talkers than doers. One way or another I think it's entirely reasonable to want to see actual code. If you want to do that by way of an open source portfolio, sure. But not everyone has open source contributions, so then I would need some other process for acquiring a work sample. I have seen many people here say you should hire people on a contract basis for a few days/a week. I don't know what it's like doing that in the US, but for the UK market that sounds like a ton of administrative overhead for both parties to take on in order to establish if they are even a good fit.
- sidlls 9y agoThis style of interview works in plenty of other professions that are much more rigorous than software development. You'll be hard pressed to find an aerospace engineering company that is going to ask candidates to evaluate integrals on the whiteboard that they'd normally look up in the CRC or implement a numerical solution for (probably using a prepackaged library), for example. Yet you're proposing an analog of this very thing here.
- actionowl 9y ago> But not everyone has open source contributions In my experience, anyone we've hired WITH open source contributions has been 10x better than those without.
- brianwawok 9y agoSo say you are at a job. fairly happy. Maybe not your dream job, but you decide to look around and interview with me. I could present you two options: 1) I just hire you after a 30 minute chat. 50% you don't work out, and we fire you after 30 days. 2) We have a longer interview. We whiteboard. We take home test. We whiteboard some more. 90% chance that you don't get fired after 30 days. Which would you prefer? As a business owner, I am happy to just try people I don't know well - IFF they are willing to accept that there is a very good chance they are fired within the first 30 days. There is such a huge range in developers. The haves vs the have-nots can be a 100x different productivity difference. I really want to try to tease that difference out. It is really really hard.
- Clubber 9y ago#1. I'm totally fine with firing after 30 days if I don't work out. I'm positive it won't, so I'd prefer to prove myself doing real work. That's the way it used to be done and I think we should go back to doing that. Read the resume, ask some questions about the resume, 30 minutes to an hour full interview, done. You get hired on, put on a probationary period, if they don't work out, fire them.
- rattaz 9y agoNo way! The lamers you end up firing (after 30 days' pay) will easily make a living out of it. They could even be PARALLEL lamers, pulling 30 days pay off multiple sucker companies.
- brianwawok 9y agoHah, you should be able to see the pattern pretty quick? Wow, 8 jobs last year? Busy life?
- miranda_rights 9y agoIt seems like they could easily drop half of those jobs off of their resume. That's usually the advice given for people who leave jobs after a short period.
- mkohlmyr 9y agoThat's (among other things) what the walkthrough / debrief is for. I like the format, but it obviously has other downsides, such as a higher up-front investment from the candidate. That being said I found the format enjoyable last time I went through it. It was less stressful during the interview itself, and I felt more confident walking in. I would recommend it to companies who are considering it.
- mrfusion 9y agoThat would show you they have a strong network of good coders and can communicate specs and get quality code done in a timely manner. You should hire them for management!