Front End Web Developer Interview Questions
Free front end web developer interview questions for small business owners: 6 sets, accessibility and speed checks, and a scorecard. Download as DOCX.
The first front end developer I ever interviewed ran circles around me. He talked about hydration and bundle splitting for twenty minutes, I nodded, and I hired him. Three months later our checkout still did not work on an iPhone and nobody could deploy anything without him. The problem was not his skill. It was that I had no way to tell his answers apart from a confident guess, so I graded fluency instead of evidence.
That is the actual problem for most owners hiring this role. Front end work is highly visible and easy to talk about, which makes it unusually easy to interview badly. The fix is not learning to code. It is asking questions whose answers you can verify: open the live site, view it on your phone, ask what they personally built. Pair these sets with the front end developer job description you posted.
At FirstHR, we build for owners and managers who run these interviews themselves, without an engineering manager to lean on. These six sets cover the role the way a small business actually hires for it, and every question comes with a note on what a good answer sounds like.
- Sign the offer letter
- Sign the employee handbook
- Workplace Safety course
What a Front End Web Developer Actually Does
A front end web developer builds everything the customer sees and touches in the browser: layout, responsiveness, page speed, forms, animation, and accessibility. The work is usually HTML, CSS, and JavaScript plus a framework, and it ends where the server begins. Everything the customer never sees, server code, databases, integrations, and security, belongs to the back end.
That boundary matters before you write a single question, because it decides which half of the risk you are hiring against. A marketing site, a landing page, or a storefront interface is mostly front end work. A booking system or a customer portal leans back end. If one person will own both, you are hiring full stack, and the broader web developer interview questions kit covers that shape better than this one does.
| Responsibility | Front End Developer | Back End Developer | Web Designer |
|---|---|---|---|
| Builds the interface customers touch | |||
| Owns responsiveness and page speed | |||
| Makes the interface keyboard accessible | |||
| Writes server code and designs the data | |||
| Produces the visual design in the first place |
Confusing a front end developer with a web designer is the most common posting mistake I see. A designer decides how it should look. A front end developer makes it work in a browser, on a phone, for a keyboard user, in under two seconds. Some people do both well, but you should ask for evidence of each rather than assuming the pair comes together.
Which Question Set Should You Use?
Pick the sets that match the actual work, then ask the same ones of every candidate for that role. The core set runs through all of them, and the other five add depth where your risk sits. More sets is not better; a focused interview scored consistently beats a long one scored by feel.
6 Free Front End Question Sets to Download
Download all six as separate Word files in one ZIP, or copy individual sets. Each follows the same structure: when to use it, the questions with good-answer notes, what to listen for, and space for notes.
Set 1: Core Front End Questions
The base set for every front end hire: semantic HTML, CSS organization, JavaScript, what the browser actually does, and live work they can open and explain. Start here regardless of the stack.
Set 2: Responsive, Browser, and Accessibility Questions
For any customer-facing role: phones first, device and browser testing, keyboard operation, focus states, contrast, and how they check their own work. Use this whenever real customers will touch what this person builds.
Set 3: Performance and Page Speed Questions
For sites that sell, rank in search, or serve customers on mobile data. These questions separate developers who measure before they change anything from developers who guess at fixes, which is the most useful single signal in the whole interview.
Set 4: Frameworks, Tooling, and Code Quality Questions
For a hire who will own or inherit a codebase: framework depth tied to real projects, version control, safe deployment, documentation, how they use AI coding tools, and what happens to your code and accounts if they leave.
Set 5: Portfolio Review and Paid Work Sample
A 30 minute screen for owners who do not write code. Open their live work, judge it on your own phone, cover how they work with clients, and set up a small paid task with the same brief for every finalist.
Set 6: Front End Developer Scorecard and Red Flags
A six-area rubric, a red-flag checklist, and a decision box, so you compare candidates on written evidence instead of on whichever conversation felt best. Use it with any set above.
How to Judge Skill If You Do Not Write Code
You do not need to grade the code; you need to tell a specific answer from a vague one. That distinction survives without technical background, because the pattern is consistent across every question in these sets: strong candidates name real projects, real constraints, and real mistakes, while weak candidates speak in categories.
Three questions carry most of the load. Each one has a strong version and a weak version that you can recognize on the call, without knowing what any of the terms mean.
Beyond the answers, weight the things you can verify yourself. Do the portfolio links load? Does the site work on your phone while you hold it? Can the candidate explain one decision in language you follow? A developer who cannot explain a choice to the person paying for it will be expensive to work with, whatever their skill.
Responsive and Accessibility Questions
Ask responsive and accessibility questions of every front end candidate, even for a role you think of as cosmetic. Most of your traffic arrives on a phone, and an interface that fails on a small screen or for a keyboard user is a revenue problem before it is an engineering problem.
| Ask | What a strong answer includes |
|---|---|
| How do you build for phone and desktop? | Starts small, fluid layout, few deliberate breakpoints, tests on a real device |
| Which browsers and devices do you test on? | A short named list, and asks what our analytics actually show |
| What does accessibility mean in your daily work? | Semantic markup, labeled fields, keyboard operation, focus, contrast, alt text |
| How do you check accessibility? | An automated tool plus manual keyboard testing, and knows what automation misses |
| Tell me about pushing back on a design | A real example framed around the user, not around rules |
Accessibility is also the area where a weak answer costs the most later, because retrofitting it into a finished interface is far more expensive than building it in. Treat a dismissive answer here as a signal about everything else the candidate considers optional.
Performance Questions That Reveal Experience
The most revealing question in a front end interview is the slow page question, because it exposes method rather than knowledge. Ask what they would do about a page that takes eight seconds to load on a phone, then listen for whether the first step is measuring or guessing.
Developers who have shipped to real users always start by looking: what is downloaded, in what order, and what is the largest single item. Developers who have not start reciting remedies. That difference predicts how they will behave on every future problem you hand them, which is why this set is worth running even for a small marketing site.
| Ask | What a strong answer includes |
|---|---|
| Our page loads in eight seconds. First hour? | Measures on a throttled connection before touching anything |
| Which speed numbers do you watch? | Loading, interaction, and layout stability, tied to what users feel |
| Usual causes of a slow page? | Oversized images, heavy JavaScript, blocking third-party scripts, fonts |
| Marketing wants four tracking scripts | Measures the cost, loads them without blocking, explains the tradeoff |
| How do you keep it fast after launch? | A repeatable check and a budget that flags regressions |
The Portfolio Review and Paid Work Sample
For a non-technical interviewer, the portfolio walkthrough and a small paid work sample are worth more than every verbal question combined. Both produce evidence you can judge directly, and both are hard to fake in the way a confident answer is easy to fake.
Run the portfolio review live rather than reading a PDF. Ask the candidate to open two sites, then open one yourself on your phone while they talk. Then give every finalist the same short brief, pay for the time, and score the result against criteria you wrote down before anyone submitted anything.
Keep the sample close to the real job and away from puzzles. Algorithm questions are a poor proxy for front end work, where the difficulty lives in browsers, devices, and users rather than in data structures.
Scoring and Red Flags
Score each candidate on a written rubric immediately after the interview, while the answers are fresh. Rate the same six areas for everyone, anchored to what the candidate actually said or showed, so you compare on evidence rather than on whichever call left the best impression.
| Scoring area | What a 5 looks like |
|---|---|
| Core front end craft | Picks elements by meaning, explains browser behavior plainly |
| Responsive and accessible build | Phones first, keyboard operable, checks contrast and focus |
| Performance | Measures before changing, knows what costs speed |
| Shipped evidence | Live sites that open, honest about what they owned |
| Handover and risk | Version control, safe deploys, docs, your accounts in your name |
| Communication | Explains a technical choice to a non-technical owner |
The red flags worth weighing hardest are dead portfolio links, an inability to say which parts of a project they built, editing the live site directly with no way to roll back, and wanting hosting or the domain in their own name. If two people interview, each should score independently before you discuss, then compare notes in a structured interview feedback step.
Keep the completed scorecards with the rest of the hiring record rather than in scattered notebooks and inboxes, because the written evidence is what you fall back on if a decision is ever questioned months later. Applicant tracking is coming soon to FirstHR, and until then a single shared folder and a consistent file name per candidate do the job.
Front End Developer Pay and Classification
Benchmark against federal wage data first, then adjust for your market, the seniority you need, and whether you are posting remote. There is no separate federal occupation for front end developers specifically, so the nearest classifications are web developers and the adjacent web and digital interface designers.
Four things move a candidate inside that band: years of shipped production work, depth in the exact stack you run, the local market, and whether the role is remote. A remote posting competes against national pay expectations rather than local ones, which is the biggest surprise for owners in lower-cost markets. Decide the remote question and publish a range before you start interviewing.
On classification, the Fair Labor Standards Act computer employee exemption is not automatic. It requires payment on a salary or fee basis of at least $684 per week, or at least $27.63 an hour, plus qualifying duties such as the design, development, testing, or modification of computer systems and programs, per Department of Labor Fact Sheet 17E. State rules can be stricter, and the employee versus contractor test follows the shape of the work rather than your preference.
Fair, Legal, and Structured Interviewing
A good technical interview is fair, legal, and structured, and the three reinforce each other. Asking the same job-related questions of every candidate and scoring them on a written rubric keeps you compliant, reduces bias, and produces better hires at once. This is the part the generic question lists skip entirely.
A structured interview, where every candidate answers the same questions scored against a consistent rubric, predicts on-the-job performance more reliably than an open conversation. Asking the same job-related questions of everyone also keeps you inside the EEOC's rules against basing decisions on protected characteristics. This is general information, not legal advice.
Interviewing Without an HR Department
At a large company, a front end candidate runs through a panel of engineers with a recruiter managing the scorecards. At a small business the owner usually runs the whole thing alone, between everything else, and often without anyone who can evaluate code. That reality shapes the interview, and it is where the avoidable mistakes concentrate.
From Interview to Onboarding
The interview is step one. Once you choose a developer, onboarding this role has a few extra steps because of the access involved: a signed offer letter and a confidentiality agreement, an intellectual property assignment, and repository, hosting, domain, and analytics access created under the business rather than under the developer, alongside the standard I-9 and W-4.
Give the new hire one small, real change to ship in week one. It teaches you more than a month of setup and it proves the deployment path works end to end. Pair it with a structured onboarding template so the first thirty days have a shape, and keep the new-hire paperwork in the same place as the interview scorecards you used to decide.
FirstHR connects the offer, the agreements, e-signatures, and the onboarding workflow in one system, and stores every signed document on the employee profile, so a small business can run hiring through onboarding without a spreadsheet and four inboxes. FirstHR is an onboarding and HR platform, not a code hosting or project management tool, so connect those separately. Applicant tracking is coming soon to FirstHR.

Frequently Asked Questions
What questions should I ask a front end web developer?
Ask questions that produce evidence rather than opinions. The strongest openers are: show me two sites you built that are live today and tell me what you personally did; how do you decide which HTML element to use for a button or a link; walk me through building a page that works on a phone and a desktop; our page takes eight seconds to load on a phone, what do you do first; can someone use what you built with a keyboard alone; and what happens to our site, code, and accounts if we stop working together. Add framework and deployment questions if the hire will own a codebase. Close with a small paid work sample so you see real output before you decide. This page includes six ready-to-use sets and a scorecard, each question paired with a note on what a good answer sounds like.
How do I interview a front end developer if I cannot code?
You do not need to grade the code, you need to grade the evidence. Ask the candidate to open two live sites on the call, then view one on your own phone; a broken mobile layout is something anyone can see. Ask them to explain a technical decision in plain language, because a developer who cannot explain their choices to an owner will be expensive to work with. Listen for specificity and honesty: strong candidates name what they personally built and admit what a designer or teammate did. Then run a small paid work sample with the same brief for every finalist and score it on five things you can check yourself: match to the design at phone and desktop width, keyboard operation, load speed on a phone, clarity of their written note, and whether they delivered on time.
What is the difference between a front end and a back end developer?
A front end developer builds everything the customer sees and touches in the browser: layout, responsiveness, page speed, forms, animation, and accessibility, usually with HTML, CSS, and JavaScript plus a framework. A back end developer builds what the customer never sees: server code, the database, integrations with payments or email, security, and uptime. A full stack developer does both, which is what many small businesses actually need when one person owns the entire website. Decide which half carries the risk in your business before you write the questions. A marketing site, landing pages, or a storefront front end is mostly front end work. A booking system, a customer portal, or anything holding payment data leans back end. A web designer is a fourth thing again, closer to visual design than to code.
Should I give a front end developer a coding test?
A small paid work sample beats both a whiteboard test and an unpaid take-home project. Give every finalist the same brief, keep it under four hours, pay for the time, and make it mirror the actual job: build one responsive page from a design so that it works on a phone, is operable with a keyboard alone, loads quickly on mobile data, and comes with a short note explaining the choices. Score it on stated criteria before you look at who submitted it. Unpaid multi-day projects filter for candidates with free time rather than for skill, and strong developers frequently decline them. Algorithm puzzles are a poor proxy for front end work in particular, because the job is far more about browsers, devices, and users than about data structures.
Why do accessibility questions belong in a front end interview?
Because the front end is where accessibility is either built in or lost, and the cost of losing it lands on the business. The Department of Justice has consistently taken the position that the Americans with Disabilities Act applies to the goods and services a public accommodation offers on the web, and its guidance points to the Web Content Accessibility Guidelines and the Section 508 standards as the technical references most often used. A developer who labels form fields, keeps interfaces keyboard operable, maintains visible focus states, and checks color contrast prevents a category of problem that is far more expensive to retrofit than to build correctly. Ask what accessibility means in their day-to-day work and how they check it; vague or dismissive answers tell you what you will inherit. This is general information, not legal advice.
How much does a front end web developer cost?
Pay varies widely by experience, specialty, market, and whether the role is remote. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), web developers had a median annual wage of $92,650, about $44.54 an hour, with the lowest 10 percent under $48,100 and the highest 10 percent above $162,290. The closely related web and digital interface designers occupation reported a higher median of $104,000. The spread between the deciles is more than three to one, so the title alone tells you almost nothing about the number. Four factors move a candidate inside the band: years of shipped production work, depth in the exact stack you run, the local market, and whether you post the role as remote, because a remote posting competes against national expectations rather than local ones.
Are these front end developer interview questions legal to ask?
Yes. Questions about a candidate’s technical experience, how they build and test, which browsers they support, how they deploy, and what they shipped are job-related and permitted. The legal caution is general to all interviewing: avoid questions touching protected characteristics such as age, race, religion, national origin, disability, or family status, and note that a growing number of states and cities restrict asking about salary history. Keep every question tied to the work and ask the same core questions of every candidate for the same role. Using one structured set and one scorecard for everyone is itself a safeguard, because it documents that you evaluated candidates on the same job-related criteria. For specifics, consult EEOC guidance or a qualified employment advisor. This is general information, not legal advice.
Should I hire a front end developer as an employee or a contractor?
The decision follows the shape of the work, not your preference or your budget. A defined, project-shaped need with a clear end, such as rebuilding a marketing site, suits a contractor. Continuous work with ongoing direction, set hours, and your tools suits an employee. The classification test is legal rather than optional, and a long-term contractor whose work you direct closely can drift into employee territory over time. Whichever route you take, settle account ownership in writing before the first commit: repository, hosting, domain registrar, and analytics registered to the business, with the developer added as a user. Add a confidentiality agreement and an intellectual property assignment. This is the single most common gap I see at small businesses, and it is far cheaper to fix at the offer stage than after someone leaves.
Make HR the easy part of running your business
Onboarding, e-signatures, training and core HR in one place. Up and running in 5 minutes.
- 7-day free trial
- No credit card required
- Cancel anytime

