DEV Community

Discussion on: What would your ideal developer interview process look like?

Collapse
 
gabescarbrough profile image
gabescarbrough

I’d say it depends on the role. Nothing crazy complicated. Everyone is going to have access to Google on the job. I just like it because it gives me an opportunity to discuss a problem with the interviewer. Code tests in a text editor are totally valid too. If you just want to know if they know conditionals and loops then fizzBuzz is fine. If you think SQL is key to the job ask them to write a SELECT statement that requires a JOIN or something.

I don’t like take home tests because I want my time at home to be for me. And they almost always take longer than they tell you it will take because they can’t do it themselves without an advantage and most people wouldn’t say that it took them longer. If you have a time limit then it is even worse because I focus on how much time I have left like it’s a race.

At least in a one-on-one conversation you know the code test is going fine as long as you’re still talking to them and they are giving you good feedback. And you can ask clarifying questions which is almost as important as showing you know whatever they’re asking.