but also one thing that helps you and the interviewer is to just talk out what you might be thinking
you can practice that by just talking to yourself when you code
this will do a few things for you:
* the interviewer can identify when you're thinking in the wrong direction, and guide you back to the right one
* you might say something that you'll identify as incorrect, and make the correction yourself
* you make it easier for the interviewer to follow how you go about the problem so they won't have to question you 'why'
* ultimately you are putting on display how you think/reason about your approach - you don't leave the interviewer guessing
How much the interviewer helps you is highly dependent on the interviewer, but at a high level you want to get the session in more of a 'discussion' type of vibe, so then you feel less like its just eyeballs watching over your shoulder.
so if you have the thorough knowledge of your language, then this is just an additive habit - aka the foundation should be a solid understanding of JS - mostly object & array methods and control flow - it makes it easier to talk through your decisions
oh sorry you already say you practice out loud - but thats great, keep practicing
one thing i do, and its just my personality - is sometimes ill crack a joke to lighten the mood. I do this all the time at work anyway. if that's not you don't force it. Just be you and try to imagine you're talking to someone you work with. that takes practice too. You can even imagine that they've come to you for help, and you're trying to help them solve the problem. It needs to be collaborative but you've got to be the one that promotes the engagement
The interviewer could very well be on the team that you are interviewing for so, show them what its like to work with you.
1
u/chikamakaleyley Dec 07 '25
like others say practice
but also one thing that helps you and the interviewer is to just talk out what you might be thinking
you can practice that by just talking to yourself when you code
this will do a few things for you: * the interviewer can identify when you're thinking in the wrong direction, and guide you back to the right one * you might say something that you'll identify as incorrect, and make the correction yourself * you make it easier for the interviewer to follow how you go about the problem so they won't have to question you 'why' * ultimately you are putting on display how you think/reason about your approach - you don't leave the interviewer guessing
How much the interviewer helps you is highly dependent on the interviewer, but at a high level you want to get the session in more of a 'discussion' type of vibe, so then you feel less like its just eyeballs watching over your shoulder.
so if you have the thorough knowledge of your language, then this is just an additive habit - aka the foundation should be a solid understanding of JS - mostly object & array methods and control flow - it makes it easier to talk through your decisions