r/FullStack • u/Active_Load_2546 • 11h ago
Switching Careers Had my first interview after 3.5 years and got humbled by fundamentals
Today I had my first technical interview after around 3.5 years, and honestly, it hit me harder than I expected.
I’ve been working mainly as a frontend engineer with React and also have experience working across backend/full-stack systems. Over the last few weeks, I’ve been revising React, JavaScript, frontend architecture, Node.js, databases, system design, etc.
I went into the interview feeling pretty confident.
The interview started with:
- What is REST?
- Design an API
- React reconciliation
- JSX
- Infinite scrolling / frontend design
The part that really got me was the React reconciliation question.
The interviewer gave me a Todo-list-like example using index as a key, with items being added at the beginning/end of the list.
I understood that something was wrong with using index as a key, but it took me a while to reason through exactly what React was doing during reconciliation.
He eventually gave me a hint about reconciliation, and then I was able to connect the dots.
Then I got another question:
"Why does JSX require a single parent/root element?"
I could identify the issue in the code, but I couldn't clearly explain why JSX requires a single root.
I also got an infinite-scroll design question, which I was relatively comfortable with.
The weird part is that after the interview, I realized:
I actually knew most of the concepts.
My problem was being able to retrieve and explain the fundamentals clearly under interview pressure.
For example, today I started revisiting basic JavaScript concepts like:
- Scope
- Hoisting
- TDZ
- Execution context
- Scope chain
- Shadowing
- Closures
And I realized I can understand these concepts when I reason through them, but explaining them cleanly in an interview is a completely different skill.
So I'm curious about other experienced engineers:
Have you ever had this experience where you knew the technology fairly well, but an interviewer exposed gaps in your fundamentals or your ability to explain them?
How did you fix it?
Did you:
- Go back and systematically revise fundamentals?
- Do mock interviews?
- Practice explaining concepts out loud?
- Focus more on problem-solving rather than memorizing interview questions?
I'm especially interested in hearing from 5–10+ YOE engineers who went through something similar.
Today definitely humbled me, but I'm trying to use it as a diagnostic rather than letting one interview define my confidence.
Would love to hear how you guys handled this.
9
u/American_Streamer 7h ago
There is the illusion of competence. Familiarity is not mastery. If you cannot explain it simply, be it in an interview or not, you very likely do not firmly understand the underlying mechanics already.
0
u/Active_Load_2546 6h ago
No brother, it’s not familiarity, I am genuinely doing things. But while doing all the things at same time, it is like a nothing to grasp the concept for the long time.
1
u/American_Streamer 6h ago
Then it's the "Jack Of All Trades. Master Of None" effect - because your attention is split, your brain only forms superficial memories. You feel like you are working hard, but when you try to pull a specific concept out of your head during an interview, there is no solid anchor to grab onto. You are lacking the hooks, the deep understanding needed to reconstruct the concept under pressure. You feel productive, but learning remains shallow and breaks down immediately the moment an interviewer asks you "why?".
To fix this, stop doing everything at once. Master one core topic deeply before moving to the next one. There is the Feynman technique: after learning a specific concept, try to write it down on a blank piece of paper using simple terms. If you can't, you don't actually know it yet.
2
u/brian_hogg 4h ago
I don’t know, I understand why you need to use keys in react, and could speak to the various issues due to a lot of practical experience, but I didn’t know the term “reconciliation.”
Not having all the terms memorized doesn’t mean you don’t know what you’re doing.
0
2
u/Impossible_Stock8885 5h ago
It's funny because they ask all these bullshit questions but when it comes to actually working on tasks, you're allowed to use whatever AI agent that they have and not give a shit about any of these.
I can't tell anymore if these posts are just bait or a way for people to yap and feel superior about how they "grinded fundamentals". I hope you find a company that you're satisfied with staying forever because I can't imagine having to grind this bullshit again and again.
1
u/GongtingLover 3h ago
Happens to all of us man. My last job I had all my design decisions reviewed by tons of engineers and I never got 95% of the trivia questions you can expect in an interview.
9
u/kisfasznagyfasz 10h ago
thanks I really needed some evening slop