|
|
|
|
|
by Harj
3390 days ago
|
|
I'm not sure exactly how your process works, from that description there's three ways we differ: (1) We don't submit resumes to companies. We give them a profile of the candidate which describes their technical skills and their work history but without any mention of specific schools or companies. For a company to move forward with a Triplebyte candidate, they have to trust in our screening process more than credentials. (2) Companies agree to not do any technical phone screens or coding challenges with our candidates. Instead they do an initial pitch call and then move to an onsite if there's candidate interest. This saves engineers a lot of time spent in repetitive phone screens. (3) The metric we optimize for is our onsite success rate i.e. how often does a Triplebyte candidate onsite interview result in an offer. Since our candidates don't go through the regular technical phone screens, any improvement we can make on the industry standard of a 20 - 25% onsite success rate saves the company engineering time spent doing those phone screens. Currently we're averaging 2x that rate across all our companies. |
|
I can see where that's valuable to the companies. What value are you trying to provide to candidates? I already know how to apply to companies, pass the phone screen, and wash out of the interview. If I knew how to pass the interview, I'd still know how to apply and pass the phone screen. What is Triplebyte supposed to help with?