DEV Community


Discussion on: Let's face it, we have a broken technical interview process in our industry

190245 profile image
Dave • Edited

I'm not confusing the terms at all. I'm trying to find a way that works for everyone in the process, genuinely.

I need to, at least hazard a guess, at how a candidate (at any level) might cope with work pressure. How am I to do that, without risking some performance anxiety?

Would you suggest, instead, that I focus on removing work pressure? (We already have very little of it)

Further, if they have performance anxiety in an interview, are they not likely to have the same (and suffer imposter syndrome etc) while working? Unfortunately, even with juniors, I don't have the budget to help improve their confidence over the next (as an example) 6-12 months.

I completely understand that some people suffer panic attacks etc, and I wish them well with their health & their career - but I'd much rather know about that up front, and take it into account. Who knows, for the PERFECT candidate in every other way, I could probably spend the time to shield them from sources of anxiety in the office. I've just never talked to the PERFECT candidate.

As another point of topic, I worked with a senior once who didn't realise what he was feeling was imposter syndrome. He could do the job perfectly well, but group meetings made him anxious. So we changed things up for him, and made more of a point of showing him his successes. The point being, he communicated, and essentially asked questions. Apparently, him talking to me, putting a label on it, and him researching about it helped him in his personal life, and he's spotted the same in other people.

If people cannot ask questions, for whatever reason, then we're going to have problems.

Thread Thread
deepu105 profile image
Deepu K Sasidharan Author

Asking questions have nothing to do with live coding or whiteboarding. I don't think people suffering with anxiety or imposter syndrome have problems asking questions. They will ask questions if they have any. Problem is unable to code or solve a problem (which they will be able to do perfectly fine in a normal work situation, even with time based pressure or some other work pressure) when they know that there is a person watching their every move and evaluating it (doesn't matter how nice or comforting you sound, its hard to control how a brain works) from what you said it seems like you care about people you hire, so just switch to take home assignments or worst case, something like codility, then have a review session to talk through what they did. It will give you more insight into the candidate and they will feel much more at ease and perform much better.

Thread Thread
190245 profile image

Asking questions have nothing to do with live coding or whiteboarding.

Specifically whiteboarding, I probably don't do the way that most people do. I use a whiteboard for the very purpose of them drawing something they know (or should know, if they've been paying attention in their previous/last role), in order to generate the questions I ask.

I think that probably differentiates on that key principle, other than the candidates history, I don't come into an interview with a pre-set list of questions. It's much more akin to a conversation, and if it's not a two way conversation, with the candidate asking me (sometimes very tricky) questions, they probably won't get the job.

That's probably why I (probably incorrectly) jumped from "performance anxiety" to "debilitating anxiety" - while they have commonalities, it's most definitely not the same thing.

Back to whiteboards, the best one I had, was an interviewer asked me to "draw the testing triangle" - nothing more, just wanted to know if I knew it. It's the kind of thing that as a developer, we never really bother thinking about, but should definitely be aware of.

Problem is unable to code or solve a problem (which they will be able to do perfectly fine in a normal work situation, even with time based pressure or some other work pressure)

In any situation, interview, daily work, shopping - if someone can't tell me there's a problem, there's nothing I can do. However, tell me there's a problem, and we'll move mountains (hopefully together) to put it right.

switch to take home assignments

Seniors get a take home assignment, juniors don't. For a little better context with what I do with juniors, check my post (and please feel free to give feedback, knowing the context better):

Off-topic (for this conversation) - I didn't see your job title until today, when I decided to read the thread fully on my laptop, instead of my phone. It was actually a junior developer (in the job, not in an ineterview) that introduced me to jHipster, and while it doesn't quite work well for us, we do make use of it where sensible. So kudos on working on something that other dev teams use (our work is all internal only, very specific domain knowledge etc).