3 ms·
Hopefully they paid you for that time they wasted, though I doubt it. Reminds me of interview code assignments. Sometimes they don’t even care if you solve any
by austin-cheney 2y ago
Hopefully they paid you for that time they wasted, though I doubt it.
Reminds me of interview code assignments. Sometimes they don’t even care if you solve any problem. Programming is sometimes not the point, and in those cases it comes down code vanity. It’s a test to determine if the interviewer can read the code, because they probably can’t, even with ample code comments and test coverage and formal documentation, and somehow that is the fault of the candidate with several hours wasted.
At any rate I have signals that I look for during the interview, that I learned while unemployed, and I try to drop out as early as possible if it smells childish.
- JohnBooty 2y agoDo you give them feedback about why? I've only had one that I had to cut short recently, and I did. I wasn't sure if I should or not. I can think of valid reasons why to do it and valid reasons not to.
- darth_avocado 2y agoI don’t if the process is standardized for the company. In that case you don’t do anything beyond sounding salty. If it’s a team specific thing, then yeah, I try to point it out in the most polite way possible. I recently had a “culture fit round” at a company, again for a software engineering position, where I had to meet 3 people (one in sales, one in legal and one was the receptionist for the building) and chit chat for 45 mins. Not that I did poorly, but the whole thing was kinda awkward and didn’t really add any value except confirm that I was not an introvert (which I totally am, but can pretend I am not for short amount of time).