tl;dr Credentials carry signal, but recruiters at companies have gone overboard, giving that weight above all else. We push against that.
Relying solely on those signals though acts to the detriment of skilled people whose best work hasn't been done at prestigious, name brand companies.
Our approach to removing credentials from our screening process is to prevent ourselves being biased by them and forcing ourselves to build a process that can find strong engineers who don't look good on paper. This is a win for the companies we work with as it expands the pool of talent they can hire from.
If I need someone to build me a compiler, there's no point sending me any number of job applications who did brilliantly on a coding test, if they have never built a compiler before.
(Of course sometimes it's great to build someone up from scratch, but you can't do that for an entire team all the time).
Ah, all makes sense then.
Ok, then shoot me an email, and we'll build the compiler. I'd be happy to find a position that actually involves compiler work at all.
Triplebyte has been really helpful for me there, and got me interviews with companies that care more about problem solving ability and are happy to hire someone like me who will learn on the job.
Someone who designed the IR for V8 would no doubt have no trouble directly getting interviews with whatever companies they want, and people look you who screen applicants based on experience shouldn't have much trouble finding such applicants. General problem-solving / coding ability on the other hand is not quantifiable on an ordinary resume / linkedin, and Triplebyte's system provides a good screen (within the limitations of a few hours of testing) to quantify that.
It would be great to allow programmers to show their portfolios, but that would likely enable interviewers to google them, giving away their backgrounds.
I have a few interesting projects in my portfolio that I am proud of, a reasonably high CS GRE score (a test which is unfortunately not administered any more), and a moderately good topcoder history. However, after being told by an HR person that they would not hire me because of the college I went to (a for-profit college) I started to view the relation between hiring and credentials as illegitimate. So for that reason I hope TripleByte catches on.
Plus, people with a good body of work need less help getting interviews. TripleByte has less value add in that case.
I don't get it. If someone's done has an incredible body of work behind them, why do you want to hide that from yourself?
Isn't it a great way to pick the best people out of the pool of applicants? 'Ah this person designed the new IR in Google's V8 - we should definitely talk to them'.
When I speak to potential hires the first thing I ask is 'tell me about the projects you've worked on - what have you built in the past'. Am I doing it wrong? Someone could be great at general programming and pass a coding test, but if they have no experience in my field what are they going to do for me?