| > Perhaps creating a single view of a website/app for a frontend role. Or creating a few API endpoints for a backend role Those things are relatively trivial, and easy to coach as well. If someone never did it before, you can easily show them how on the job. You also wouldn't have time to have them work that in an interview, so you'd need to do a take home, and then you can no longer validate they truly did it themselves, how much time they spent to do it, how much googling they had to do, how they approach the problem or delt with issues, etc. I also find they tend to be framework/language specific, some companies even have internal frameworks and all that so they'd have to relearn part of it anyways. > Or whiteboarding through a technical architecture This is normally included as part of a "leetcode" like interview. It tends to be a half day, where you're asked one or two system design questions, which are of the format you describe, and are asked one or two data structure and algorithms questions, and one or two small programming questions that checks your ability to write readable and maintainable code that is well structured, well organized and well factored. Sometimes the latter two are combined into one bigger question that tests both code design quality and requires an algorithm or special use of data structures to solve. |