DEV Community

Discussion on: 11 Mistakes To Avoid On A Technical Interview

Collapse
cat profile image
Cat

Great, awesome, wonderful advice! Explaining the method to your madness goes such a long way. 10+ points to the interviewee if they don't use buzzwords.

Thank you for writing this! Sharing ASAP.

Collapse
buinauskas profile image
Evaldas Buinauskas

I don't think there's anything wrong with buzzwords as long as you know what exactly they are and they're used correctly.

But generally speaking, the less of them, the better. Yep.

Collapse
ice_lenor profile image
Elena Author

I agree: I'm fine with any technology if it's applicable and if the candidate knows it or about it at least a bit.

Interestingly enough, no one has tried to use blockchain on my interviews yet.)

Thread Thread
rhymes profile image
rhymes • Edited on

The day will come when a candidate will answer "How would you sort an array of 10 numbers?" with "Well, have you heard about the blockchain? Let me mansplain it to you " 🤣

Thread Thread
khophi profile image
KhoPhi

And then they start with the history of Blockchain and how great the mystery developer behind is....

Thread Thread
vinayhegde1990 profile image
Vinay Hegde

Couldn't have been explained more lucidly, thanks Elena :)

Pardon me for asking a silly question but how would you recommend handling the situation if the Interviewer does all of it instead of the candidate?

Thread Thread
ice_lenor profile image
Elena Author

Hi Vinay,
Haha, that must be funny :). Depending on what they do, sometimes I wouldn't want to work with them, whatever side of the interview they're on. I think during the interview I would do the same what I do now: politely listen, ask some questions to make sure I'm not imagining things.

Then I would weigh this problem against benefits. Is this place otherwise good to work at? Is it only one person doing that? Was it just one occasion? Maybe I could decline the offer if I decide this is too bad and is very common in that company.

For candidates you can provide feedback, saying, for example, that they didn't motivate their decisions. For interviewers, however, this is not very common practice, so I would just let it go.

And what would you do?

Thread Thread
vinayhegde1990 profile image
Vinay Hegde

Hi Elena,

Yes it's funny sometimes because it leaves you wondering as to how they got selected in the first place. Most of the times, it's downright rude!

Since I believe in the theory "Do unto others what you would have them do unto you" so I always strive to listen, ask queries about the company and role I went in for and in general interact courteously during interviews. Regardless of my skills, I like to make a positive impression of myself wherever I go for an interview - in person or remote.

Also, I'd have a similar approach as your second point which needs atleast 1-2 more interviews with different team-members to determine answers to those questions but then again, you're at a company's mercy to be getting it.

Quick question - What should a person do if a company gave them a very good offer and appears to be a good place to work but they found the aforementioned interviewer would be their senior or lead?

Thread Thread
ice_lenor profile image
Elena Author

Thank you for your reply, Vinay.
I don't know what I would do in that case, honestly. I guess I would very carefully weigh all pros and cons - just like when you encounter any other "con". I don't think there's a universal recipe.

Have you been in a situation like this? What did you do?

Thread Thread
vinayhegde1990 profile image
Vinay Hegde

Thanks for the response, Elena!

While I understood that careful evaluation of all pros and cons is the way to determine whether to take the job offer however even I've never been in a scenario like the one I mentioned until now.

Assuming if I were to, I'd have a one-to-one discussion to let that person know a good professional rapport is a two-way street which I believe would do the trick :)