> the entire goal of tech hiring is just finding people in the 100 to 115 midwit block then outright rejecting everybody else as too much of an unknown risk.
This is clear to me. My performance on tech tests is extremely mixed. I either do extremely well or I don't finish the test due to time constraints. With long-format tests where they give at least 2 hours, I tend to do well but some tests have contrived explanations and unclear requirements and short durations... Like sometime, they give you a weird, contrived goal which could only exist under lab conditions but they don't tell you up-front that your solution needs to be efficient as if it was built for the real world... Then you run their tests they provide and realize that some of them fail because your solution doesn't meet the efficiency requirements and it wasn't the exact same solution they were looking for... Ok fine, I can do that way too but you just wasted 30% of my valuable test-time under the false pretense that any correct solution would be fine...
So because you added this arbitrary time constraint to your test, I was optimizing my solution for implementation speed but now that I've built the solution and run the tests, you tell me that I had to optimize it for performance. But now because I wasted 30% of the test's duration going down the simplest path, there is no way I will be able to complete the test in time. Great...
This is clear to me. My performance on tech tests is extremely mixed. I either do extremely well or I don't finish the test due to time constraints. With long-format tests where they give at least 2 hours, I tend to do well but some tests have contrived explanations and unclear requirements and short durations... Like sometime, they give you a weird, contrived goal which could only exist under lab conditions but they don't tell you up-front that your solution needs to be efficient as if it was built for the real world... Then you run their tests they provide and realize that some of them fail because your solution doesn't meet the efficiency requirements and it wasn't the exact same solution they were looking for... Ok fine, I can do that way too but you just wasted 30% of my valuable test-time under the false pretense that any correct solution would be fine...
So because you added this arbitrary time constraint to your test, I was optimizing my solution for implementation speed but now that I've built the solution and run the tests, you tell me that I had to optimize it for performance. But now because I wasted 30% of the test's duration going down the simplest path, there is no way I will be able to complete the test in time. Great...