Intervooh · Interview questions by job · Technology & IT
Frontend Developer interview questions (2026)
Frontend Developer interviews in the UK are assessed on modern javascript & frameworks, accessibility & semantic markup, web performance, usually across 3 stages — phone or video screen, then competency and behavioural questions, then technical interview or test. The 12 questions below are the ones actually asked, each with what a strong answer does.
Researched, current questions asked in real frontend developer interviews in the UK (Technology & IT), with what a strong answer actually does. Questions marked 2026 are the newer, AI-era questions employers now ask. Last reviewed 2026-07-22.
Build my free day-by-day prep plan →
Tell it the company, role and date; it does the rest. Free, no card.
What they assess
- Modern JavaScript & frameworks
- Accessibility & semantic markup
- Web performance
- Working with design & product
How a frontend developer interview usually runs
- Phone or video screen
- Competency and behavioural questions
- Technical interview or test
The questions to expect
Tell me about the most complex UI you've built. What made it hard?
Pick complexity of state or interaction, not visual polish — race conditions, optimistic updates, undo. Show the architecture that tamed it.
Describe a time a design wasn't feasible as specced. How did you handle it with the designer?
Show you offered options with costs, not a flat no. The result is a shipped compromise and a designer who still trusts you.
Tell me about a time you made a slow page fast. How did you measure it?
Numbers before and after — Core Web Vitals, bundle size, time to interactive — and the one change that mattered most.
Tell me about a time you improved accessibility. What did you change and how did you test it?
Real testing convinces: keyboard-only runs, a screen reader, axe or Lighthouse — plus WCAG criteria named without being recited.
How does React decide when to re-render, and how would you stop an unnecessary re-render?
State/props flow first, then tools: memoisation, state colocation, keys. Mention that the React Compiler changes the manual-memo calculus.
Build (or talk through) a type-ahead search box: debouncing, cancelling stale requests, keyboard access.
A favourite live exercise. Narrate edge cases as you go — empty input, out-of-order responses, aria roles — that's where marks live.
How do you decide whether state lives in a component, a context, or a store?
Give a decision rule — ownership, sharing scope, server vs client state — and an example where you moved state and why.
Why frontend, rather than backend or full stack?
Show you chose it: the user-facing feedback loop, the craft of interaction. Avoid sounding like backend was too hard.
AI tools can generate a working component from a prompt. What do you check before you'd ship one?2026
The checklist is the answer: accessibility, performance, edge states, security of inputs, fit with your design system. AI rarely does these.
Tell me about a time you explained a technical problem to someone non-technical.
Pick a real audience and show the translation: the analogy you used, what you left out, and how you checked they got it.
Describe a production incident you were involved in. What did you do first?
Order matters: mitigate, communicate, then root-cause. Finish with the fix that stopped it happening again.
Walk me through a technical decision you made that you later reversed.
Reversing well is the skill. Show what new information arrived, how fast you acted on it, and what the reversal cost.
How to prepare for a frontend developer interview in the UK
UK frontend interviews usually pair a practical exercise (live or take-home) with a chat about past work; expect React plus TypeScript as the default assumption, and have a real accessibility story ready — it's asked more here than candidates expect.
How Technology & IT interviews are run in 2026
- Coding rounds increasingly allow — or expect — an AI assistant: you are marked on how you prompt, verify and fix its output, not typing speed. Live reasoning, debugging and code-review rounds have grown to compensate.
- System design and 'explain your thinking out loud' rounds carry more weight than puzzle-style coding; many employers explicitly verify real-time reasoning because take-homes are now AI-solvable.
- Volume employers screen with async one-way video and online tests before any human round, so camera practice matters at the top of the funnel.
Turn this into a plan
A list of questions is a start; a programme is what changes the outcome. Intervooh builds a day-by-day plan for your exact frontend developer interview — company research, story building with an AI coach, spoken practice with delivery feedback, and scored mock interviews. It never writes your answers for you.
Related Technology & IT roles
- Cloud Engineer interview questions
- Cyber Security Analyst interview questions
- DevOps Engineer interview questions
- IT Manager interview questions
- IT Support Technician interview questions
- Mobile Developer interview questions
- Network Engineer interview questions
- QA Engineer interview questions