Engineering and IT · Interview questions

Frontend Developer interview questions

These questions check whether a candidate can build screens that are fast, accessible and consistent, not only screens that match a design. Ask every candidate the same questions in the same order and score each answer against the strong answer notes.

The questions

Ask every candidate the same questions in the same order, and score each answer against the notes before you talk it over with the panel.

  1. Tell me about a page you made noticeably faster. What was slow, how did you find out, and what changed?

    What it tests
    Page speed outcome.
    A strong answer
    They describe measuring first, for example with Lighthouse or the browser performance panel. They name a specific cause such as oversized images or a large JavaScript bundle and give before and after figures.
    Watch for
    Guessing at fixes without measuring before or after.
  2. Here is a short React component that renders a list of 2,000 orders and re-fetches them every time a filter changes. Talk me through what you would change and why.

    What it tests
    Practical code review and performance.
    A strong answer
    They notice the unnecessary re-fetching and suggest debouncing or caching the request. They suggest pagination or list virtualisation for the long list and mention stable keys.
    Watch for
    Rewriting everything without explaining which problem each change solves.
  3. Describe a reusable component you built that other people used. How did you decide what it should and should not do?

    What it tests
    Component library outcome.
    A strong answer
    They explain how they kept the component small and predictable, with clear props for states like loading and error. They mention documenting it and handling requests to add special cases.
    Watch for
    A component with dozens of flags that tries to cover every possible screen.
  4. Walk me through how you would check that a checkout form works for someone using only a keyboard or a screen reader.

    What it tests
    Accessibility outcome.
    A strong answer
    They tab through the form, check visible focus and logical order, and confirm every field has a label. They mention error messages that are announced and testing with a real screen reader such as NVDA or VoiceOver.
    Watch for
    Treating accessibility as only adding alt text to images.
  5. A customer reports that the Pay button is hidden behind the footer on their phone, but it looks fine on your laptop. How do you work out what is happening?

    What it tests
    Debugging visual bugs.
    A strong answer
    They ask for the device, browser and a screenshot, then reproduce it with device emulation or a real phone. They consider viewport height issues, fixed positioning and on-screen keyboards, and add a check so it does not come back.
    Watch for
    Closing the report because it cannot be reproduced on their own machine.
  6. Tell me about a time a design you were given would not work well on small screens. What did you do?

    What it tests
    Working with design, responsive layout.
    A strong answer
    They raised it early with the designer, showed the problem on a real device and proposed an alternative. The final result kept the design intent and worked on mobile.
    Watch for
    Quietly building something different without telling the designer.
  7. How do you decide what to test automatically on the frontend, and what to leave to a manual check?

    What it tests
    Reducing visual and layout bugs.
    A strong answer
    They test the flows that would cost the business most if broken, such as sign-up and payment, with end-to-end tests. They keep unit tests for logic and accept manual checks for low-risk visual details.
    Watch for
    Either no tests at all or a plan to test every pixel.
  8. The backend returns errors as a plain 500 with no message. Users see a blank screen. What would you do this week, and what would you ask the backend team for?

    What it tests
    Collaboration with backend, error handling.
    A strong answer
    They add a clear error state and a retry option in the interface straight away. They agree a consistent error format with the backend team so the interface can show useful messages.
    Watch for
    Blaming the backend and leaving users with a blank screen.

New to structured interviews? Read how to run structured interviews and how to build an interview scorecard.

Start from the job description

These questions follow the first-year outcomes in the matching template.

Frontend Developer job description template

Similar roles

Your next hire, start to finish, in one place.

Free workspace. No card. Full scoring free for 7 days.