DEV Community

Discussion on: Why I've started asking companies about their technical interviews before proceeding with them

Collapse
 
ravavyr profile image
Ravavyr

Let me rephrase [sorry for the late response], I have my opinion when i see people's resumes and code. I might sugarcoat it and go "That looks unpolished" or as i do in my head "it's rubbish, it's crap, it sucks" and so on.

I NEVER say that to an applicant. I know words can hurt. I also know how fickle everyone is these days and how insecure and how nerve-wracking interviews can be. Saying that to someone could really break them and make them feel like crap. I don't do that.

I have however said to applicants "Your code just isn't at the skill level we require at this time". And I've had further discussions with some who then said "Well, can you tell me what I need to improve on". And i do wish them well and better luck at their next interview, but the general thing is that they need to practice more before they apply to the next one.

Some portfolios ARE utter rubbish though. eg. Missing any useful urls to ANY work at all. Any dev should at least have something online you can look at. Or how about not having an email or phone number, so we have no way to contact them? There are worse examples, and these are completely unrelated to their actual dev skills. Some people just don't take the time to make a good resume, and if they're not doing that, i don't think they'll take the time to do good work either. Perhaps that's just a horrible assumption on my part.