Member-only story
How to build coding interviews that sell your job: 3 easy steps.
Interviews are an amazing way to not only evaluate talent, but also to genuinely sell the role that you are hiring for right now. Too many companies shoot themselves in the foot by creating overly complex interview questions that have no relevance to the actual job. What do I mean? Well, I’ve seen a lot of teams choose recursion questions (example), not because they are relevant to the job, but because they “tease the brain” and require a “higher level of thinking.” I’m going to call BS. I assume it is in there because you were googling coding interview questions or remembered that your failed Google or Amazon interviewer made you solve it. So, now you are making every poor schmuck you interview go through the same BS that you despised in the past.
In a previous article about preparing for coding interviews, someone commented:
“You left off the most important part: trying to think while someone is watching, sniffing and fidgeting and making misleading suggestions. I can’t think with someone looking over my shoulder.
And the questions. I haven’t worked with a linked list in 20 years and the only time I’ve worked with binary trees is in interviews. When I develop algorithms it’s over hours or days and away from the computer.
And “can you make it run faster?”…
