Skip to content
uxerhub

Frontend developer interview questions beyond the code

By Sergio Gualda · 4 min read · Updated

Use a coding test to see whether a frontend developer can build, and use the interview to learn what they'd choose to build. The questions below cover the second part: how they treat a design with gaps, when they push back and what they do about failure states. Plenty of guides cover framework trivia, so these don't.

Questions about what gets built

Listen for whether they think about the person using it, as well as the ticket.

  • Tell me about a design you changed before building it. What did you notice?
  • A design arrives with no empty, loading or error states. What do you do?
  • When did you talk a team out of building something?

Questions about cost and quality

Strong answers give a specific line they held or gave up, and why.

  • What's something you shipped that you weren't happy with? Why did you ship it?
  • A deadline moves up by a week. How do you decide what goes?
  • How do you explain to a designer that their request costs far more than it looks?
  • When is it right to add a dependency, and when isn't it?

Questions about failure

Everyone has a production story, and how they tell it says a lot.

  • Tell me about a bug users found before you did. What changed afterwards?
  • What happens in your code when one part of a page fails and the rest doesn't?
  • How do you find out whether real users on slow devices are having a bad time?

Frequently asked

Should I still ask about JavaScript fundamentals?
Yes, if you don't have a coding test covering them. If you do, don't spend interview time repeating it. An hour with a senior engineer is expensive for both of you.
How do I interview a frontend developer if I'm not technical?
Ask a trusted engineer to cover the code, and take these questions yourself. Most don't need technical knowledge to judge, only attention to whether the answers are specific.