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?

  • Abby@vlemmy.net
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I loved our test at my last company.

    Do an API exposing a fizzbuzz. Make it “prodable”.

    The definition of production ready is completely for the candidates to determine .

    The subject is simple, doable in a few hours. What we were looking at was how code was organised, tests, usage of libs, …