DEV Community

loading...

Discussion on: What was your win this week?

Collapse
itsasine profile image
ItsASine (Kayla)

I conducted an interview, being the kind of interviewer I wish I would have. Trying to make hiring a little less painful for all involved a little at a time.

Transparency, no whiteboards (at least for associates... I might lose that fight for seniors.), keeping it casual to not play into the power dynamic. Just us chatting to figure out if we want to work together.

Collapse
stereoplegic profile image
Mike Bybee

Great job. If I've learned anything from interviews, it's that the candidate learns far more about me/company culture (none of it good), than I will about them, by creating an on-the-spot, high pressure, watched/timed environment. Conversely, I've learned that it's far easier to detect BS when the atmosphere is relaxed.

Collapse
itsasine profile image
ItsASine (Kayla)

The hiring manager is a tad miffed I didn't do the high-pressure whiteboard interview... this was for an associate role. Either, he doesn't know the code yet, as we know from his resume and the chat I had with him, or he's a hidden code savant and looking at a little login function and asking him what it does is going to be patronizing. Most likely both, it'll be patronizing and useless as we know he hasn't coded professionally. It's better to just have a chat and figure out what he wants to learn and know and what he's researched on his own. I can teach him the code later.

Thread Thread
stereoplegic profile image
Mike Bybee

The high pressure, looking over your shoulder approach (not referring to pairing, that's a whole 'nother discussion) has no basis in the reality of a developer job at any level (and if it is a reality in your job, RUN). Any senior dev who thinks this is an effective interview method should know better.