3 ms·
Personality, communication skills, etc., all matter. A lot. There's more to being a good software engineer than knowing how to code well. You have to be able to
by jsatk 11y ago
Personality, communication skills, etc., all matter. A lot. There's more to being a good software engineer than knowing how to code well. You have to be able to back up your ideas, convince others of your ideas, hear others view points and objections to your ideas, etc. Take home projects are great, but they're not a substitute for a face-to-face interview.
- duderific 11y agoWe do both: - A take-home project that takes a few hours - We assess their code; if it looks good, we bring them in for a few more interviews, both tech and non-tech - If it doesn't look good, we move on to the next candidate
- asadlionpk 11y agoI think doing both is the way to go for now and this tool helps you do both.
- orless 11y agoOMG. A few more interviews? Can't you handle everything in one or two interviews? Seriously, from my (quite senior) point of view - if you've seen my CV, done research on me (StackOverflow, GitHub etc.), seen my code from the take-home project, did a technical and non-technical interview and still unsure if I'm a match or not, I'd really doubt your competence. I must be really so exceptionally interested in the position to do a "few more interviews".
- bm1362 11y agoI think this is ideal - as long as the technical interviews are about the project itself. Reading these responses, I get that a lot of people here are in the role of interviewer and seem to forget what it's like to be trying to get in the door. You cram as much algorithm knowledge, language trivia so you can be prepared for 4-5 pet interview questions that could be anything. It truly sucks, is a huge time investment for the prospective employee and most of the time it's not clear what the Nth interviewer is looking for when he asks you your favorite network protocol.
- meggar 11y agoThen be specific and put "Extroverted" in your job description.