DEV Community

Discussion on: If you could change one thing about the technical interview process, what would it be?

Collapse
 
kpollich profile image
Kyle Pollich

No more riddles and algorithm puzzles. Focus on candidate experience, get their thoughts on benefits/drawbacks of different technologies. Focus on getting a sense for how a given candidate approaches problems. Systems engineering problems are usually good too, and I'd like to see more of those. Things like "how would you go about architecting an application to do XYZ?" and going off from there work well.

Collapse
 
vbordo profile image
Victor Bordo • Edited

Yeah for sure. Those puzzles always feel so trivial. Curious to know how junior devs will respond to those questions. It's definitely a more common route in a senior dev or DevOps engineer interview. Have you had good experiences with systems engineering implementation scenarios? Add a feature to a codebase you're familiar with, etc?

Collapse
 
kpollich profile image
Kyle Pollich

At a previous job we used to walk through "How would you tackle the task of creating a class registration system for a local college?" It went well for mid level engineers -> seniors, but I never really saw a junior tackle that particular problem. Maybe something a bit more watered down would work better.