An interview is just a test. Like any tests there are false positives and false negatives. There is a trade off between having more false positives/negatives and generally when it comes to hiring, a false positive is much more expensive than a false negative so many interview processes will end up rejecting good developers.
An interview can’t tell the company whether or not you are a good developer or a bad one. It can only say you can demonstrate certain skills to a certain level under interview conditions which means you are pretty likely to be a good developer.
It’s tough when you get rejections but because of the above factors, unfortunately it’s not enough to be a good developer to pass interviews a lot of the time. You also have to be good at interviewing. The good news is like any skill it can be practiced and if you’re already a good developer it shouldn’t really take much effort to become good at interviewing but it does require practice.
adj16@lemmy.world 1 year ago
Painful read, as it resonates with me. I think I’m pretty hot shit but was humbled by the interview processes a few years back.
But in unrelated thoughts, found myself laughing at this reply in the comments:
This reminds me about the time I almost got fired. I was at work, playing an intense round of table tennis, when the CEO burst out of his office. “This is it everybody!” he yelled, running over to the Big Wheel. He gave the wheel a spin, and then hurriedly explained “I’ve got a linked list and I need to know if it contains a cycle!”
Sigmatics@lemmy.ca 1 year ago
Coding a linked list in C in Notepad and only one syntax error? This guy’s worth the money!
nitefox@sh.itjust.works [bot] 1 year ago
This is fucking awesome
HowManyNimons@lemmy.world 1 year ago
What TF did I just read? You live in Hell.