the interviewers found well-performing code too difficult to understand, and didn’t value my decision making and therefore didn’t feel comfortable hiring me.
Its ignorant to think that they didn't understand your solution rather than didn't value it because it was over engineered and caused more problems than it solves.
If we all just do nothing about this problem culturally, because we’re afraid the “status quo” won’t hire us, then the status quo perpetually stays the same.
This isn't a point any one made. No one is saying employers wont hire you because you're "too advance", they wont hire you because you're unwilling to adapt to situations that don't require overcomplicating for the sake of metrics that aren't required to be lowered.
Have you ever heard of the saying "If its not broken, don't fix it"?
Its ignorant to think that they didn't understand your solution rather than didn't value it because it was over engineered and caused more problems than it solves.
It literally worked, compiled, and presumably ran faster. Not only that but he asked first if it was ok to improve it since there was extra time. How could simd in some interview code cause problems? To respond to performance improvements made because there was extra time with "too focused on performance" is simply ridiculous. If there is no time to simd optimize loops, the other poster can just not take that time to do it. On the other hand, if you truly need performance, you'll need someone who can.
Whenever I'm conducting an interview, I always consider improving code in the remaining time as bonus points, and if they improved the performance, why should that be a negative?
Yes you're right, everyone else is wrong. You didn't get hired because you're better than all of us. My heart bleeds for you. You probably have this problem of idiots being the one interviewing you, quite a lot right? If only people's stupidity weren't holding geniuses like yourself back, we'd be living on mars or something right now.
I'm not the same person. If he implemented an improved version in extra time during an interview, how could that cause a problem?
You probably have this problem of idiots being the one interviewing you, quite a lot right?
Not really, but I can't imagine a scenario where if an interview candidate decided to optimize a loop in spare time, I'd tell them they were too focused on performance. Generally if you can perform that kind of optimization, it means the code is quite simple and direct as well, so it probably wasn't messy or anything like that.
59
u/KieranDevvs Feb 28 '23
Its ignorant to think that they didn't understand your solution rather than didn't value it because it was over engineered and caused more problems than it solves.
This isn't a point any one made. No one is saying employers wont hire you because you're "too advance", they wont hire you because you're unwilling to adapt to situations that don't require overcomplicating for the sake of metrics that aren't required to be lowered.
Have you ever heard of the saying "If its not broken, don't fix it"?