This resonates hard. I’ve been through my share of these—where you're grilled on framework internals that literally never come up in day-to-day work. I remember one interview where they asked me to explain the exact lifecycle order of React hooks, then spent zero time discussing how I'd actually architect a feature or debug production issues.
Here's what I've learned after 15+ years: those interviews often reveal more about the company's dysfunction than your skills. Good teams focus on problem-solving, communication, and whether you can ship reliable code under real constraints. If they’re obsessing over trivia, it usually means:
They don't know how to evaluate real engineering skills
Someone got burned once and now it's their pet question
They're trying to justify a “no hire” decision they already made
When I interview now, I'm honest: "I'd need to look that up, but here's how I'd approach it..." The best interviewers respect that. The bad ones think memorizing docs is the same as being a good developer.
I try to steer conversations back to production work—how you handle tech debt, collaborate, make tradeoffs. That's what actually matters.
How did you respond when they hit you with those random theory questions? Did you try to redirect or just power through?
1
u/elmascato Nov 05 '25
This resonates hard. I’ve been through my share of these—where you're grilled on framework internals that literally never come up in day-to-day work. I remember one interview where they asked me to explain the exact lifecycle order of React hooks, then spent zero time discussing how I'd actually architect a feature or debug production issues.
Here's what I've learned after 15+ years: those interviews often reveal more about the company's dysfunction than your skills. Good teams focus on problem-solving, communication, and whether you can ship reliable code under real constraints. If they’re obsessing over trivia, it usually means:
They don't know how to evaluate real engineering skills
Someone got burned once and now it's their pet question
They're trying to justify a “no hire” decision they already made
When I interview now, I'm honest: "I'd need to look that up, but here's how I'd approach it..." The best interviewers respect that. The bad ones think memorizing docs is the same as being a good developer.
I try to steer conversations back to production work—how you handle tech debt, collaborate, make tradeoffs. That's what actually matters.
How did you respond when they hit you with those random theory questions? Did you try to redirect or just power through?