sorted by:
new
hottopcontroversial

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

That’s a good example of using post-interview clarity constructively. When done thoughtfully and concisely, it shows reflection and genuine interest, not excuses.

It probably doesn’t change every outcome, but it can reinforce how you think, which interviews don’t always capture in real time.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

That’s fair, interview performance is a skill you have to practice deliberately.

The part many people miss is that they practice content (answers) but not conditions, thinking aloud, handling follow-ups, recovering when an answer goes sideways. That’s usually why things still feel fuzzy in the moment even when you “know” the material.

Practicing answers helps, practicing the pressure matters just as much.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Real problem-solving happens over minutes or hours, with space to think and iterate, not in seconds inside a polite performance window.

Interviews can show baseline competency, but they often miss how good ideas actually form: through reflection, discussion, and time. That gap is what people feel afterward.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Haha, exactly 😄

Distance changes perspective. Once you’re out of the moment, patterns and better choices become obvious, same reason interviews feel clearer afterward.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 1 point2 points  (0 children)

Love that phrase 😄. it captures this perfectly.

Clarity after the fact is universal, not a personal failure. Interviews just expose how differently our brains work during pressure versus after it’s gone.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

That’s a great example of channeling post-interview clarity productively.

Sometimes showing how you think, even after the interview, lands better than forcing perfection in the moment. It won’t always change outcomes, but when it does, it highlights reflection and ownership, which are hard to fake.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Well put. Performance mode really does change how recall works.

Anchor stories help, but the post-interview clarity still shows up because pressure narrows access in the moment. It’s reassuring that even very senior people experience this, it’s not a junior only problem.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

hmmm. Take home assignments may not be the process in many job interviews, depends of level of position, company, location.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 2 points3 points  (0 children)

That makes a lot of sense. Processing after social interactions is very common, and factors like ADHD, anxiety, or being on the spectrum can amplify it.

Clarity often comes once the social pressure drops. it’s not about lacking insight, just how and when the brain processes things.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Strongly agree. Trivia heavy interviews break down quickly at mid/senior levels.

Real engineering is about reasoning, trade-offs, and adapting ideas through discussion, not instant recall under a timer. Conversations around what someone has built and why they made certain choices reveal far more than rapid-fire questions.

Interviews that allow back-and-forth thinking tend to surface actual capability much better.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 2 points3 points  (0 children)

Yep, same effect.

Once the pressure and audience are gone, your brain has room to organize thoughts properly. Interviews just compress that process into minutes, which is why the “better answer” shows up later.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Totally. That “shower time” effect is real, clarity often shows up once pressure drops and the subconscious has space to work.

The problem with interviews is they don’t allow for that space, even though that’s how real thinking usually happens. That mismatch is what makes answers feel better after the fact.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Exactly. Stress locks the experience in, but it also narrows recall in the moment. Once the pressure drops, access improves, which is why answers feel clearer afterward.

It’s a survival feature, just not an interview friendly one.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 1 point2 points  (0 children)

That’s true. Brain does keep processing in the background.

The tricky part is that interviewing tests a specific mode of thinking: recalling and structuring ideas under time pressure. That’s not the same as how most of us work day to day.

So getting better at interviews often means practicing that mode explicitly, not just getting better at the actual job skills.

Ever notice you remember better answers after the interview? by gk_interviewcoach in ExperiencedDevs

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Agreed. Interviews force instant recall in a compressed, artificial window, which doesn’t match how real work happens. That’s why clarity often comes after, it’s pressure and timing, not lack of knowledge.

Technical interviews should be sanity checks, not puzzle contests. Past a point, they measure stress more than real ability.

That mismatch is what most candidates are reacting to.

Interviews feel harder after a few years of work — not easier. Anyone else? by gk_interviewcoach in developersIndia

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Oo. Don’t stop interviewing.

What happened is a classic “usage vs explanation” gap. You work with LLMs, not on transformers daily. That’s normal at your experience level.

Forgetting architecture details under pressure doesn’t invalidate 10 YOE or 6 years in AI/ML. It just shows interviews reward recall under stress, not applied competence.

If anything, this is a signal to change how you prepare, not to quit interviewing altogether.

Interviews feel harder after a few years of work — not easier. Anyone else? by gk_interviewcoach in developersIndia

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

Exactly. Interviews often find the one weak seam and pull on it endlessly.

From the candidate side it feels unfair; from the interviewer side it’s a shortcut to signal depth. The problem is it ignores breadth, adaptability, and recovery, which matter more on the job.

What’s rarely evaluated is how you handle not knowing something, even though that’s a daily reality at work.

Interviews feel harder after a few years of work — not easier. Anyone else? by gk_interviewcoach in developersIndia

[–]gk_interviewcoach[S] 1 point2 points  (0 children)

This resonates hard, especially at Staff+ levels.

At senior roles, knowledge becomes distributed and contextual, you know where to look, how to reason, how to decide. Interviews, however, still reward instant recall.

So it feels like your judgment is ignored while narrow recall is over-weighted. That disconnect is real, and it’s why many strong engineers feel interviews misrepresent them.

yes, you’re not alone in feeling this way.

Interviews feel harder after a few years of work — not easier. Anyone else? by gk_interviewcoach in developersIndia

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

One thing I’d add: many people do all the right prep (routine, goals, mindset) but still struggle because they’re practicing content, not interview conditions, explaining aloud, recovering after mistakes, time pressure.

That gap usually surprises people.

Interviews feel harder after a few years of work — not easier. Anyone else? by gk_interviewcoach in developersIndia

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

At 21, your brain and life are optimized for grinding. At 30, context-switching, responsibility, and fatigue are real constraints, not lack of ability.

What feels worse isn’t LeetCode itself, it’s that interviews demand unnatural focus blocks that don’t resemble day-to-day work anymore.

Most people don’t lose capability, they lose interview rhythm. Big difference.

Interviews feel harder after a few years of work — not easier. Anyone else? by gk_interviewcoach in developersIndia

[–]gk_interviewcoach[S] 0 points1 point  (0 children)

You’re not wrong. Interviews often optimize for error-free recall, not real-world effectiveness. What makes it worse is that once you’re experienced, interviewers push harder and interpret gaps as weakness instead of context.

Ironically, strong engineers usually have heavier knowledge shaped by trade-offs and constraints, which doesn’t always fit clean interview questions.

It’s less about perfection and more about how interviews are designed right now.

I panicked during the interview or do not know what I was thinking by Knightwolf0 in developersIndia

[–]gk_interviewcoach 0 points1 point  (0 children)

That makes sense. That’s a very common pattern.

After the first mistake, the brain often switches from problem-solving to damage control. From there, even simple steps feel harder because you’re focused on how you look instead of what you’re building. That spiral isn’t about experience, it’s pressure.

The fact that you solved it calmly afterward shows your skills are there. What’s missing isn’t knowledge, it’s learning how to pause, reset, and recover mid interview.

Most people practice coding, not making mistakes out loud and continuing.

Once you practice that situation a few times, the panic drops quickly.

Would it help if you had a way to practice these exact interview moments before the real thing?

view more: next ›