this post was submitted on 26 Jun 2023
41 points (88.7% liked)

Experienced Devs

3978 readers
1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

founded 1 year ago
MODERATORS
snowe@programming.dev
jmk1ng@programming.dev
drewsiferr@programming.dev
41
How to make a coding challenge to hire a new engineer? (discuss.tchncs.de)
submitted 1 year ago* (last edited 1 year ago) by hi65435@discuss.tchncs.de to c/experienced_devs@programming.dev
35 comments fedilink hide all child comments
 

We're a very small team with little experience in hiring but got approval for a new engineer. Basically HR will look for people through the usual channels and I think we have a reasonably good job description. Unfortunately the coding challenge (a 30h+ take home) is atrociously difficult and doesn't really reflect what we do. On the other hand I think the false positive rate would be low. FWIW it's a Linux application and it might be difficult to only count on experience from the CV.

Any ideas how to build a good challenge from scratch and what time constraints are reasonable?

you are viewing a single comment's thread
view the rest of the comments
[–] Next_Position_Please@lemmy.world 11 points 1 year ago

There are a ton of good challenges on leetcode. I'd use a [virtual] whiteboard and have the candidate ask questions. When I'm hiring, I want engineers who can ask clarifying questions. I don't want someone who takes an incomplete set of requirements and goes off and builds what they think is the solution. I prefer they use pseudo code and not worry about syntax. Their IDE of choice would correct the minutia. I once had a candidate ask me if I thought design pattern X would be a good fit for the solution. Excellent question. That shows me they are thinking critically about the problem and open to peer input.

If you go with the programming puzzle type challenge, have a few in your repertoire. I've seen candidates totally blank on puzzle A, but rock puzzle B and vice-versa.

Things that have turned me off in interviews:

  • ask me to write code in a specific language, then nit pick spacing, exact syntax, etc. They can fuck right off. I'm not working for your micromanaging ass.
  • invite me to a 1 hour interview with HR, 1 hour interview with my potential boss, followed by a two hour technical interview. After about 2 hours, I'm done, and need a break. A 30h take home would be a hard pass.

Good luck on the hiring process!