Interviewers can read code, not your mind. Unfortunately, hiring decisions often HINGE on how a candidate thinks.... or rather how they communicate their thoughts.
Many candidates are given the generic advice to "share your thoughts out loud," but if you're trying to impress interviewers during a technical interview, that advice is not 👏🏼 good 👏🏼 enough 👏🏼
In this video I share what you should be saying instead. I'm talking example phrases AND what your interviewer is honestly looking for and thinking. You may not be able to read their minds, either, but you can pretty dang close!
0:00 - Honest intro
1:01 - Why not narrate?
2:59 - Narrating your thoughts out loud is not good enough
Examples:
3:29 - Taking a shortcut
3:50 - Design decisions
4:21 - Intentions when do something different
5:00 - When you run your code, get more credit
5:52 - Whenever there is an error or problem !!
6:24 - THIS IS THE ONLY TIME 🤫
7:47 - The last thing I'll say about narration 🤮
- Mood by Lake from Infinity Train
- Music by Dyalla and Gunnar Olsen
CANDIDATE PLANET:
Empowering candidates to ace interviews, negotiate offers and advocate for themselves at work. Leave a comment or email Lusen@CandidatePlanet.com with questions you want me to answer.
SUBSCRIBE \o/:
☆ Youtube ☆ https://youtube.com/CandidatePlanet
☆ Spotify ☆ https://open.spotify.com/show/39mwa4oOlKC7dMaNbLNFYE
☆ Newsletter ☆ http://newsletter.candidateplanet.com/
☆ LinkedIn ☆ https://linkedin.com/in/lus
SALARY NEGOTIATION PLAYLIST:
☆ https://www.youtube.com/playlist?list=PLY0uEDNh-Haqes9eEvyGtzrUWOHv-c1op
ACE YOUR INTERVIEWS PLAYLIST:
☆ https://www.youtube.com/playlist?list=PLY0uEDNh-HarP6UtKFYRJZnkXzz4ICi73
Top comments (1)
"Well, some thoughts are dumb" hahahahaha very true! Great actionable advice :) I'm very new to the coding interview process, how do you suggest we practice?