[Fire-Dragon-DoL]

I still prefer take home over everything else for interviews.

I do have one serious question: how to decide what good code is for an interview? It's already highly opinionated, but I can write code that's all dependency injection to the extreme and it would be considered overengineered. I could write a single file project with no DI and it would be ok (one off, 2 hours max), but it would not simulate a real situation. These two things are both valid approaches but they pull the code in opposite directions.

In a real scenario, we have a fixed deadline so it is possible to determine how many design points are available and work on those.