[virtuous_signal]

>And that's a shame because the live coding exercise is both a better predictor of hands-on job success and it's a better recruiting tactic

I'm very interested in this claim. Every interviewing-is-broken thread, someone mentions that pairing, or take-home exercises, or work samples, or their favorite method, are better predictors than algorithm problems. On the one hand I doubt any but the biggest companies could conduct studies on this; on the other hand individuals at smaller companies might honestly remember only those times their hires filtered through this method were successful, due to confirmation bias. So it seems like an inherently difficult thing to study.

Whereas, algorithm questions lend themselves easily to a "rubric" and seeing, 1 or 2 years later, if higher "grades" corresponded to better job performance.

[manquer]

There are studies out there [1] from assessment providers

The problem is any one spending time on this question also has a vested interest in the answer.

FWIW my experience in hiring for my org and in the talent acquisition tech also reflects this . (Not related to the company in the link)

The reason usually this method is not as popular while the efficacy is understood is because it very hard to scale and do inconsistent evaluations and also takes a lot more time per candidate

[1] https://www.qualified.io/blog/posts/truly-predictive-softwar...

[bradleyjg]

Even for the biggest companies the analysis is only going to be as good as the internal performance measuring system and how can a company gain confidence that is working?

There was a long discussion in the GCP thread yesterday about what google has been hiring and promoting for over the last ten years and what culture that produced. Any look-back at hiring methodology vs success at google is going to embed that implicit strategy. Among other things that means another company should very much not extrapolate from Google’s experience—-even if it is based on solid data analysis—-unless they are trying to replicate that culture.

[abledon]

can you link to that thread? Does it dig into how a focus on rote memorization of leetcode, has made a subtle influence in how the interface/systems are designed?

[bradleyjg]

https://news.ycombinator.com/item?id=24167260

It’s more about building new things vs maintaining / improving existing things.