>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.
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.