81–90 of 230 posts
Why not just pair with the interviewee for half a day or a day? You will learn how they think and work and if you like them. It's a riddle to me. I've never heard from anyone actually trying it and not being happy with the insight won.
Earlier quoted context omitted.
That "opportunity" is not worth having no company-provided health insurance, nor is it worth paying both halves of the FICA tax, except for the desperate.
Because it's impossible to pay someone at a higher hourly rate than they would be paid as a full-time employee?
Earlier quoted context omitted.
Why would the competent developers migrate to the company that is more hostile, in a purely objective sense, than the alternatives?
It's like they're almost trying to winnow the pool down to developers whose programming ability outperforms their career experience and business sense. They certainly exist: I had the business sense of wet paint as recently as two years ago (which might explain why I willingly worked as a salaryman despite having perfect knowledge of the hours and salary).
I spent many years hiring and working for companies that did it the way most people do it. The results speak for themselves: most companies suck to work for and most of them suck because of a few (or not so few) bozos and the environment they create.
My last interview process was intense: 1. A write-a-document test. I was given a fairly simple (contrived) scenario over the phone and was asked to write specs and a deployment plan with a deadline of an hour. 2. A programming test. Again, a description given over the phone and someone available to answer questions if I had them. After delivery, there was a followup programming task to extend it from a client app to…
This doesn't follow at all! Consider, as is surely the case, that only a small fraction of the applicants would have turned out to be average to excellent. The interview process can filter out the vast majority of the sub-average applicants and still leave you with a significant fraction of sub-average employees.
Earlier quoted context omitted.
I am getting down votes for this?! WTF? Look at the domain name and understand the original post, before downvoting! Think and then act!
Yeah, keep downvoting me and don't even have the curtesy to write a comment as to why!
Earlier quoted context omitted.
Because it's impossible to pay someone at a higher hourly rate than they would be paid as a full-time employee?
It's not the easiest thing in the world to explain, no, which is why I bet most people who do the temp-to-perm thing don't bother, and just pay the contractor according to their yearly salary. After all, if they don't know enough not to take the term-to-perm offer, why complicate things? ;)
I'm happy to pay higher hourly during the contract to compensate for the lack of benefits.
I'm happy to pay a (naive) employee more than they asked for because I know what the position is worth and have no interest in tricking them.
This isn't generosity, it's just good long-term business IMHO.
1) Software development is a TEAM work, so asking one questions like "how did you design this or that" is just pointless. We did design that on that specific period of time...Our motivation was ... 2) Good Developers Copy, Great Developers Steal (altered from P.Picasso), so we all use Google, HN, GitHub, wikipedia and alike to innovate our solution, so if you ask me B-Tree algos, I'm sorry, but I've to look at wikipedia... 3) Hiring process is just a scumbag for both parties, you impose big, the other party imposes big. So what? You're not Google, and he's not Kevin Mitnick... 4) I think, companies should try to get the personality, not the KLOCs of applicants. If you gonna ask programming puzzles, please be authentic and ask something related to you. Not just copy a Googlr interview question because you liked it.