> 1. If you do Google the question beforehand, delete your tracks afterwards
Wait, you get to know the question beforehand!?
> The more you say and do, the more partial credit an interviewer can give you if your code doesn’t fully work
In my experience, if the code wasn't fully correct, you don't pass the interview
> 2. Set up a basic program and make sure you can run it
If they are not using Coderpad
> 14. Talk as much as you reasonably can
Lots of interviewers stress this but I find it annoying that while trying to find a solution I also have to verbalize what I'm thinking, just give me a minute to think
3 comments
[ 3.3 ms ] story [ 14.3 ms ] thread> 1. If you do Google the question beforehand, delete your tracks afterwards
IMO, if you ask me the same question that I had found online, that's on you. Do I have to pretend that I didn't prepare for the interview?
Wait, you get to know the question beforehand!?
> The more you say and do, the more partial credit an interviewer can give you if your code doesn’t fully work
In my experience, if the code wasn't fully correct, you don't pass the interview
> 2. Set up a basic program and make sure you can run it
If they are not using Coderpad
> 14. Talk as much as you reasonably can
Lots of interviewers stress this but I find it annoying that while trying to find a solution I also have to verbalize what I'm thinking, just give me a minute to think