3 ms·
I had the experience of going through 14 rounds of interviews (excluding the HR calls), where the manager and the team liked me. And then had a 15th interview w
by darth_avocado 2y ago
I had the experience of going through 14 rounds of interviews (excluding the HR calls), where the manager and the team liked me. And then had a 15th interview with a “cross functional stakeholder” where the interviewer was super busy and couldn’t schedule an interview for a while, eventually scheduled a 30 min “conversation” where she asked domain specific business questions that you wouldn’t know answers to if you didn’t work in that company and then rejected me for not “getting the right signals”. Never mind the 15 approvals from the interviews prior and the fact that this was a generic software engineering role. This is a company that prior to the interviews said “we value everyone’s time, so if at any point we feel it is not a right fit, we’ll cut the interviews short, even if more are scheduled for the day”. They also apparently schedule the interviews in the increasing order of seniority of the interviewers because they want to ensure they save company time by cutting interviews short and not having the senior interviewers interview candidates that are not a great fit.
- austin-cheney 2y agoHopefully 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).