I'm going to reference coding tests specifically, because I'm not against them but I'm against them implemented poorly:

- If I have an extensive github, and my github is on my resume, and you don't have the time to look at it, I don't have time for your coding test.

- If your coding test asks thinly veiled lateral thinking questions, I will not be accepting a job with your company.

- If you spend more than 60 seconds of the interview asking me what I think of your coding test, I will not be accepting a job with your company.

- If I'm interviewing for a position where I'm going to be mostly developing CRUD apps, don't ask me to implement a bubblesort. Interview for the job you're actually hiring for.

- Ideally, let someone else design your coding test. There's plenty of companies that do these now, and they'll be better at it than you are.