Let’s not forget the emotional element of these interviews where you’re being asked questions that mean very little about whether you can perform in the role. but many pretend that they are. For me the day long “technical” interview loop is a flashback to gradeshool hell. It tests my anxiety levels at least 5x more than my skillset.
It’s a common thought among my circles that interviewing is the hardest part of being a software engineer - once you’re in somewhere it’s a lot easier.
It's often the hardest part because many people think they can hit the ground running after following a Udemy programming course.
Engineers are expensive to start with and inexperienced/over-confident engineers even more so due to the potential damage on the product.
Tough interview stages like leetcode are a simple method HR can employ to establish a baseline competence.
Personally I have zero interest in grinding for months solving riddles and when interviewing I always check what the stages involved are. On numerous occasions leetcode has been dropped upon request - no harm in asking!
> It’s a common thought among my circles that interviewing is the hardest part of being a software engineer - once you’re in somewhere it’s a lot easier
I’ve heard a similar sentiment from my circles too. But lately
I’ve also met people for whom it’s the exact opposite: they can clear the first round of the interview and they fail in the subsequent design rounds (which in my opinion are a lot less challenging)
I’ve also met people who manage to get hired but are soon overwhelmed with the real work that they have to do and some even get pip’d
| It tests my anxiety levels at least 5x more than my skillset.
I'm not so convinced that these are two distinct things. I want coworkers who can maintain their level of skill under extremely hostile, stressful conditions. I'm not going impose those conditions on them, but I can't necessarily control the myriad third parties or circumstances that might.
It’s a common thought among my circles that interviewing is the hardest part of being a software engineer - once you’re in somewhere it’s a lot easier.
There needs to be something better.