←back to thread

Please stop the coding challenges

(blackentropy.bearblog.dev)
261 points CrazyEmi | 5 comments | 15 Nov 24 15:32 UTC | HN request time: 0s | source
Show context
fishtoaster ◴[15 Nov 24 18:07 UTC] No.42149357[source]▶
I recently ran an interview process for a relatively senior eng role at a tiny startup. Because I believe different interview methods work better for different people, I offered everyone a choice:

1. Do a takehome test, targeted to take about 4 hours but with no actual time limit. This was a non-algorithmic project that was just a stripped-down version of what I'd spent the last month on in actual work.

2. Do an onsite pairing exercise in 2 hours. This would be a version of #1, but more of "see how far we get in 2 hours."

3. Submit a code sample of pre-existing work.

Based on the ire I've seen takehome tests get, I figured we'd get a good spread between all three, but amazingly, ~90-95% of candidates chose the takehome test. That matches my preference as a candidate as well.

I don't know if this generalizes beyond this company/role, but it was an interesting datapoint - I was very surprised to find that most people preferred it!

replies(7): >>42149441 #>>42149536 #>>42149571 #>>42149636 #>>42150136 #>>42150254 #>>42151318 #
bhhaskin ◴[15 Nov 24 18:17 UTC] No.42149441[source]▶
Why would you even do any of that for a senior role? I wouldn't waste my time with it, and it shows you don't know how to interview/evaluate for a senior position.
replies(6): >>42149512 #>>42149515 #>>42149540 #>>42149560 #>>42150471 #>>42151698 #
alkonaut ◴[15 Nov 24 18:32 UTC] No.42149560[source]▶
Because for a senior role you need to hire a person with senior role skills, I suppose. Just N years of experience at X company doesn't provide that. I'd rather look at someone's github repo than talk to their reference tbh.
replies(1): >>42149651 #
John_Cena ◴[15 Nov 24 18:44 UTC] No.42149651[source]▶
I've never worked at a company with a public repo. I never understood this. I have a life outside of work
replies(1): >>42149692 #
alkonaut ◴[15 Nov 24 18:49 UTC] No.42149692{3}[source]▶
Neither did I. But I'd rather just "smuggle" out some past work and "rewrite it" to make it inconspicuous, if I didn't have my own personal work to show. The company I work for isn't well known so saying "I worked there in a senior role for 10 years" isn't going to get me the next job. If I didn't have anything to show for that I either made for fun or could display from a past job, I'd not apply for another until I had tbh.

People say "No I don't have any past hobby work, never contributed to OSS, and all my professional work is verboten to show" that's not unusual, but it's also not an encouraging sign to me when interviewing.

replies(2): >>42149804 #>>42149966 #
John_Cena ◴[15 Nov 24 19:21 UTC] No.42149966{4}[source]▶
The elitism is rampant. As an embedded sector guy everyone thinks every other RTOS isn't a real RTOS and the knowledge and wisdom don't translate.

Every time I find some open source I would contribute to, what I wanted to implement is already there or is already in the works. I'm not going to change shit just to change it. I'll buy them a coffee tip and leave.

replies(1): >>42150814 #
1. alkonaut ◴[15 Nov 24 20:46 UTC] No.42150814{5}[source]▶
If I'm interviewing for people to work in some specific tech stack or business, it's just as good to see completely different things they can show. Could be a php site for their book club or whatever. But the key is to have some code to discuss that is their code. Because I want to see them describe and reason about code they know, and it works 10x better if it's code they know, rather than some code I present and say "here, let's reason about this code".
replies(1): >>42151272 #
2. skydhash ◴[15 Nov 24 21:24 UTC] No.42151272[source]▶
Why not discuss a problem you have? You're obviously hiring for someone to solve your problem. Looking to check if they can code (in a specific language) seems like the XY problem.
replies(1): >>42151585 #
3. alkonaut ◴[15 Nov 24 21:52 UTC] No.42151585[source]▶
Because they aren't familiar with or enthusiastic about the code I give them, they could be about code they have written. It's the classic "describe one time you did something poorly/well"-question, but with code. I want to see them critique some code, or explain what's so great, or why it ended up the way it is.

Reasoning about a problem i have (even showing some code) is also a good part of an interview. But it's my side of the field. I just found it's much better to move the interview to the interviewee's side of the turf, because they are more comfortable there.

replies(1): >>42153357 #
4. John_Cena ◴[16 Nov 24 01:31 UTC] No.42153357{3}[source]▶
I would like to just be asked. I can't post my code on github but I can talk about my projects at length.
replies(1): >>42155809 #
5. ozim ◴[16 Nov 24 11:06 UTC] No.42155809{4}[source]▶
For all this thread solution is simple. Small take home assignment where you write the code to discuss during the interview.

I know people are vocal about not wanting to do take homes. But if take home is reasonable and used as a talking piece it checks all the boxes for good tool.

I think in reality I had single person that outright refused and of course bunch of people who didn’t bother to deliver - great candidates delivered it the same day, busy great candidates delivered it over the weekend.