Asking for a friend, of course...
But really. I'm not currently interviewing, but I've failed plenty of technical interviews before and I still shudder thinking of my very first one.
I bombed it.
After, I didn't know what to do. I wondered if I should just give up.
Doing poorly in a technical interview meant I wasn't cut out to be a developer. At least, that's what I believed at the time.
Fast forward to today and I know that isn't true. But I often hear aspiring developers talk about how failing technical interviews shook their confidence afterwards and made them question if they could really become devs.
So here's a question that I'd love to hear the answer to from other developers--how do you bounce back after a technical interview? What do you tell yourself? What do you do next?
One thing that's been helpul for me:
Always figure out the answer later. At the end of the interview, it seems like I'll never understand what the solution to the technical problem presented to me was. But later, when I learn as I go over it, I see that I can. That helps rebuild my confidence as I identify the knowledge gap that preventing me from understanding the problem, and I close that gap.
But I wish I would have known this sooner. That's why I created this thread.
In your experience, what should you do after you fail the technical interview to ensure that you'll learn and grow as a developer because of the experience, not in spite of it?
Single Responsibility Principle (or SRP) is one of the most important concepts in software development. The main idea of this concept is: all pieces of software must have only a single responsibility.