Up here in Canada not all procedures are insured, Pharma, Vision & Dental are the big three that most either pay out of pocket or purchase extended insurance for - though there are generally pretty good provincial programs to help with the costs of those. However, nobody is walking around in Canada concerned that they may get fired and then be bankrupted by a heart attack.
Companies absolutely do still bear a significant per-employee cost to support provincial healthcare and residents do need to pay a pretty light fee into a pool (with options available for financial assistance).
The end result is that companies do end up bearing pretty heavy burdens on a per-employee basis - but employees don't end up with as much of a burden forcing them to remain in undesireable employment positions, though some guaranteed income would really free up employees to have a more equal amount of power in the job market.
Mate when I (in the US) took a month off because I got COVID, my insurance tried to cancel. Fucking insane that we have to deal with this shit.
[0] https://www.fidelity.com/retirement-ira/contribution-limits-... [1] https://www.irs.gov/retirement-plans/ira-deduction-limits
And you kind of have to bomb the contract phase to not be given the offer, unless there are other circumstances at play (budgets, pandemics, etc). Hang with the team at lunch or after work if they do that, make code contributions asap, and be the kind of person any team would want to have.
C2H usually just makes it easier for them to drop you if you're (surprisingly) not a good fit - and after that kind of time and money investment, they definitely don't want to do that.
That's because the employer is covering significant costs on behalf of the employe. A fully-loaded FTE typically costs 30% to 40% more than they're base salary.
Contractors need to make more because they're covering all of those things themselves.
When I was hired I did about 1-2 hours of work for 3 days, after my normal job and was hired before even finishing the "project".
Negotiating your salary upfront is likely going to give you the best deal you can get. Don't kid yourself into thinking that you can "show your value" to improve your negotiating position. Your first few months on the job are usually when you are at your lowest performance, since you are learning the company's processes. That is your trial period.
You are in your best negotiating position when the company needs you more than you need them, and that is absolutely NOT after doing contract work for them for a while.
Once you're at the point of converting, if you get a lowball offer, the contract position is a black mark on your resume that hurts your negotiating position with other firms.
That said, I would be happy to do C2H if the following conditions were met:
* Signing bonus paid in full at point of signing the contract, with no clawback.
* Full health coverage during the contract portion (extra money plus the option to buy from their plans).
* Severance pay at full salary for at least 6 months if you choose not to convert.
* Non-exclusivity during the contract period (I can do other work if I want, and you don't own any IP I produce other than what I produce explicitly for you).
I think this is sufficient to equalize the negotiating disadvantage that I get for taking the contract. I don't think any of your clients would go for it.
In most cases companies have a ball park salary in mind for the position, so when it comes time to convert there is some room for negotiation, but no surprises.
Companies are so desperate for good software engineers that they aren't going to let a good dev go after several months on contract in order to low-ball you and save a few thousand dollars.
I'm almost willing to believe this works for people who absolutely are unable to pass any sort of interview, but in that case aren't they still in trouble? How does a company decide who to bring on for the contract? Surely you can't replace the interview process with this.
That does not conform to my experience as employee or as an employer. Do you have any evidence to support it? If does sound like something a recruiter who wants to take a cut of your first year salary (from the employer) would say.
How does C2H help me jump jobs as a dev who is already employed?
Since I already work 9-5, typically my only free days are my weekends. I might be willing to work for a few weekends if it would lead to a hire, but are those really compatible with what the hiring company wants? My guess is that they want me to take the step of leaving my current job, which comes with loss of health and dental insurance, which is often a big concern.
So you are paying for your health insurance yourself, but you keep the same plan.
There's still the risk of them not bringing you on at the end of the contract or terminating it early if it's not going well. But I think the upside of easier interviews and trying out a team out weighs the downside.
I don’t disagree that it would be nice if every candidate could take the time to try a company out before they join them, but the real world really can make that impractical. Some of the suggestions this thread makes around “buying” ones way out of these problems (such as knowing to have paid for COBRA ahead of time and being able to afford it) represent knowledge and opportunity that is all together distinct from ones ability to do the job.
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.
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.
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.
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.
A short time later, I did another conversion interview, got people who were willing to tell me "look, we know you can code" because they had SEEN me code and design systems they were using every day. They still did some interview questions, but lo and behold I didn't feel like jumping out the window every second.
If you've already worked with the candidate, you already know this so there's no point in having an interview.
I put up a few PRs, then a final assessment was a discussion that was essentially, "Now that you've seen our codebase, what are your thoughts on how we could improve our architecture, etc.?"
I was paid for my time as well (because I was legally able to accept payment at the time). I think that's actually a larger hurdle — companies that disallow contract work that prevent engineers from getting paid for this type of interviewing, although I suppose it's in their best interest.
Besides, from the hiring company perspective, only unemployed people or people who really hate their jobs would end up sending their CVs. The competent people who are currently happy where they are would never try C2H. So they are missing a lot of potential good candidates that way.
Companies whose core business is software development probably do, some other companies have almost entirely outsourced development, even where they have very large ongoing custom development needs.
There was one where I converted to full time, and then we got hit with the dot com crash, so that sucked.
Especially in this environment, it could be weeks or months before the next C2H, especially with so many more engineers being laid off. There could be a ton of people competing for a single job.
Also, negotiated a higher salary when THEY hold the cards because now you need to find a new job? That's insane.
If you're consistently swinging from contract to contract you're a freelancer, and you should be arranging contracts accordingly, not letting headhunters/recruiters control the playbook by dangling full-time employment.
I agree with the grandparent: C2H usually means you're unemployed, or you want out of your current gig badly, or you're aiming slightly higher than you're qualified; if you're qualified for the role and already have a job then they should be willing to take you on from the get-go.
However, it is likely you'll be able to negotiate a higher base salary when you convert than you would have been able to negotiate if you had hired on directly as a salaried employee, because it would cause them extreme pain to try and replace you.
I would certainly move, even internationally, for the right job, but I'm not going to relocate for a shot at a job.
Temp-to-hire is problematic for its own distinctive reasons:
* It's difficult to generate apples-to-apples comparisons of candidates in a temp-to-hire setting because the engineering workload isn't constant; candidates are getting the luck of the draw with whatever the tasks are during their contracting period.
* There's as much subjectivity built into the projects candidates get during their temp-to-hire as there are in whiteboard interviews, so culturally preferred candidates are just as likely to get fast-tracked in a temp-to-hire process as with interviews.
* Interview processes routinely evaluate many candidates for a single opening --- that's expected in basically all hiring, across every industry --- and can't reasonably offer temp roles many candidates simultaneously, so in effect temp-to-hire just pushes the qualification problem to a higher level of the funnel, where the recruiting process decides who to extend temp offers to.
* Temporary contracts draw out the hiring process and potentially make it take far longer to finally fill a role than other processes do; you're required to trade accuracy of evaluation against the time taken to fill a role, bearing in mind that when candidates wash out of their temp contract, you likely have to start all over again with another candidate, making it even more important to pre-screen candidates before offering roles, which just recapitulates the whole problem.
* The tech industry is notoriously bad at evaluating on-the-job performance too; every developer I've talked to has stories of dead weight team members† that were kept on the team interminably because no process existed to evaluate their performance accurately. There's a whole cottage industry of people who have failed up† through role after role, because there's no resume difference between people who phoned in a role† for a year or two and then decided to move on, and people who did well.
* Perhaps most importantly, temp-to-hire is deeply unfair to candidates; a career norm in tech is that people secure their next role while winding up their previous one (in fact, that's a norm in most white collar industries, which is why there's so much written career advice about how to handle counteroffers). Taking a temp-to-hire position requires a candidate to forego income security for a chance at a job; when that job doesn't work out, they're now in a distressed position when looking for their next job.
(I'd add, though it's a nit, that temp-to-hire positions virtually never compensate appropriately; contractor wages are routinely 2x+ what FTE wages are, in large part precisely because of what makes temp-to-hire so attractive: freedom to fire on a moment's notice with no commercial/reputational cost.)
† Shut up, Kurt
I wouldn't take a "temp-to-hire" or a job with a trial period either.
Now before you dismiss the idea because you are "too good" to do C2H hear me out. Everyone knows that actually working with someone on the job is the only way to get an accurate evaluation of an engineer. Everything we currently do in technical interviews (whiteboard coding, pair programming, take home assignments, etc) are just attempts to recreate a working environment. If you are hiring a contractor first, you can do a light-weight interview process and then just bring them on and start working together.
As the dev being brought on you can prove your value before you negotiate your salary. You can also try out the company and manager before committing to an offer.
It's crazy, I know, but I think it would drive dev salaries up if it weren't so hard to change jobs because of the tech interview gauntlet we've created for ourselves.
[*] https://www.facet.net