loading...

Common Mistakes in a Coding Interview

tiptopgs profile image Jen Chang ・1 min read

I’ve been following the Tech Lead and love some of his raw advice on tech careers. He sometimes talks lots of sarcasm and I like it. It is about being human. This sketch is a summary of what he shared on his recent video on common mistakes in tech interviews.

I think it’s pretty standard and generally good advice. Coding on the spot is something that always intimidates me due to lack of practice but I’m glad most folks out there share the same feeling.

I generally feel more comfortable with companies that ask questions based on your work experiences like my current company. For college or university interviews, we generally ask more algorithms and data structure questions. It’s reasonable because they might lack the work experience. But what do you think? Is it better to do one approach over the other? Which one do you prefer?

In terms of the topic, what other mistakes have you seen in coding interviews?

YouTube video by the Tech Lead

Discussion

pic
Editor guide
Collapse
jess profile image
Jess Lee (she/her)

👋

Just wanted to let you know that youtube videos are embeddable if you want to include them in your post! Here's the syntax if you want to try it out :)

{% youtube pV7XIZnsbgM %}

Also thanks for sharing the Tech Lead! I'd never heard of them before.

Collapse
tiptopgs profile image
Jen Chang Author

Thank you, Jess :D

Collapse
le_newtype profile image
Nicholas ―M―

I've done a few interviews (as the interviewer: I've done many many more as the interviewee) and the biggest thing I noticed is that people don't like admitting they don't know something.

If you haven't heard of this function or this feature or this concept, tell me! I'd rather talk through what it does with you to see if you understand why it's useful or how to apply it, than watch you flounder for the answer you think I would like to hear or stare at me blankly until I move on.

Maybe I'm too optimistic, but I like it when interviews are more like conversations gauging to see if I will like working with this person, and less like standing in front of a firing squad, seeing what knowledge you can recall offhand.


I think the referral bit is situational. It's not going to be possible to accomplish this for ever position you want to go for unless you sink a bunch of time faking being interested in someone's life on LinkedIn for long enough to get a referral out of them, or genuinely know someone who works for that company.

Plus, in my experience, my company has rejected or been rejected by every single referral for a developer that we've gotten after speaking with them (for a number of reasons or circumstances that weren't going to work out) and have hired "randos" (myself included).

If you know someone who can refer you, definitely go for it, but I don't think you should limit where you apply based on not having one.

Collapse
tiptopgs profile image
Jen Chang Author

Thank you for sharing your thoughts, Nicholas =] I've heard it from multiple sources that referrals help. If not for getting hired, but at least it gets their foot in the door. There's no guarantee that they'll get hired.