> .... if they're a good fit for your team, have good work ethic and can get the job done.

I'd modify that last to "and can get the job done well". Most of my co-workers have been fantastic, but there have been one or two who absolutely got the job done... in ways that eventually cost so much dev time (on maintenance / refactoring) that it would have been better to have someone else build the thing in the first place.

(Which is also presumably easier to discover from sample work than from a whiteboard interview. :)