Skip to content
CareersAble

Interview questions

Frontend Developer interview questions

Frontend Developer interview questions for each round: frameworks, performance and accessibility, with what each interviewer is scoring.

Answer one Frontend Developer question out loud today and time yourself.

All software engineering questions

How Frontend Developer interviews are scored

Frontend interviews score whether you think about the user as well as the code. Mentioning accessibility, loading states and slow connections without being asked separates you from candidates who only talk about frameworks.

What hiring managers check in Frontend Developer interviews

  • Whether you build loading, empty and error states without being asked, because real users hit them every day.
  • Whether you measure performance with a tool and a number, not by how fast it feels on your laptop.
  • Whether you raise accessibility yourself, which they watch for in the live build rather than ask about.

Pick the check you are weakest on and prepare one Frontend Developer story for it tonight.

Questions Frontend Developer candidates get

On top of the questions every role in this field is asked, these come up for this title in particular.

Screening interview questions

Usually a recruiter or talent partner, 15 to 30 minutes, often by phone or video.

  1. Which frontend framework have you used most, and how big was the app?
  2. Have you worked from a design system or built one?
  3. Do you use TypeScript day to day, and how strict is your setup?
  4. Which browsers and devices did your last app have to support?
What this round scores

Hiring manager interview questions

The person you would report to, 45 to 60 minutes, sometimes with a team member.

  1. Tell me about a page you made faster and how you measured the difference.
  2. How do you make sure a component works with a keyboard and a screen reader?
  3. Tell me about a time a design could not be built as drawn. What did you do?
  4. How do you test UI code, and which bugs still get through?
What this round scores

Final round questions

Senior leaders, a panel, or a case task, 60 minutes to half a day.

  1. Build a searchable list component that handles slow and failed requests.
  2. Walk me through how you would manage state in a large single-page app.
  3. Here is a page that takes six seconds to load on mobile. Where do you start?
  4. Review this pull request for a form component and tell us what you would change.
What this round scores

Plus the software engineering questions every round asks

  • Walk me through your engineering background in two minutes.
  • What languages and frameworks have you used most in the last two years?
  • What kind of team and codebase are you working in now?
  • Tell me about a technical project you are proud of and your part in it.
  • Tell me about a production incident you helped fix.
  • Describe a time you disagreed with a technical decision.
  • Design a URL shortener that handles millions of requests a day.
  • How would you find out why an API got slow last week?
  • Walk me through the trade-offs of the architecture in your current system.
See all 24 software engineering questions, with scored example answers

Get the software engineering question pack by email

Every question on this page in one email, grouped by round. Plus three things that are not on the page:

  • 12 more questions, 4 per round, that only go out by email
  • What a strong answer covers in each round, to check yourself against
  • A 7-day prep plan that matches where you are in your search
Where are you in your search?

We email you the pack once. We never sell or share your details. Privacy policy

Hiring manager interview

One question, three answers, three scores

The same question answered three ways, scored the way an interviewer would mark it.

“Tell me about a page you made faster and how you measured the difference.”

Weak28
“I'm always optimising my code. I use lazy loading and keep components small so things stay fast.”
Why: A list of techniques with no page, no measurement and no result.
OK58
“Our product page was slow on mobile, so I compressed the images and lazy loaded the reviews section. Lighthouse scores went up quite a bit.”
Why: A real page and a real fix, but no starting number and no link to what users experienced.
Strong86
“Our product page had a largest contentful paint of 4.8 seconds on mid-range Android. I found the hero image was 1.2 MB and the reviews widget blocked rendering, so I served responsive images and deferred the widget. LCP dropped to 2.1 seconds, and the team saw mobile add-to-cart lift over the next month.”
Why: A measured before and after, a diagnosed cause and a business result tied to the change.

Example scores on the 0 to 100 scale CareersAble uses. Your own answer gets its own score.

Reading the questions is not the same as answering them.

CareersAble writes the questions your actual job ad will ask, records your answers, scores each one three times and tells you plainly what to fix.

Free to start. No card needed.