> 2. Micro-skills take-home problem. The candidate completes a coding problem and reviews it with the interviewer. Talking through the problem with the candidat

> 2. Micro-skills take-home problem. The candidate completes a coding problem and reviews it with the interviewer. Talking through the problem with the candidate helps us assess ability as well as the candidate’s thought process, and how their priorities and values in writing software line up with ours. This is generally a lousy experience. I've been places that want me to build a 'simple' (single entity) fullstack CRUD app (angular w/ASP.NET core backend.) So what is it that they want prioritized? UI skills? Backend dev skills? I can do both, but I'm not going to spend a week making it enterprise-production-ready. The hiring engineers all have things they are looking for and these things are never well defined for you up-front, so no matter what you do (unless you spend way too much time on it,) someone may use it to disqualify you (without you ever knowing it was important.)