Quote:
Originally Posted by humfrz
"Panic attack" during an interview?
How did that surface (what caused it)?
 |
Partly I'm out of practice. I haven't practiced the type of coding problem he was asking me to do since I interviewed for the current job.
I had figured when they said coding questions for this internal transfer opportunity, it'd be more like discussing code I've written here for my current team or work on a relevant problem for this new team. Not just a straight-up typical challenge problem that's asked of people interviewing to every new job.
So while I'd seen this problem before, I hadn't practiced it recently and the pattern recognition for thinking through how to solve it was rusty. Some people can still solve stuff like that on the spot, but I got anxious.
Also, in general when it comes to these types of interviews I've just always felt fairly insecure and unskilled because they're usually styled at one type of vague, very unrelated problem solving on the spot, which I'm not good at. Rather than the kind of problem solving that is actually relevant to the job itself.
The last time I interviewed when I got my current job back in Dec. 2019, it was a full day on-site with 4 one hour segments, each with a different person. Did fine with 3/4 of them, panicked on one.
I'm mostly out of practice, which makes the fear/anxiety problem worse. And it's difficult to spend time outside of work practicing because we're in crunch mode on some projects.
Most people you ask would say the typical software engineer interviewing process is incredibly awful, but there's not really a better way either.
The sad thing about this scenario is just that since I already went through that process, I was hoping/expecting that with this being internal, my earlier interviews would have counted and these would be more relevant to the role itself, which they clearly are not.