I agree using this approach on someone just out of school wouldn't work very well, but I don't think that's the bulk of the problem space. If someone has 3 yea

I agree using this approach on someone just out of school wouldn't work very well, but I don't think that's the bulk of the problem space. If someone has 3 years experience, there should be plenty of results to allow an in-depth look at what they've been working on. It wouldn't matter if someone 10 years senior had "more stuff", because it's not about quantity. I think it's important to take in the context of where that person is at in their career and what's realistic. >>There are false negatives from rejecting great engineers who...can't communicate their experience well Well, it's true this is a problem isn't it? Whatever you call it, it's part of a lot of us, part of who we are, and does sometimes result in unfair judgement. The problem is, I'm not sure TripleByte's process gets around this either. Part of their process is a dynamic interview that surely requires some communication skills. Pass that and no doubt even more communication skills will be needed at the employer interviews.