Also, expectations of coding tests should be upfront. E.g. we're looking for the most optimal solution, not the one that is most convient.
I was declined for a position at a trading shop for a C# backend role because I used linq to do something. I didn't have unlimited time for the tests, so I went with expedient over performant, for which they did not care. Fuck that, set clear expectations for interview "tests".
If you tell me "here, do this, you have 2 hours" I won't even think about the possibility that you want anything that isn't quick to write.
If your priorities aren't aligned with the environment you set up, you are the one that must say so. On a real world project that means once in a while I'll take a project back for small fixes, instead of wasting unending hours thinking about every possible problem up-front... if you expect something different, well, that's not optimal.
You also need to ask about resource time and money budgets here some little start up is not going to have the resources a tier one TLA will have in its black data centre.
I was declined for a position at a trading shop for a C# backend role because I used linq to do something. I didn't have unlimited time for the tests, so I went with expedient over performant, for which they did not care. Fuck that, set clear expectations for interview "tests".