Code Style Matters in a Take-Home Interview

Let’s get this out of the way to start: probably not just software engineering interviews, but all interviews are in some way flawed. They can overemphasize unimportant aspects during the job and underemphasize aspects that are very important on the job but might be harder to capture in an interview. The task is a bit of an impossible one: given a few hours, measure if a candidate will be capable of performing a job for a minimum of 40 hours a week, for 50 weeks a year. You’re supposed to gauge someone’s future performance with what amounts to less than one percent of the time they’d work for you for a year. The best interviews are like internships, where you can gauge how someone would perform on the job. But not everyone wants an internship (or is offering one). So, given that these interviews are flawed, are they at all defensible? Yes, we have to try and hire people somehow instead of just inviting friends and family to work for us. <a href="https://betterprogramming.pub/why-code-style-matters-in-a-take-home-interview-problem-c53623e4d2a2">Website</a>