News for hackers. Stuff that matters.
Re:On Secretly Terrible Engineers by morgante on Sunday March 08, 2015 @04:31PM (#9167111)
The problem with the portfolio approach is that many incompetent engineers can easily point to code that they "wrote." Often it was part of a larger team carrying them, but sometimes they wholesale copy it.

A similar problem applies to pure project interviews: the total incompetents are also the ones most likely to get someone else to "help" them with it.

Re:On Secretly Terrible Engineers by analogwzrd on Sunday March 08, 2015 @06:11PM (#9167545)
Yep, there also needs to be a way to detect bat-boy syndrome (where the team goes to the world series, but the guy you interviewed was just there to lug the equipment around).

I've always heard that you learn more in an hour of playing(as in a sport) with someone than you will in ten hours of conversation. I like the idea of being paired with an engineer to solve a problem because it let's someone see how you think, what your process is, and, most importantly, how you learn.

Re:On Secretly Terrible Engineers by learc83 on Sunday March 08, 2015 @05:12PM (#9167287)
>The problem with the portfolio approach is that many incompetent engineers can easily point to code that they "wrote." Often it was part of a larger team carrying them, but sometimes they wholesale copy it.

Have them walk you through it, or ask specific questions about it.

>A similar problem applies to pure project interviews: the total incompetents are also the ones most likely to get someone else to "help" them with it.

The best interview I've ever seen is where they pair you with another engineer and give you an hour or 2 to solve a problem. The other engineer is there to help you and you actually work as a team.

At the end that engineer evaluates you.