45 ms·

I've just finished this maddening process for the 4th time in my "career" and it was as frustrating as i remember. To all potential employers and recruiters: W

I've just finished this maddening process for the 4th time in my "career" and it was as frustrating as i remember. To all potential employers and recruiters: When a candidate asks you for the agenda or some indication to the structure a meeting will take its because they want to be prepared. They aren't trying to "cheat", they want to be as productive as possible. Unless your company operates some insane work methodology where preparation for any task is strictly forbidden i don't understand why you wouldn't give them this info. Twice in my last round of interviewing additional people where added to the call with short or no notice. These people where obviously experts in their technical niches so expecting me to preform well in a 30 minute grilling unprepared seemed unreasonable.

sokoloff 6y ago
My experience is that when obvious experts in niches are added late to an interview loop, that’s almost always a positive sign for the candidate. Those people are generally busy and aren’t on the “everyday candidate” loop typically.
tumetab1 6y ago
For some reason developers seem to assume that the recruiting process is immune to the regular company dysfunctions. If they scheduled an interview without an agenda is because it's the norm to do that within the company when talking with outsiders. If someone jumps in to a call, it's their practice to have surprise guests within meetings. If someone ask you subject matter expert questions, it's how the company sees developers, as subject matter experts. So, you were interviewing to a company which views, my guess, developers as subject matter experts, has people jump in into calls and doesn't prepare specific calls.