News for hackers. Stuff that matters.
Re:Always Be Coding – How to Land an Engineering Job by objclxt on Wednesday May 22, 2013 @06:01AM (#5749793)
> I want a "1-hour guarantee" that I'll receive your considered offer after one hour of interviewing

...I wouldn't have hired many of my fellow engineers after an hour. I would at least want two interviews, one with me (the line manager), and one with my team.

To flip it the other way round, I don't think I could get a good enough feel for an employer from a single hour. I'm not sure this works for everyone.

I would, however, hire a consultant after an hour's interview. The difference is, at least in the country I live in, is that I can fire the consultant with almost no notice, whereas a FTE is more of an investment.

Re:Always Be Coding – How to Land an Engineering Job by WalterBright on Wednesday May 22, 2013 @06:05PM (#5754105)
I don't make major financial decisions in an hour, either, and hiring an engineer is a 6 figure commitment.
Re:Always Be Coding – How to Land an Engineering Job by kanzure on Wednesday May 22, 2013 @08:41PM (#5754693)
You don't have to decide during that interview. You can take your time. Look at the candidates' source code on github, bitbucket, look at their mobile apps, disassemble them, take a look at how well they write software, etc.
Re:Always Be Coding – How to Land an Engineering Job by prodigal_erik on Thursday May 23, 2013 @12:29AM (#5755356)
How could you verify the code is actually theirs in just one hour, and not something they've been coached on? The stakes are so high that we already have an awful lot of blatantly unqualified people trying to bluff their way through in-depth interviews, and making that easier is a huge step backwards.
Re:Always Be Coding – How to Land an Engineering Job by freework on Thursday May 23, 2013 @02:23AM (#5755596)
Its usually pretty damn obvious Ask them to explain what the code does and why they wrote it. If they backpedal and aren't able to say anything then you can assume they didn't write it.
Re:Always Be Coding – How to Land an Engineering Job by kanzure on Thursday May 23, 2013 @02:40AM (#5755628)
> How could you verify the code is actually theirs in just one hour

You don't have to review the code inside of one hour. You can take as long as you want on that. The point was that when talking with them either on the phone, in person, whatever, you take only an hour. Code review can take as long as you please. I highly encourage you to look at source code before making a hiring decision.