Thinking about coding interview questions or take home assignments. We all come up with our own that we use to evaluate all our candidates. And it's a great tool for figuring out a candidate's capability to deliver working software.
Then I came across my friend's Tweet:
qian 🌺Very 😒 at companies that just expect you to contribute two technical tests' worth without even a HR / screening call for the candidate to know about the company
Interviewing is a two way street FFS!!!10:37 AM - 22 Jun 2020
I know of many job seekers who hunker down over weekends to do multiple coding assignments with fixed deadlines. Perhaps we are expecting too much or going overboard with our interview questions.
Other than take home assignments, we also do live coding interviews to further evaluate a candidate's culture fit - how do they handle stressful situations, how do they troubleshoot a problem, can the candidate communicate well or articulate the technical decisions they make. These are good for gauging whether a candidate could be a suitable co-worker. So the culture aspect is quite specific to your company culture and what you look out for in a suitable candidate.
What i'm curious to know is if there can be a set of coding assignments that candidates can use to show that they know their shit. Not as formal as a certification, but more of a do you have a baseline competency for the role we are looking for.
Sure, we can use HackerRank or something similar for this as a shared reference point for the candidate's capabilities. But those coding problems tend to incentivise a certain kind of behaviour. Coding for performance in a coding puzzle is not the same as writing well designed & maintainable code.
Perhaps we should let candidates who don't make our cut to just bring their coding assessment to show the next company? I mean, you can say its your company's intellectual property... and it might encourage plagiarism... or give future candidates an unfair advantage if they know your coding test.
However, the flip side is this might actually accelerate the interview process. If the candidate is good, they wouldn't just copy pasta, they would do something properly (depending on the type of company you are in, copy pasta may or may not be a good thing).
Also, this may also ease the stress level of newbie coders who are bogged down with so many coding interview assignments from the companies they interview at.
What do you think?