3 ms·
I think one issue with this is that some candidates who might be great at the actual job could, for whatever reason, be bad at this verbal type of simulation. P
by golol 3y ago
I think one issue with this is that some candidates who might be great at the actual job could, for whatever reason, be bad at this verbal type of simulation. Perhaps they work by staring at the problem on their screen a lot, perhaps they struggle to think at the same time as roleplaying. Just saying that this roleplaying aspect is somewhat tested for and doesnt align with the job exactly.
- mock-possum 3y agoYes precisely. Make sure that you’re actually selecting for what you mean to be selecting for.
- paulcole 3y agoA lot of companies would much rather pass over a great fit than hire a bad fit. Not hiring great people isn’t that bad of a thing in most cases.
- abathur 3y agoThe interview the post describes actually sounds like a good format for me, but I do have some problems adjacent to the ones you mention. As someone who struggles with ~parallelizing some tasks (especially when anxious), it would be great to have an up-front check in about how comfortable I am with the format of any technical ~challenge. (And even better to discover there's some wiggle room to accommodate.) For example, I find it very difficult to code my way through a problem and narrate what I'm doing and take feedback while I know I'm being evaluated and the clock's ticking. If the interviewer says something important in the middle of this, I often have to put down any plates I've managed to get spinning (and maybe go offload some adrenaline) and then ask them to repeat before I can even parse the words they said, let alone figure out how they apply to the problem.