4 ms·
Getting a phone interview by contacting a company is easy if you have the right resume credentials. If not, you need someone to vouch for you to even get in the
by Harj 10y ago
Getting a phone interview by contacting a company is easy if you have the right resume credentials. If not, you need someone to vouch for you to even get in the door. That's what we're doing for engineers who are strong but lack these credentials and the connections to be referred.
We find that engineers who apply to us even if they have those resume credentials are doing so for two reasons:
(1) People only have bandwidth to talk with a few companies. We have enough data across companies to filter out the ones you won't be a technical fit for. This saves the wasted time of failed onsites, which as you say is the bane of existence for programmers.
(2) Finding companies you wouldn't have otherwise heard about or realized were an interesting option for you. We can especially help here with engineers interested in joining smaller companies that haven't had breakout success yet.
Traditional recruiters only help with getting you an introduction to an arbitrary company (usually whichever responded first to an email blast). We strongly believe that a recruiting service which does intelligent matching provides a lot of value for both candidates and companies (we wrote more about that here: http://blog.triplebyte.com/triplebyte-engineer-genome-project http://blog.triplebyte.com/triplebyte-engineer-genome-projec...).
- CiPHPerCoder 10y ago> Getting a phone interview by contacting a company is easy if you have the right resume credentials. That's the problem. Resumes shouldn't matter. The capability to solve programs through an understanding of software-- which is often acquired without going through a resume-building path-- is what matters.
- Harj 10y agoWe agree, that's why our technical interviews are done blind without knowing anything about the credentials of a candidate.
- rtpg 10y agoSerious question though: what steps on good paths are there that you can't put on your resume? You can totally list projects you've worked on, or some other stuff which isn't "MS in Comp Sci at Stanford" I feel kind of the same way about resumes for hiring as you, but they're pretty good entry filters: if you can't be bothered to write 300 words (or, you know, reuse one with a slightly different intro), why should the company bother talking to you? I think this is all part of the "avoiding false positives" mindset that comes with recruiting. Since recruiting people is really expensive!
- CiPHPerCoder 10y agoTeaching yourself computer security by getting root on the servers hosting illicit torrent-sharing websites isn't exactly something you put on a resume, as a particular example.
- exolymph 10y agoWhy not?
- CiPHPerCoder 10y ago"This person is a criminal. Next!"
- exolymph 10y ago:( I'm disappointed in companies who are that pedantic about the law. On the other hand, corporations are definitely all about risk-reduction.