News for hackers. Stuff that matters.
Re:What If You Could "Date" Companies? by colmvp on Friday June 21, 2013 @03:13PM (#5920292)
Exactly. It's not uncommon for design firms (interactive and motion) to conduct a probation period with potential employees by paying them a freelance rate for a few months prior to writing an offer.

That's also why I balk at companies that give take home tests to screen applicants.

Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @03:17PM (#5920316)
FWIW: the practice of having prospective employees do a probation period as a contractor is (take your pick) unreasonable and/or counterproductive.
Re:What If You Could "Date" Companies? by gruseom on Friday June 21, 2013 @03:29PM (#5920402)
It does seem like the mechanisms people have come up with for this so far are counterproductive. But the underlying problem seems to me a real one, and a hard one: how can you tell whether someone will be good to work with? The only way to know is to actually work with them. So (the argument goes) rather than relying on bogus predictors, let's just test the hypothesis "this person will be a good addition to our team" directly.

Since you think about hiring a lot, I'm curious: do you think the above is accurate? If no, how would you phrase it differently? If yes, how would you recommend testing that hypothesis instead?

Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @03:57PM (#5920602)
I think it's very accurate, and I think the idea of temp- to- perm hiring is seductive for exactly that reason.

In addition to the argument that the economics of temp- to- perm don't work out in this market for tech talent, there are also fundamental problems with the approach.

Most importantly: lots of people can perform well for short periods of time, especially if they don't have to deal with interpersonal conflicts (which take time to develop) or technical design disagreements (which only happen at inflection points in product/service design; ie, it might take 8 months to discover whether someone can "disagree and commit" to work on a team where they disapprove of some technical decision). Also, lots of people can work well on a project for a couple weeks before they get bored, and some of those people lack the ability to kickstart their engagement back up again once they feel "burned out" by a problem domain.

I think those are some of the most likely failure modes of new employees, and they also happen to be different from the failure modes that classic interviewing and work-sample testing are likely to suss out; ie, you can cover the non-psychological non-work-ethic concerns about new candidates with a relatively straightforward hiring process, so temp- to- perm might not even buy you much even if you don't assume that the approach is costing you the best candidates.

Re:What If You Could "Date" Companies? by andrewflnr on Friday June 21, 2013 @03:32PM (#5920421)
I'm not sure I see the difference between the freelancer->fulltime and contractor/probation->fulltime progressions. Is is just because in the latter case they weren't already a freelancer/contractor? Is there a big terminological issue I'm missing?
Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @03:46PM (#5920516)
The two issues (unfairness and inefficiency) are somewhat orthogonal. So let me just guess that you're referring to the "inefficiency" side of the problem.

The problem is that companies looking to fill full-time slots are looking to fill full-time slots, not to engage a succession of contractors.

By requiring candidates to perform in a contractor role prior to signing on full-time, companies are effectively disqualifying most candidates that are currently employed. That's because very few people sniffing around for a better job than the one they have now can afford to drop out of the market for months or even weeks delivering work as a contractor. That's not how most people switch jobs; instead, most people search for their new job from the comfort and security of their current job, knowing that if (say) interviews don't work out, they can take their time looking for the next lead, knowing that they can continue to execute on their current job.

This is a problem for employers because virtually everybody you'd want to hire in this market is already employed.

Re:What If You Could "Date" Companies? by mechanical_fish on Friday June 21, 2013 @05:41PM (#5921196)
And those who aren't full-time employed may not bite on the contract-to-perm offer either. Because in my limited experience "here's our contract-to-perm offer" usually translates to: "Please freelance for us at sub-market rates, under our poorly-thought-out non-negotiable boilerplate contract with unclear deliverables."

Typically they offer to take a slightly-low full-time weekly salary+benefits number, divide it by 40, and pay that as an hourly rate. Oh, goody.

No company wants to pay a contractor the going rate for contractors, and then face the unenviable task of talking that contractor's rate back down again when making them a full-time offer. Nor do they want the bother of haggling over the details of a contract deal that will almost always prove, one way or the other, to have been a wasted opportunity. (If the worker proves to be competent, the contract will be replaced by a full-time offer as quickly as possible. If the worker is incompetent, the contract will be terminated at the earliest practical date. In no case does anyone care much about the contract. It is a consolation prize for everyone involved.)

My personal philosophy is to treat contracting and employment like oil and water. Both can be tasty. But they are different things and one does not merge seamlessly into the other.

Re:What If You Could "Date" Companies? by andrewflnr on Friday June 21, 2013 @08:25PM (#5921956)
So the difference is whether you started off in a full-time job, and come into the deal hoping for one? If you're a freelancer, the chance of a fulltime position is one you can take or leave at your leisure. But if you start off as a fulltimer somewhere else and come into some contract-to-hire scenario, that's what you don't like. Amirite?

Anyway, I learned. Thanks.

Re:What If You Could "Date" Companies? by thestoic on Friday June 21, 2013 @03:51PM (#5920553)
Contrary to the other comment, moonlighting is just as easy for someone FT employed to try as someone who is no employed. The FT employed can make 20-30hrs available a week to try out a company on a set amount of work and get a feel for it. The alternative is to go through a set interviews (that if you read the google article, are useless) and then change your job (effectively putting a bullet on your last job) only to find out that you hate your new job and now you are stuck there. Try outs are safer and available for all.
Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @04:00PM (#5920621)
So now we're talking about constricting the flow of candidates down to those who are willing to accept a second job for weeks to mitigate the concerns of future employers.

The problem here is obvious: the best candidates don't ever have to put up with stuff like this. They're actively courted by prospective employers.

Sure, not every candidate can be "one of the best candidates". But why would a rational employer select a screening process that overtly rules those candidates out?

Re:What If You Could "Date" Companies? by ghempton on Friday June 21, 2013 @03:34PM (#5920435)
Calling it a "probation" period is creating a loaded discussion. It can be in the developer's interest to find a job that really interests her rather than give a full-time commitment based off of an interview.
Re:What If You Could "Date" Companies? by Zimahl on Friday June 21, 2013 @04:28PM (#5920784)
Ugh, the take-home test/coding assignment. I've done two of these and I will never do another. Bottom line, if a company can't be bothered to respect that the time the interview process eats up for both parties, they probably aren't going to be worth spending their time with long-term.
Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @04:39PM (#5920843)
Interesting. Why do you feel this way? We rely on "take-home" (they're set up in advance of the f2f interview) work-sample tests pretty extensively, and I feel like they're probably more humane; for instance, you can look things up on the Internet, do them in a comfortable setting, &c.
Re:What If You Could "Date" Companies? by Zimahl on Friday June 21, 2013 @05:03PM (#5920981)
I'll leave out the details of the two I've done since it's a sore spot on my psyche but I'll talk about them in general.

Maybe yours is different, but I think the first problem is they typically have a lack of clearly defined goals. I know that probably is the idea behind these - to see what someone comes up with - but it can be very intimidating. Especially given the fact that the interviewee is already nervous enough and now they are given something ambiguous. I think that's more nerve-wracking than the interview itself.

Second, I think that code-style tends to get graded on these more than the content. Unless it's completed in some really novel way (which isn't always a positive) there's nothing to do but nit-pick how the code looks.

Third, its disrespectful of the interviewees time, especially relatively large coding assignments. If a candidate has a job, is it fair to expect them to go home and spend a couple hours working on something that is essentially worthless?

Finally, typically the candidate gets no feedback. I had one that was a 'pass' and I never found out why. You are essentially grading me on an assignment and then don't have the decency to tell me what was wrong? This is related to the previous item as a time-waster.

So, those are my reasons. Just my two cents.

Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @05:09PM (#5921019)
I don't want to let myself off the hook too easily here, because we don't hire for typical developer roles; our work-sample tests are very well defined (they're exercises in finding and exploiting vulnerabilities) but I'm generally interested in the technique overall. So let's stipulate I'm a hiring for a standard dev role. I think you make some great points.

(1) Yes, ambiguity is death. It's bad for the reason you say it is (it psyches you out, and discovering how people perform when they're at their most psyched-out is a pointless exercise). But it's also bad because open-ended tests are hard to grade and compare. Work-sample tests need to be standardized and they need to be defined rigorously enough that you can draw comparisons between candidates, and then draw comparisons between the performance of hires and the tests.

(2) Yes, grading superficial issues is also bad, for the same reason: when you give someone "points for style" (or demerits), you lose the ability to make apples-apples comparisons with candidates over time.

(3) I flat out disagree that take-home work is disrespectful of candidates. Most interview processes demand that employees submit to several (3+) hour+ long phone screens, then show up at an office for 1-2 days of interviewing. Allowing candidates to do the most important technical portion of the interview on their own time, on their own schedule, in their own location is simply better for the candidate than forcing them into a room with a whiteboard.

(4) Yes, not giving feedback to candidates is one of the great sins of tech hiring. Some of this is folkloric; for instance, there's a belief that providing feedback to candidates you opt not to hire sets you up for frivolous complaints down the road. But there are ways around that problem.

Re:What If You Could "Date" Companies? by Zimahl on Friday June 21, 2013 @05:44PM (#5921208)
I see your arguments for #1, #2, and #4. Fair enough responses.

As for #3, if you aren't a fairly exclusive 'brand' (like Google, Amazon, maybe Facebook) and you are known for having a long interview process, I think a fair number of applicants won't even bother. I've been asked by Amazon to interview a few times and their process just seems like a big pain for not much gain. Unless I was right out of college I just wouldn't find it worth the effort.

So if a recruiter tells me an interview process is extensive and way too involved for the market, I'll just pass. When jobs are plentiful a candidate can afford to be picky.

EDIT: sentence clarity.

Re:What If You Could "Date" Companies? by ardit33 on Friday June 21, 2013 @05:03PM (#5920980)
Good developers have always a project that they are working on. Be either an open source project, app, game, little library, whatever. Working on a take home assignment is just a waste of time, where that person could be working on something useful. Or they could be spending that time with their kids, friends, or just relaxing.

The only time it is ok to ask for a take home assignment is when the person is at most a couple of years out of school, and they haven't proven themselves yet.

I personally refuse doing to do take home assignment as I have enough projects in my belt that I can show. It is usually a sign that the other party is not mature enough, and they don't know what they are looking for, and once you join that company they will treat like a junior engineer, when you might be past that.

Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @05:14PM (#5921051)
But you can say the same thing about a long in-person interview, which has the added disadvantage of demanding your time during the working day.
Re:What If You Could "Date" Companies? by ciclista on Friday June 21, 2013 @04:59PM (#5920962)
How long do you usually expect these tests to take? Do you pay for the interviewees time?
Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @05:01PM (#5920968)
No, we don't. And, a couple hours. The time commitment we demand from candidates is calibrated to be about the same as you'd demand from a (rigorous) day of on-site interviews. Our on-sites are a half-day thing, not a full-day.
Re:What If You Could "Date" Companies? by nicolethenerd on Friday June 21, 2013 @05:33PM (#5921150)
I used to agree with you, but I've seen the other side of this. When I was applying for FT jobs out of school, one of the companies I interviewed with sent me a small coding assignment, which I completed - I got the job. I've been here for over 2 years, and turning in that coding assignment is probably one of the best things I've ever done for my career. Was it really necessary for them to tell that I could code? I don't know, but showing up at work and knowing that everyone I worked with had been subjected to the same test and rigorous technical interview was nice - I knew I was working with smart people. In contrast, the other two companies I got offers from barely had any interview process at all, which was worrying to me - if they'd hire me without so much as a fizzbuzz test, who knew what kind of people they had working for them?
Re:What If You Could "Date" Companies? by Zimahl on Friday June 21, 2013 @06:23PM (#5921386)
Are you going to be so responsive to silly fizzbuzz tests 10 years down the line with multiple successful (and unsuccessful) projects under your belt? If a senior developer gets asked to write a sorting algorithm don't be surprised if they just walk out and enjoy the rest of their day.
Re:What If You Could "Date" Companies? by tptacek on Friday June 21, 2013 @07:23PM (#5921683)
The point of fizzbuzz is that it's so simple that behaving as if it was a pain is an indicator.
Re:What If You Could "Date" Companies? by Zimahl on Saturday June 22, 2013 @07:52PM (#5925634)
You're right, it's an indicator that the company doesn't know how to talk to developers with experience.
Re:What If You Could "Date" Companies? by nawitus on Friday June 21, 2013 @05:43PM (#5921206)
Coding assignment sand fizzbuzz tests are not necessary if the applicants can demonstare their coding ability otherwise, by e.g. showing a portfolio.