One horror story is when the interviewer was constantly interrupting the candidate. The candidate was trying to explain their solution to a coding problem, but the interviewer kept cutting in with their own thoughts, not letting the candidate fully express themselves. This made the candidate very nervous and they couldn't perform at their best.
One common type is the unprepared interviewer. They might not have a clear understanding of the skills they are supposed to test, so they ask irrelevant questions or misinterpret the candidate's answers. Another is the overly strict time limit. For example, being given a very complex problem but only a few minutes to solve it. It doesn't give the candidate enough time to think and code properly.
One horror story is when a student was asked a really difficult question about a complex theory right at the start. The student froze and couldn't answer at all. It threw off their whole interview and they felt so embarrassed.
There was this case where an interviewee was in the middle of answering a question about market trends. Suddenly, one of the interviewers received a phone call and started chatting loudly. The interviewee was left hanging there, not knowing whether to continue or wait. When the interviewer finally finished the call, they just asked the next question without any apology, completely throwing the interviewee off balance.
There was a team working on a big project. One programmer was trying to debug a function that was supposed to calculate the area of different shapes. He was getting really strange results for the triangle area calculation. After hours of looking through the code, he realized he had mixed up the base and the height variables in the formula. It was really funny when he told the team and they all had a chuckle over such a basic mistake.
One horror story is when a developer made a small change in a critical function without proper testing. It led to a cascade of errors in the whole system. Hours were spent debugging to find that one innocent - looking line of code was the culprit.
Another threading horror is starvation. This occurs when a thread is continuously deprived of the resources it needs to run. For instance, in a system with a priority - based scheduler, if high - priority threads keep getting scheduled all the time, low - priority threads may starve. So, a thread that is supposed to perform an important background task may never get a chance to execute.
I knew someone who went to an interview and the room was freezing cold. The interviewer didn't seem to care and just carried on. To make it worse, they were very rude and cut off the interviewee mid - answer multiple times. It was a horrible experience for my friend. They felt so disrespected and didn't get the job in the end.
There was this situation where the HR interviewer was asking inappropriate personal questions. Things like relationship status in a way that made the interviewee uncomfortable. This is not only unprofessional but also made the whole interview seem more like an interrogation than a job interview.
One horror story is when an interviewer asked a very personal and inappropriate question about a celebrity's family member's health issues. The celebrity was visibly uncomfortable and the interview took a really awkward turn.
A frequently occurring horror story is related to dependencies. Let's say you build a project relying on a particular library. Then, that library gets updated and the new version has some breaking changes. Your code that was working fine before suddenly stops working. You have to either find a way to make your code compatible with the new version or roll back to the old version, which might have security risks. It's a real headache especially when you have a large and complex project.