This doesnt' happen to me after I grinded leetcode for a couple of months.
you are anxious if you feel unprepared.
31–40 of 1001 posts
This doesnt' happen to me after I grinded leetcode for a couple of months.
you are anxious if you feel unprepared.
> In short, the findings suggest that companies are missing out on really good programmers because those programmers aren’t good at writing on a whiteboard and explaining their work out loud while coding. In most of my programming jobs, explaining your work was most of the job and writing code was less important. The whiteboard environment is a bit unnatural but I don’t want to hire someone who gets the right answer…
And having skills retained under pressure is actually a valuable trait in this industry. And at least at desirable companies, the process is designed to minimize false positive, it doesn't care that much about false negatives. This is by design.
My guess would be that they filter out orders of magnitude more people with poor resume-writing skills or that didn't go to the right school.
Although I do agree that interviews that you can/must practice for are silly and there's a lot oof that around.
It was made the clearest to me when I interviewed a colleague who had left to another company and two years later was interviewing to return. I knew he knew everything and had the skills for the job because, well, I know him, I’d worked with him before. He’d done this very job previously. Yet he still performed terribly in the interview and (rightly or wrongly) I had to base my evaluation on my knowledge of him rathe…
Having multiple respectable people that can vouch for you is a much better performance predictor than a 1-day interview. Same reason that recommendation letters are more important than GRE tests for the ones seeking PhD studies.
In reality human to human interactions, sometimes stressful, are part of the job. Customer & PM requirements, technical debates, giving feedback, explaining your technical solutions, etc. are common.
Maybe part of the problem is the education that does not prepare people to reality of the job.
Note: I do realize that SWE interviews suck, and I'm not trying to defend them. Just making comment on the study.
Having said that communication and interpersonal skills are big part of most jobs even in tech. We hardly develop software in isolation these days.
I don’t know about other industries, but in Tech there are some really inexperienced interviewers out there, who’re impulsive and lacks discipline in conducting objective and meaningful assessment.
Seeing how they deal with a stressful situation is an integral part of the interview in my opinion, and I imagine it is a feature for any IT role where that is the case. Standard dev roles, or other roles where time-based stresses aren't as prevalent, may be different.
Only yesterday I had a candidate bow out 10 minutes into the whiteboarding exercise, which is probably best for both the individual and the company if that kind of situation is untenable for them.
Interviewers need to do their due diligence. Coding tests can have their place when interviewing for certain kinds of positions, especially for new grads and entry level positions. In the end nothing can replace checking references and looking into a person's work experience.
There is no algorithms and data structure whiteboarding test that can differentiate between a junior and a senior developer. Being senior is a product of acquired wisdom, not just skill. And in fact senior devs can easily bomb out a whiteboarding test because we're further from university CS experience.