Front-end developer phone screen questions: the stack in one pass, a shipped-screen walkthrough, the accessibility standard and pay fit

A front-end developer phone screen is a 20 to 30 minute recruiter call that checks whether the candidate has built and shipped what the seat needs before an engineer spends an hour on a technical round. Confirm the must-have framework and language in production in the last two years, the kind of product (marketing site, single-page app, design system, storefront) and the working pattern. Then take their recent stack in one pass, walk through one screen they shipped (what it did, how it worked with a keyboard, what was slow and how they knew), confirm which accessibility standard the seat works to, and close with motivation and pay expectations. Rules and standards below are dated as of November 2026.

This page is the first-call version. The deeper bank, with state management, cross-browser bugs, bundle size and code review questions, is in front-end developer screening questions; the general method for any engineer, including the ownership ladder, is in software engineer phone screen questions; the full loop is in the interview guide for software engineers. If you are not technical yourself, read how to interview for technical roles as a non-technical recruiter first.

What do you need from the hiring manager before the call?

How should a 25-minute front-end developer phone screen run?

1. Opening (1 to 2 minutes). Who you are, the product and team in two sentences, the length of the call, and your consent line if you record.
2. Knockouts (4 minutes). Framework and language in production, product type, location and hours, work authorization.
3. The stack in one pass (4 minutes). Their last two jobs, in a fixed order.
4. Shipped-screen walkthrough (7 minutes). One screen, three prompts.
5. Accessibility and assessment fit (3 minutes). The standard the seat needs, the process ahead.
6. Motivation and pay expectations (4 minutes). Why now, what they need.
7. Their questions and the next step (2 minutes). Consent to submit, interview times.

The timings are a planning example. If a knockout fails, say so kindly and end the call or redirect.

Which knockout questions come first?

The authorization wording follows the Justice Department's Immigrant and Employee Rights Section FAQ, which says an employer may generally ask whether applicants have the legal right to work in the United States and whether they will need visa sponsorship (as of November 2026).

How do you get the stack in one pass?

Ask once, for the last two jobs, in a fixed order, and write the answers down as said: "For each of your last two jobs, what framework and version, what language, how were pages rendered, how did the app handle state and data, how did you style it, what did you test with, and was there a design system?" People who did the work answer in seconds; people who sat next to it answer in categories.

Three checks you can run without judging the code:

• Versions and dates. "Which version, and did you upgrade it?" Someone who led or survived a major upgrade remembers it.
• Theirs or the team's. "Who chose that approach?" is enough to hear whether they decided, used or just watched.
• Gaps said plainly. "We had almost no tests" is a better sign than a perfect list that matches the job ad word for word.

How do you run a shipped-screen walkthrough?

Ask before the call for one live page or screen they built, or, if it sits behind a login or an NDA, for a description of it. Then use the same three prompts for everyone. You are not judging the code; you are hearing whether they owned the screen in production.

1. "What does this screen do, who uses it, and what part of it was yours?" Good: a user and a task, then their part, separated from the team's. Weak: a list of libraries.
2. "If I used it with only a keyboard, or with a screen reader, what would happen?" Good: focus order, labels, what they tested by hand and one problem they fixed. Weak: "We ran an automated checker" and nothing else.
3. "What was the slowest moment on that screen, and how did you know?" Good: a metric, how they measured it and what changed. Weak: "It felt fast."

For the third prompt, Google's web.dev guidance gives the answer key: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads, segmented across mobile and desktop (as of November 2026). INP replaced First Input Delay as a Core Web Vital in 2024. A candidate who names one of these and a before-and-after has worked on performance; one who only names a lab score may not have.

Which accessibility standard does the seat need?

Ask the hiring manager, then ask the candidate which standard their last product targeted. Three standards come up most, as of November 2026:

A good answer names a version and level and something they did to meet it: "We worked to 2.1 AA; I rebuilt our date picker because it trapped keyboard focus." A weak one names the acronym only. The screening bank has the follow-up questions on custom components and testing; the same standards matter for designers, covered in UX designer phone screen questions.

How do you ask about AI coding tools and the assessment?

Give every candidate the same task and the same rule. How to score a take-home is in how to evaluate a take-home assignment, and how to check that the candidate can explain their own submission is in how to verify take-home assignment authorship.

How do you test motivation on a front-end developer phone screen?

How do you ask about pay without asking salary history?

Many states and cities bar employers and their agents from asking about current or past pay, as of November 2026; the list is in salary history ban states. Ask what the candidate needs for this seat, in the employment type the seat offers.

If the candidate volunteers a number, keep it out of your notes and the submittal and record the expectation instead. This is general information, not legal advice; check the law where the job is located.

When should you advance a front-end developer?

An example rule to agree with the hiring manager: advance when every knockout passes, stack match and ownership score at least 2, and two other areas score 3. Hold when one fact, such as how much server-side work they did, needs a question from an engineer. Decline when a knockout fails. Once hired, the 30-60-90 day plan for software engineers can be adapted for the first months.

What should you not ask a front-end developer on a phone screen?

The EEOC says pre-employment inquiries should be limited to what is needed to judge whether someone is qualified, that questions which reveal race, sex, national origin, age or religion may be used as evidence of intent to discriminate, and that employers may not ask about disability before an offer.

The full list is in illegal interview questions. For the design side of the same team, see graphic designer phone screen questions. If you take the screen through your computer, Interview Signal keeps the framework and assessment questions pinned until you ask them and writes the stack and the walkthrough answers into the scorecard with the candidate's own words beside them, with no bot in the call.