This is a generalization that doesn't always ring true.
As I've gained experience, I've come to enjoy interviewing at times. Especially when I'm going into an interview where I feel quite comfortable discussing that particular domain.
If you're someone who doesn't mind social interaction and who doesn't lack confidence (for better or for worse), interviewing can be an enjoyable experience.
I doubt that I'm the only one who feels this way.
It's something about the "set and setting" of a job interview.
I'm unsurprised if there's a lucky cohort of people who just don't have this problem. Enjoy! For my part, I'm looking forward to spending more and more of my career beating the tech job interview to death with my bare hands, because I loathe it --- from both sides, as a candidate and now a hiring manager.
Death to interviews!
Agreed. What is your approach to finding good people given this phenomenon?
[1]: I'm phrasing it in this way not because I don't agree with him, but because it's new enough that I don't think it's been established as objective truth. I'm of the opinion that the pipelines are very cool and fairly effective as recruiting tools.
I've been rattled by every job interview I've had. That includes interviews for roles that I'd been courted for. It includes interviews for jobs I didn't even want, where I was interviewing mostly because a friend had asked me to. One of those interviews was for a company I actively disliked and would under no circumstance work for. I didn't sleep the night before! I did a multicast streaming media company in the late 90s and owned the router; later, I interviewed at a friend's company, got asked how to implement Towers of Hanoi without recursion, and for the rest of the day forgot everything I knew about routing protocols --- despite having spent the preceding two years doing nothing but implementing them.
Job interviews suck. They're hostile processes that involve complete strangers not just sitting in judgement of you, but also working under the delusion that their job is to break you so they can avoid hiring "B players".
I basically interview people for a living now and pay pretty close attention to this, and have come to the following conclusion: there is zero correlation between how people comport themselves in job interviews and their ability to do a job.
My best advice is, know the stuff you know. If you want to bone up on algorithms and data structures, don't cram. Implement them in your most comfortable language and watch them work, and go to the interview knowing not that you can recite them from memory, but that push-to-shove you can in fact throw down and get them working. Then just answer questions honestly.
The hardest interviews you take might be for the worst, most dysfunctional teams; a mean (or even just wicked) streak in interviewing candidates is a sign of broken teams, not weak candidates.
Good luck!