But it needs to be:
- In-depth. Not just a single exam or interview. You need to really know the employee’s strengths and weaknesses
- Detailed. You can’t just give someone pass / fail or a single score. Not only is it mean, but you end up getting misaligned candidates anyways, because some people are really bad at some aspects of software but good at others. In fact maybe the process should ditch scores entirely and just show the recruiters the actual employee interviews, and what he/she has and has not accomplished.
- Changing over time. Not a short period of time. But like, if I take the assessment, 6 months later I can take a smaller assessment and it will update my scores and log my progress.
Triplebyte is not 1 or 2. Idk but I think it’s 3 and you can retake the quiz. But then it’s only telling employees if you’re basically competent for some arbitrary statistic, which doesn’t even tell if you’re basically competent at the company.
I think it would be nice if i could take one thorough interview instead of several less-thorough company-specific interviews, but that’s not Triplebyte.
Companies wouldn't trust a third party to run binding technical assessment for them, and quality devs would probably avoid places that hire without having someone from the destination team show up
I think the opposite would be more beneficial: a light check to validate work claims and some high level foundational question about code just to make sure one has basic proficiency in what he claims he has
Then companies would need lot less hr pre-screening and could focus in technology and culture matching
If you can hire someone skilled, but who other companies might overlook, that's a huge benefit to your team.
Triplebyte is really just the first screen, and the importance each company wants to put on the signal is up to them.