If that candidate has been bitten – gone through an issue related to concepts that were difficult and resolved them – that’s a huge plus. Been BittenĪt least one section of the interview needs to be focused on concepts like Closures, Functional Programming (pure functions), and immutability. For junior roles, it’s more about if they can explain the concepts like dispatching actions or if they’ve worked in Redux, MobX or React in prior roles. What you want to see is this person’s ability to explain why they’d choose one or the other.”Īt a senior level, look for the ability to stand up the capability on their own with the appropriate justification for the merits of their choice. “There are a lot of competing libraries that help you manage it – and which one is best can sometimes rise to the level of a religious discussion for some engineers. “There’s no one right way to do it,” says Geggatt. Their answers around communicating with APIs and pulling different datasets into the system should reflect an understanding of the complexity that’s correlated with more features in the product. Ask your candidates about strategies they’ve used in the past, libraries they’ve worked with, and why it’s important to get it right. Managing StateĪ major consideration when working with modern Javascript frameworks (like React) is dealing with state management. Jonathan Geggatt, CoderPad’s VP of Eng, takes us behind the scenes to discuss how to do exactly that. So how can you structure a Javascript-based technical interview to get the best out of your candidates and reflect well on your company? If you haven’t already, the odds are good you’ll eventually need to put candidates through their paces and see just how conversant they are in this front-end tool. There’s no question that Javascript has a major place in the canon of programming languages. So You Want to Conduct a Javascript Technical Interview?

Javascript interview questions