1. 8
  1.  

  2. 4

    Overly simplified title is overly simplified. The article says refuse tests issued by recruiters, otherwise they’re fine and have a purpose.

    1. 4

      Well, actually no, it says don’t do a home tech test until you’ve talked to an employer first, for example if you’ve had a phone interview.

      But what is perhaps implied is that a phone interview tends to negate the need for a technical test in the first place (check interviewee basic competence without employer time commitment) so they’re probably a waste of time for everyone in general.

      IMHO better to have a phone interview to check basic competence, and then bring candidates in for pair programming exercise and face-to-face interview follow-up.

      1. [Comment removed by author]

        1. 2

          That can be a lot of pressure for an applicant. Introverts will probably do worse than they would on the job.

          It’s also expensive and turns away people who can’t take a couple days off their current job without arousing suspicion.

        2. 4

          bring candidates in for pair programming exercise

          Unless the job (a) specifically requires a significant amount of pair programming and (b) expects candidates to already be skilled at pair programming before starting, you’re probably significantly increasing the rate of false negatives. Pair programming is a different skill than solo programming, and comparatively few developers have much experience with it.