DEV Community

I Failed a Technical Interview After 10 Years. Here's the Feedback.

Renato Silva on October 27, 2026

I have more than 10 years in software engineering. I've migrated monoliths to .NET Core, designed APIs, tuned SQL Server queries in production, and...
Collapse
 
christopher_jakob_acda8fa profile image
Christopher Jakob •

"Doing is not the same as explaining" is so true, and I think there's another layer to it. In an interview your body is already in a higher alert state, and when that happens your brain grabs whatever it trusts most, which for you is the stories from real work, not the textbook words. That's not you lacking the knowledge, it's the alarm going off and pulling you toward what feels safe. Saying the definitions out loud before interviews is a great fix because it gives your brain a new path it already knows is safe, so it stops reaching for the old one under pressure. Respect for sharing the email and owning it after the first defensive reaction. Most people stay stuck in that first day.

Collapse
 
renato_silva_71eef0fc385f profile image
Renato Silva •

Hi @christopher_jakob_acda8fa, it's exactly as you said, during a interview you have average 20min to convince someone that you are good at what you do. I wanted to share this because in a current situation of the IT industry people are afraid of what is coming and at same time trying to improve themselves. Thank you for the comment.

Collapse
 
christopher_jakob_acda8fa profile image
Christopher Jakob •

Yeah 20 minutes is nothing, and it's even less when half of it goes to your nerves settling down. And you're right about the timing, a lot of people are scared right now, so posts like yours help more than you think. It shows someone with 10 years in still gets rattled and can still learn from it. Good luck on the next one, you'll crush it.

Thread Thread
 
renato_silva_71eef0fc385f profile image
Renato Silva •

Hi @christopher_jakob_acda8fa, absolutely. And yes the main idea is to show that we can always improve, even though after some bad or sad results.

Collapse
 
waccha21 profile image
Federico •

"The interviewer can't see your reflexes" is spot on. Ten years of doing turns concepts into muscle memory, and interviews ask you to turn them back into words on the spot. Going from defensive to honest in a day, then writing it up publicly, is more senior than any definition of SOLID. Good luck with the next one.

Collapse
 
renato_silva_71eef0fc385f profile image
Renato Silva •

Hi @waccha21, thank you for the comment. I just saw an opportunity to share something that almost sure happens more than it seems. All of us tend to be our own bubble, I know that I'm not the prime software engineer but at same time I know that I am able to do something. Thank you again.

Collapse
 
waccha21 profile image
Federico •

Ha, the bubble thing is real. Knowing you can do the work without needing to be the best engineer in the room is a pretty good place to interview from. Hope the next one goes your way.

Thread Thread
 
renato_silva_71eef0fc385f profile image
Renato Silva •

Hi @waccha21, thank you for the comment. And also even if I get to the position where I see myself as a prime engineer I still would need to understand that as the software engineering field is huge, I would be being naive thinking I am the best. Everyone has something to add and everyone has something to teach.

Thread Thread
 
waccha21 profile image
Federico •

Well put, Renato. That attitude will come through in the next interview as much as the fundamentals will. Good luck with it.

Thread Thread
 
renato_silva_71eef0fc385f profile image
Renato Silva •

Hi @waccha21, thank you!!!

Collapse
 
arslan_ah profile image
Arslan Ahmad •

Respect for posting this publicly. Most people bury their rejections. From my years as a hiring manager: this happens to experienced engineers constantly, and it's rarely about ability. You've been using DI and indexes correctly for a decade, but explaining them crisply on demand is a separate skill, and it decays when you don't exercise it. The refresher you wrote is exactly the right response. Teaching the fundamentals back to yourself is the fastest way to make them articulate again.

Collapse
 
renato_silva_71eef0fc385f profile image
Renato Silva •

Hi @arslan_ah, thank you for the comment and 100% agree. I confess that was a sock to listen from the feedback that I had failed to explain something that I am sure how to do. And yes, reviewing the fundamentals is also a way to progress and innovate, if we know what works and how it works we can improve it, and if we know that do not work and why, also we can improve it.