@yang5843
When people are nervous emotionally, their logic brain doesnt work properly.
@enrico8730
Id recognize neetcode's voice as soon as I heard it in an interview
@AnkitaNallana
After having gone thru some brutal interviews and listening to you say that 10mins in they're really struggling and that it's gonna be a long 35 mins ahead and that you felt bad for them - thank you for saying that, good to know that. As an interviewee I never get to know about that part of the interviewer so it's good to know that you were one of those!
@puddleglum5610
I’d say it’s probably nerves. In one of my final interview rounds with Google, my brain pretty much just stopped functioning correctly and I completely lost track and started making stupid mistakes. The problem was easy too—if I had just taken a deep breath and recomposed myself, I would’ve crushed it. Luckily, it didn’t end up hurting me too bad because I accepted a really good offer at another company (got an exploding offer) before I could get through Google HC.
@sigfigronath
im really loving this series of personal stories
@nomad6913
One constructive criticism I have for Neetcode, is that problems should be ranked with regard to acceptance rate. This has many benefits: 1) solving problems on your own 2) getting confident 3) gradually being able to solve harder problems.
@-----0-----
02:03 - "get really, really good at basics" - it's not the reason ;) This situation happens due to many well-known human being specifics - it can not be solved just by "get really, really good at basics" Just few of them and there are much more there: High-stakes situations, like interviews, trigger the body's fight-or-flight response, releasing cortisol and adrenaline. This can impair memory recall and focus, making it harder to retrieve information that you normally know well. An interview requires you to juggle multiple tasks: answering questions, reading the interviewer’s reactions, structuring your response, and managing nerves. This overloads working memory, making it difficult to retrieve information quickly. When you know you’re being evaluated, fear of making mistakes can cause self-doubt. Instead of recalling knowledge naturally, you may start second-guessing yourself, which makes recall harder. Memory is often context-dependent. You may recall information better in familiar settings (e.g., your workspace). An unfamiliar environment (interview room, video call) can disrupt memory retrieval.
@ness3963
Had a moment like this where I messed up on a basic if statement that would normally be automatic for me. The nerves make your brain go completely empty. It’s like suddenly you’re thrown back to the first time you took AP CS and everything becomes cloudy
@SquirtleSquadee
the dude who told you to pick harder questions explains everything about why programming interviews are a mess. too much focus on trivia and less on the skills that matter, like the ability to find solutions and execute on them with clean code. leetcode and sites like it, along with senior programmers like the one you mentioned need to stop existing
@schan263
I prefer to be interviewed than interviewing others. I felt that I was more nervous than the candidates.
@Coderell
I think adding more easy problems is a good idea.
@xPussySlayerx69420
At google I asked (find the avg of a set of numbers) as a warmup, I explicitly told them it’s not a trick question. I expected for this to take like 2-3 minutes but it usually ended up taking like 15m before I would abort the question and move onto the “real” question. Even the Stanford grads that I interviewed couldn’t do it within a few minutes. People really need to learn the basics.
@albertohuerta
When I failed an Amazon interview, I remember cramming leetcode trying to get all the information without practicing the basics.. guys I choked at a palindrome related question during whiteboard interview.
@venkateshchakravarti2817
Exactly my situation where I know the solution but cant able to code in interview
@anotheraleks
I thought that if you struggle writing a for loop, you wouldn't even come close to a Google interview
@black_wind2794
It still is incredible to hear that there are people interviewing at Google that don't know how to write a for loop... Like how did they pass the resume screening in the first place? I probably need advice from them 😅
@cyclox73
Nerves will get the best of you for sure but an for/while/if etc should be second nature and shouldn’t even been a barrier during an interview. I do fear that gpt/ai is messing a bit with people who are just getting into dev…. Why know how to write a for loop when it just happens automatically?
@JasonLatouche
What I really hate about these online interview coding environments is the lack of auto-suggest or intellisense. I have gotten so used to it from pretty much any modern IDE and code editor that I often forget how to do pretty simple things without it...
@theophilusowusu470
This is exactly my life yesterday interview with Microsoft.
@victortruong2538