3 ms·

> because you are "too good" to do C2H hear me out No I dont want to quit my current role until I have a secure job. I'm not going to c2h to be told six weeks

> because you are "too good" to do C2H hear me out No I dont want to quit my current role until I have a secure job. I'm not going to c2h to be told six weeks later I'm on the street.

SkyPuncher 6y ago
Yea, this guy loves C2H because it makes him a lot of money. It "solves" a problem for employers - which is all he really cares about. Good employers don't use C2H because they recognize talented people have plenty of competing offers for direct-hire. If I'm quitting my current job to come work for you, I'm not taking on the financial risk for a job that YOU decided needs to be filled, set all of the evaluation and success criteria, and know what your company's culture is actually like.
- rsweeney21 6y ago
  We make roughly the same whether you go C2H or direct salaried. C2H interviews generally take much less time, so we do have an incentive, but so do the companies and candidates. You don't have to take a C2H job, but for some people that don't have stellar resumes or are bad at interviews, C2H will give them access to more opportunities.
ragle 6y ago
Right. For a very good (but not exceptional) developer, I wonder if ending up "out on the street" would be a reasonable expectation if something like this became truly widespread. If companies like Google were no longer able to filter false positives __at Google scale__ using their current hiring practice, I wonder how long it would take to decide that the next best thing is to contract some tunable number of N contractors for K positions where N >> K and only keep the best M (K <= M << N) of them. (I expect a company like Google to occasionally keep more than K because they can't afford to throw away rockstars if they get a great cohort). So, even if you're pretty good - if you aren't better than the bottom x% of your cohort (or some other aggregate measure) - you're out. Stack ranking for C2H, basically.

> because you are "too good" to do C2H hear me out No I dont want to quit my current role until I have a secure job. I'm not going to c2h to be told six weeks later I'm on the street.

SkyPuncher 6y ago

Yea, this guy loves C2H because it makes him a lot of money. It "solves" a problem for employers - which is all he really cares about. Good employers don't use C2H because they recognize talented people have plenty of competing offers for direct-hire. If I'm quitting my current job to come work for you, I'm not taking on the financial risk for a job that YOU decided needs to be filled, set all of the evaluation and success criteria, and know what your company's culture is actually like.

rsweeney21 6y ago
We make roughly the same whether you go C2H or direct salaried. C2H interviews generally take much less time, so we do have an incentive, but so do the companies and candidates. You don't have to take a C2H job, but for some people that don't have stellar resumes or are bad at interviews, C2H will give them access to more opportunities.

ragle 6y ago

Right. For a very good (but not exceptional) developer, I wonder if ending up "out on the street" would be a reasonable expectation if something like this became truly widespread. If companies like Google were no longer able to filter false positives __at Google scale__ using their current hiring practice, I wonder how long it would take to decide that the next best thing is to contract some tunable number of N contractors for K positions where N >> K and only keep the best M (K <= M << N) of them. (I expect a company like Google to occasionally keep more than K because they can't afford to throw away rockstars if they get a great cohort). So, even if you're pretty good - if you aren't better than the bottom x% of your cohort (or some other aggregate measure) - you're out. Stack ranking for C2H, basically.