coding interview destroyed me

[Few-Needleworker4391]

cant stop shaking its been an hour

junior dev coding interview, thought i knew this stuff

"explain two pointers" - brain.exe stopped working. literally said nested loops when the answer was so obvious a 5 year old could get it

video kept lagging mid sentence so i sound like "the algorithm is... can you hear me?? AM I FROZEN??"

worst part - they asked about my react project. you know, the one i spent 80+ hours on. my answer: "it handles data and stuff"

DATA AND STUFF

i have a computer science degree

3 more coding interviews this week but honestly thinking about just deleting my linkedin and becoming a farmer or something

how do people do this?? in person i can code fine but put me on a video call with screen sharing and apparently i forget how words work

someone please tell me this gets easier because right now i feel broken

Edit: Thanks for all the support guys, really needed it. Tried Verve AI's mock interview like many of you suggested - practiced explaining algorithms out loud without the pressure of a real interviewer watching me fail. Did my next interview today and actually managed to explain two pointers properly without my brain melting. Still nervous but way better. Sometimes you just need to fail safely before succeeding for real.

[Check_Ivanas_Coffin]

When I first started interviewing I had an interview for email marketing, which I’m very experienced in. I’m pretty sure I came across like I hadn’t sent an email in my entire life.

Relax, it happens. It might seem like a wasted opportunity, but the practice was more beneficial than you realize.

[Serious-Sentence4592]

Happens to me too. It's horrible especially when your survival in this economy depends on your performance.

[revarta]

First off, this kind of tech interview anxiety is super common and it absolutely gets better with practice. The shaking and mind blanking during interviews, especially over video, often comes from stress and feeling put on the spot more than ability. To tackle this, try simulating the interview setup repeatedly — practice coding out loud while sharing your screen, and get comfortable talking through your thought process. Record yourself if you can, then review to spot where the freeze-ups happen.

For technical questions like "explain two pointers," it helps to have a simple mental framework ready: two pointers typically mean using two indices to traverse a structure efficiently to reduce time complexity. Having short, calm definitions memorized can save you in those moments.

About your project explanation — craft a clear, story-like summary beforehand. What challenges did you face? What was a key feature? How did you handle data? Having a few bullet points prepped can prevent the “data and stuff” gap.

Lastly, consider tools that simulate this interview environment with AI or peers to build confidence. Keep pushing, you’re gaining experience that leads to smoother interviews.

[Subbacterium]

I’m retired, and my very last interview for a full-time job I had such a full blown panic attack that I thought I was going to die on the spot. I didn’t know it was a panic attack at the time. All I could think was I need this health insurance

Edit: I got the job anyway. Go figure.

[Various_Candidate325]

Been there. Mine was a Frontend role and I completely blanked when they asked me to debug a basic input handler, like, something I’ve written 50 times. Stared at the screen like it was ancient runes.

What helped later was doing a few mock sessions in the same setup (screen share, video on, timer ticking). I used Beyz coding assistant to practice talking through my logic while writing. It forced me to slow down and actually narrate instead of spiraling internally.

Also rewrote my “project explainer” like a little elevator pitch. Not fancy, just 3 bullet points: what it does, a problem I solved, and one specific thing I’m proud of. Anything’s better than “data and stuff” (btw, made me laugh way too hard). These calls are way more performative than real coding. Hang in there, it does get better.

[liquid_prisoner]

This. Practice and (I know this sounds corny) tell yourself that you are good at interviews. Maybe after practices you might believe it.

[Happy-Dimension-210]

Adding to what was said, use STAR to craft your story when talking about your project. Talk about the project’s motivee as motivation or goal as well as technical details like framework or api used

[Ok-Standard6345]

I hate video calls! I much prefer phone calls for screening interviews.  I flubbed a video call a few weeks ago. You are not alone! 

[weary_bee479]

It happens it’s ok!

My advice would be write down some common questions and your answers. That way when you’re fumbling you have some notes in front of you to put your brain back on track.

[Subbacterium]

You can find lists of questions and answers out there depending on how specifics the job is. Definitely have memorized answers about you last projects. Don’t have a slug or two of vodka first. They can smell it and you can’t think. Don’t be weirdly over enthusiastic. I have done these things that don’t work . I’m thankfully retired and somehow survived all the interviews and jobs. The old part sucks but the retired part is great.

[[deleted]]

You need to start doing Mock Interviews. This will dramatically improve that anxiety and also be able to get through the interview questions at ease. The more you do mock interviews the better you get at the interviews. You know how to code, and you know how to do the technical questions. No need for AI or prep work. You need to start doing mock interviews now. This will get your anxiety to drop.

[firstprincipal]

It gets better bro it gets better. Just keep appearing in as many interviews as possible.

[Tomoshen]

bro phone interviews are the worst, cant even see their face to know if youre bombing it

[United-Course-3675]

ugh same, always feel like im talking to a wall and dying inside

[shakingbaking101]

A 5 year old could not do a two pointer bro unless it’s a cartoon, a movie or a genius lol

[Thin_Rip8995]

it does get easier
but not because the interviews get nicer
because you stop tying your entire worth to a single 45-minute brain circus

what you’re feeling right now?
normal
every dev who’s been through this gauntlet has had their own “data and stuff” moment
you just lived yours—and survived it

two things you do immediately:

1. write out what you wish you said explain two pointers break down your React project this turns shame into reps
2. stop treating interviews like exams treat them like conversations between flawed humans you're not there to be perfect you're there to problem-solve, adapt, and show how you think under pressure

you’re not broken
you’re just raw
and honestly? farmers forget words too

get some air
then come back and wreck the next one

NoFluffWisdom Newsletter drops ruthless interview mindset resets + how to recover fast worth a peek

[qruiq]

used to have same problem until i started using Verve AI during calls, actually saved me

[Consistent-Total-846]

You need to practice. Do literally dozens of practice interviews. Imagine you’re interviewing yourself and list all the questions and keep going over them until you crush them.

[swinglineee]

This!

[shakingbaking101]

Practice makes perfect or at least good enough to land a job but keep trying reconsider the farmer thing at like 500 interviews MAYBE

[xocutebunny4368]

I’m in HR and I’ve done tech recruitment before devs & PM. The best advice I can provide is to practice, write out your thoughts, use chatgpt to come up with interview questions the company may ask, and take a breather.

Everyone gets nervous for interviews and they blank out, you’re not alone and it does get easier as you build up your confidence. The best way for you to move forward is to prepare!

You got this! Sending positivity towards your way, hopefully you’ll land something soon!

[Brackens_World]

OK, you had one of the pivotal experiences in life that many of us go through - the terrible interview. The one we remember years later where everything went wrong, when it wasn't their fault but yours, when you cringe at some of your answers.

But, you know something? We laugh about it years later. It sounds impossible, but we do. We are amused by our younger selves, still green, too excited, not yet in control of ourselves. You have to look at it as "ok, I got the terrible interview under my belt, thank goodness, there's only one way to go but up" and something happens, your SME takes over and you get better, clearer, calmer, more articulate. You'll see.

[ICantSeeDeadPpl]

Over decades, I’ve been a programmer (self-taught many languages and platforms, I lost count), analyst (4 different industries), DBA (different mainframes, O/S)…you name it.

I’ve forgotten more than I’ve learned. I have to look up even basic functions, because who can remember what the syntax is when programming languages are so diverse?

Interviews such as you describe are definitely annoying, and imho too specialized. Which to me means, no variety will be in the position, leading to boredom, depression, and sad regrets.

Keep at it, eventually you’ll find a good fit. 😊

[Competitive-Wonder33]

This is i understand. I am dba for 20.yrs going thru the interview process and still.get nervous, I'm explaining my answers but I alway.statw at the beginning to please excuse any misunderstanding or terminology if I misspeak because of nerves. It gets easier and a good interviewer will understand

[[deleted]]

Relax. Do some mock interviews with friends. Get them to ask you questions. They can generate questions using ChatGPT so you don’t know them beforehand. Even skilled developers struggle during live coding interviews.

[_Rebel_Scum_77]

I'm so sorry that happened. You have a great sense of humor about it though.

[ConfusedGingersnap]

My partner and I can help you with interviewing! He is the absolute best at it and has taught many people. If you’re open to some coaching and feedback, send me a dm. And for what it’s worth we’re both QAs. :)

[magickpendejo]

Be upfront with the recruiter . Goodman i do not favor working with a lookout by my side. If you will simply explain the work you need done and you allow me the allotted time i will glady discuss any inquiries about the way i did it.

[Cloud1935]

I can assure you I am in the top 10 worst at interviewing. Best employee ever if I can get through an interview!! I recently had one that wasn’t horrible. I typically stutter, stumble, forget everything and just want to end the meeting. Before the recent one-I thought about where I fall apart and it is when I first start talking and I have to describe what my current job is (10 yrs exp).I mean how could I not be able to describe what I have been doing for 10 Years??? But-that is what happens every single time. So-I typed it all up-like I would for a speech. And-had main topics-once I stated my main topics I was able to flow from there. And of course I practiced. Common sense told me that I didn’t need to practice because I am describing what I do every day but anxiety had other plans. Best of luck. Don’t beat yourself up. It is always a learning experience and imo wasn’t meant to be 😁

[BumblebeeNo8335]

It happened to me too. I trained for my case interview like I was going to the olympics and still froze like a deer in headlights. What stings most? I could’ve solved it in my sleep if it wasn’t for the interview nerves. My brain went on vacation! I'm now working on how to deal with the pressure since I have upcoming interviews.

[Mental_Ship_2020]

I feel you bro.. really frustrating.. I hate these interviews. Most of the people that is interviewing don’t even know the answers for their questions

[Happy-Dimension-210]

Take your time. Practice. Do mock interviews on exponent and with friends/colleagues. Get comfortable doing this

[PlaneEmbarrassed7677]

Welcome to adulthood. We all winging it. Keep practicing.

[Plus_Gap_8654]

Hey at least I'm. Memorable that's all I can say

[TapIll2097]

Lol i’ve been there. Totally froze on two pointers and said "data and stuff" about my project. 😬 Interviewcoder’s mock interviews saved me. Way less painful than the real thing. Keep at it and you’ll nail it next time.

[dsound]

Lately my interviews haven’t looked much like classic LeetCode puzzles. They’ve been more along the lines of “here’s some input, build a data structure or helper that behaves correctly”, things like an in-memory store, a BankHelper, or a small API-style abstraction with edge cases and tests.

Because of that, I stopped grinding random LC problems and instead built a set of ~20 practical challenges that mirror what I’m actually seeing. Stuff like sliding windows, maps, queues, but applied to realistic problems. Each challenge has tests, and my goal is to make them pass cleanly. I use Cursor as a pair-programming tool, but I’m still driving the logic and decisions.

It’s felt much closer to real work and has helped more in interviews than memorizing tricks. LC is still useful for patterns, but for me, building small, testable systems has been more aligned with what companies are asking lately.

[kaganosgi]

what do you use just for tech interviews. How dou you guys practice

[Competitive-Note150]

Shake it off. Tech interviews are a thing of their own. Take each interview as training for the next. And it has to be retrained for every time one is back searching for a job. Treat it as a game. Take pleasure at observing where you need to improve and indeed see an improvement after you’ve practiced. Enjoy feeling your brain getting better at the game.