Earlier quoted context omitted.
If you can't code under pressure, you aren't a very competent programmer. Real world projects come with high pressure scenarios for software engineers. Code monkeys may be able to get away with low pressure, minimally impactful projects.
Upvoting you to help prevent your comment from reaching oblivion - I don't agree with you, but I think what you said is a common belief. The thing is, it's a vastly different kind of pressure. When I am coding as part of a job - by myself or with others - there is no inner monologue in the corner of my brain doing something like this: "Could do that or... no damn, that's O(n^2), damn I'm taking too long that one look…
A Method I’ve Used to Eliminate Bad Tech Hires
211–220 of 517 posts
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#212Re: A Method I’ve Used to Eliminate Bad Tech Hires
#213Earlier quoted context omitted.
This works, but make sure they spend the 2 hours in your office and not 12 hours at home solving a 2 hour problem.. The other problem is that when you pay them you generate all sorts of nightmaris legal liabilities.
> This works, but make sure they spend the 2 hours in your office and not 12 hours at home solving a 2 hour problem.. This goes against the core message of the article. The candidate is supposed to think about a problem on their own, and propose a well-reflected solution on Monday. That's pretty much the opposite of "sit down in this noisy corner in an unknown environment and give us something in two hours". > The ot…
It might not be an issue for your company, but your candidate might have a non-compete (or other clause) preventing them from accepting compensation or even performing work for another company at all.
Things get trickier as soon as money is involved.
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#214Earlier quoted context omitted.
> This works, but make sure they spend the 2 hours in your office and not 12 hours at home solving a 2 hour problem.. This goes against the core message of the article. The candidate is supposed to think about a problem on their own, and propose a well-reflected solution on Monday. That's pretty much the opposite of "sit down in this noisy corner in an unknown environment and give us something in two hours". > The ot…
> If hiring a freelancer to do a little thing tends to generate all sorts of nightmarish legal liabilities, your company is either a government contractor or it has even bigger structural problems than hiring. It might not be an issue for your company, but your candidate might have a non-compete (or other clause) preventing them from accepting compensation or even performing work for another company at all. Things ge…
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#215This. 100% this. As many others are saying, I find that this is the most comfortable way for me as an interviewee to demonstrate that I do in fact know what I'm talking about. Put me in front of a room full of people and a whiteboard and throw something at me, and I'll freeze. Freezing in that situation and being a bad engineer are wholly separate things. Anecdotally, when I get one of these problems, I spent 20 minu…
This works, but make sure they spend the 2 hours in your office and not 12 hours at home solving a 2 hour problem.. The other problem is that when you pay them you generate all sorts of nightmaris legal liabilities.
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#216DuckDuckGo follows this process. They in fact do a paid 3 month assignment. May be that's taking it to the extreme and perhaps works very well for them. If I were looking for a job and this process was followed, I'd definitely be game. I will most likely be following a similar procedure while hiring as well. Just come to the office hang out with us for a day - we'll fly you in, put you in a nice hotel + pay you a per…
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#217Earlier quoted context omitted.
This isn't a viable approach for much of the hiring pool, as a majority of working engineers have contracts which explicitly forbid work for contract for other employers. As such, if you hire any of those, you're hiring somebody with a proven willingness to ignore their contract, which is a strong anti-pattern.
Or a $200 donation to their fave charity
I would be much more willing to do the project if I knew the employer would lose $200. Among other things, this shows that I'm valued.
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#218Earlier quoted context omitted.
As a hiring manager and candidate dealing with external recruiters, that's not what I saw happen.
How did you get people you didn't hire to share with you their actual salary preferences, and companies that didn't hire you their actual salary ranges? Sounds like that would be super useful info
Re: A Method I’ve Used to Eliminate Bad Tech Hires
#219DuckDuckGo follows this process. They in fact do a paid 3 month assignment. May be that's taking it to the extreme and perhaps works very well for them. If I were looking for a job and this process was followed, I'd definitely be game. I will most likely be following a similar procedure while hiring as well. Just come to the office hang out with us for a day - we'll fly you in, put you in a nice hotel + pay you a per…