What I'Ve Learned From Giving Coding Interviews
What I'Ve Learned From Giving Coding Interviews
that, for a while, that’s what prevented me from finding a new job.
This just didn’t feel like an efficient use of my time when I could
did help, but there’s so much more to them than knowing the
language.
At the time, I didn’t quite realize what makes one candidate stand
This may seem so simple but you’d be surprised how many people
The week before your interview, spend at least an hour each night
You may feel like you’re failing by searching for answers, but
It’s a more efficient use of your time to find the solution you are
looking for rather than racking your brain for something you
have familiarity with window functions that could help you solve a
2. Clarify assumptions
to assume one thing and work out the entire solution only to find
talking through what they were doing, only to be totally off base
This will save you time, which can be valuable if the company is
To reiterate, talk talk talk! The more communicating you do, the
you’re thinking about it, it’s easy for the interviewer to get lost and
easier to pinpoint where the mistake occurred and to easily fix it.
In the end, this will save you time in working through difficult
Even if it seems obvious to you what you’re coding, talk about it!
You can’t always assume your tactic to solve the problem is the
you know what function you are trying to use, but forget the exact
name, ask.
For example, in one of my Python interviews, I needed to use the
also unsure and quickly searched for the right function for me to
use.
aren’t testing you to see if you can remember every tiny detail of a
language. They want to understand how you think about and work
Don’t fret the small stuff like remembering the exact function
Conclusion
We put way more pressure on ourselves for coding interviews
was most efficient. However, I practiced all four of these tips and