Interview questions
Web Developer interview questions, from 222 real job postings
What employers ask Web Developer candidates about, based on the skills their open postings list. Each question says what a strong answer shows.
- Open postings
- 222
- Top skill
- HTML
- Fully remote
- 6%
- Posted pay
- –
43 list skills
in 51% of postings
of open postings
Not enough posted pay
What employers ask for
Share of 43 open Web Developer postings that list each skill.
- 51%
- 49%
- 49%
- 35%
- 19%
- 19%
- 19%
- 16%
- 16%
- 16%
Technical questions
Three questions for each of the 6 skills Web Developer postings ask for most.
HTML
In 51% of postings- 1
When would you use semantic HTML elements like `<article>`, `<section>`, and `<nav>` instead of just `<div>` tags?
What a strong answer shows: Explains semantic tags improve accessibility for screen readers, help search engines understand structure, make code more readable, and are required for proper document outline.
- 2
A designer hands you a mockup with a form that needs to validate email and phone number while typing. What HTML attributes or elements would you use to handle this?
What a strong answer shows: Mentions input type attributes (email, tel), describes using pattern attribute for custom validation, notes that browser validation is a first line of defense but server validation is always needed.
- 3
Tell me about a time you had to fix accessibility issues in existing HTML markup.
What a strong answer shows: Describes a specific problem (missing alt text, unlabeled form fields, broken heading hierarchy), names the tool they used to find it (axe, WAVE, screen reader), explains what they changed.
CSS
In 49% of postings- 4
Explain the CSS cascade and specificity. When would you use !important and why should you generally avoid it?
What a strong answer shows: Defines cascade as later rules override earlier ones, explains specificity scoring (inline > IDs > classes > elements), notes !important breaks the cascade and makes debugging harder.
- 5
You're building a layout that needs to work on phones, tablets, and desktops. Walk me through how you'd approach this with CSS.
What a strong answer shows: Mentions mobile-first approach, describes using media queries with breakpoints, explains using flexible units (em, rem) over pixels, discusses testing at actual sizes not just resizing.
- 6
Tell me about a time you solved a layout problem in CSS that turned out to have a simple solution.
What a strong answer shows: Describes the problem in detail (centering, spacing, overflow), explains what they tried first, names the CSS property that actually fixed it and why it worked.
JavaScript
In 49% of postings- 7
What's the difference between var, let, and const in JavaScript?
What a strong answer shows: Explains var has function scope and hoisting quirks; let and const have block scope; const prevents reassignment but doesn't make objects immutable. Gives an example of when this matters.
- 8
You notice a web page is loading slowly. Walk me through how you'd identify whether the problem is in your JavaScript code.
What a strong answer shows: Mentions opening browser DevTools (Performance tab or Network tab), checking for long-running scripts, measuring execution time, and looking at which operations are blocking the main thread.
- 9
Tell me about a time you fixed a tricky bug related to asynchronous code or callbacks.
What a strong answer shows: Describes a specific issue (race condition, callback hell, unhandled promise, etc.), what they tried first, how they solved it, and what they'd do differently now.
React
In 35% of postings- 10
Can you explain the difference between state and props in React, and when you'd use each?
What a strong answer shows: States are mutable and local to a component; props come from parents and are immutable. Gives an example like a form input (state) versus a button's label (prop).
- 11
You're building a list of items and each item has a delete button—how would you handle the deletion and re-render, and what would you need to be careful about?
What a strong answer shows: Shows they'd update state (remove item from array), explains why you can't mutate directly (use spread or filter), mentions key prop on list items to avoid render bugs.
- 12
Tell me about a React component you built that became complex and how you refactored it.
What a strong answer shows: Describes a real component, what made it complex (nested state, multiple callbacks, side effects), and how they split it (smaller components, custom hooks, context) with concrete code or structure details.
A/B Testing
In 19% of postings- 13
What does statistical power mean in an A/B test, and why do you need to calculate it before running the test?
What a strong answer shows: Explains power is the probability of detecting a real effect if it exists; mentions power and significance level together determine sample size needed.
- 14
You want to A/B test a new checkout flow. Walk me through how you'd design this experiment and know when to stop.
What a strong answer shows: Discusses hypothesis, success metric, power and significance level, sample size calculation, stopping rule; avoids peeking at results mid-test.
- 15
Tell me about an A/B test you analyzed or ran—what were you testing, what did you find, and what was your recommendation?
What a strong answer shows: Names the change tested and the metric tracked, states the result and confidence level, explains the business decision that followed.
REST APIs
In 19% of postings- 16
Can you explain what makes an API RESTful and what REST principles guide endpoint design?
What a strong answer shows: Describes using HTTP verbs (GET, POST, PUT, DELETE) for actions, resources identified by URLs (/users/123), status codes indicate results, stateless; names principles like HATEOAS if appropriate, avoids vague definitions.
- 17
You're designing an API where clients need to fetch posts and their author's profile information—how would you structure the endpoints to avoid over-fetching or under-fetching?
What a strong answer shows: Considers approaches: include related data in POST response (?include=author), separate endpoints clients call, nested routes (/posts/123/author); discusses trade-offs, shows thinking about client needs.
- 18
Tell me about a REST API you built or maintained and what you learned about versioning, pagination, rate limiting, or error handling.
What a strong answer shows: Names the API, describes a specific problem they encountered (clients breaking on schema changes, large result sets, abuse prevention, inconsistent error formats) and how they solved it.
Behavioral questions
Have one real story ready for each.
- 19
Tell me about a time you had to debug a production issue—what was the problem and how did you solve it?
What a strong answer shows: Describes the specific error or symptom, the debugging steps they took (logs, profiling, etc.), and what root cause they found. Shows they can isolate problems methodically, not just apply random fixes.
- 20
Describe a situation where you had to refactor legacy code—what made it necessary and what approach did you take?
What a strong answer shows: Explains the actual problems in the old code (performance, maintainability, bugs), the refactoring strategy they used, and how they verified nothing broke. Shows they balance pragmatism with code quality.
- 21
Tell me about a time you disagreed with another engineer on how to solve a technical problem—how did you handle it?
What a strong answer shows: Recounts the disagreement and how they discussed trade-offs (performance vs. maintainability, timelines, etc.), what decision was made, and what they learned. Shows they can advocate for ideas while staying collaborative.
- 22
Give an example of a feature you built that turned out more complex than expected—how did you manage it?
What a strong answer shows: Describes what assumptions were wrong, how they re-scoped or communicated the complexity to stakeholders, and how they delivered. Shows they can adapt when reality diverges from the plan.
- 23
Tell me about a code review where you found a significant issue—how did you communicate it?
What a strong answer shows: Explains the issue itself (security flaw, performance problem, edge case bug), how they framed feedback constructively, and whether the person accepted it. Shows they can be thorough without being harsh.
Questions to ask them
Use the data. Interviewers remember candidates who ask specific questions.
Timeline. Web Developer postings stay open a median 29 days (30 closed in the last 180 days). Ask when they plan to decide and how many rounds are left.
The role. Ask whether this is a new role or a backfill, and what happened to the last person in it. Check the company's hiring score on HirQ first.
- 1
How do you measure success for someone in this role during their first year?
What the answer tells you: Their answer reveals whether the company has clear expectations or vague goals, and what they actually care about you delivering.
- 2
Can you walk me through what a typical week looks like for someone in this position?
What the answer tells you: You'll learn whether the role matches the job description and whether the daily work aligns with what you want to do.
- 3
Why is this role open right now—did someone leave, or is this a new position?
What the answer tells you: If it's a backfill, you understand the workload; if new, you learn whether the company is growing or shifting priorities.
- 4
What's the team structure, and who would I be working with most closely?
What the answer tells you: You get a sense of your peer group, reporting lines, and whether you'll be isolated or have colleagues to learn from.
- 5
What's your timeline for making a decision, and what does the rest of the process look like?
What the answer tells you: You know when you'll hear back and what to prepare for, so you can plan next steps and avoid uncertainty.
- 6
What does onboarding look like here—do people have a ramp period or are they expected to contribute immediately?
What the answer tells you: Their answer shows whether the company invests in new hires or throws them in; this affects how quickly you can actually be effective.
- 7
What are the biggest challenges this team is facing right now?
What the answer tells you: You hear what problems are real versus what they said in the job posting, and whether you're equipped to help solve them.
- 8
How has this role evolved since it was first created, or how do you expect it to change in the next year or two?
What the answer tells you: You understand whether the job is stable, growing, or shifting—and whether your skills will stay relevant here.
- 9
What does a typical career path look like for someone doing well in this role?
What the answer tells you: You learn whether there's room to advance within the team or if you'd need to move around to grow.
- 10
What made you decide to work here, and what keeps you here?
What the answer tells you: Their honesty about why they stay tells you whether this is a place people actually want to be or just tolerate.
Practice for a specific job
Practice for a specific job
Uses 1 AI runPaste a HirQ job link or the job description. We write 8 likely questions with talking points from your resume (your profile resume if you leave it blank).
Skills come from the text of open postings on HirQ, matched against a fixed list of 230 skills. Questions were written once per skill and category with AI and checked against that list; they are not from any one employer.
Get new Web Developer jobs by email
Free alerts, daily or weekly. We only send jobs that are still open.
Questions people ask
What skills do Web Developer interviews focus on?
Based on 43 open Web Developer postings that list skills, employers most often ask for HTML (51%), CSS (49%), JavaScript (49%), React (35%), A/B Testing (19%). Expect technical questions on the first two or three.
How should I answer behavioral questions for a Web Developer role?
Use one real story per question: the situation, what you did yourself, and the result. Keep each under two minutes and be ready for a follow-up on what you would do differently.
How long does hiring for a Web Developer take?
Web Developer postings that closed in the last 180 days stayed open a median of 29 days (30 postings). Ask about the timeline at the end of your first interview.