picked.
Log inPost a role
picked.ai/hire/frontend-engineer/interview-questions
30 frontend engineer
interview questions that actually work.
Pulled from the Neuroworx item bank: nine years of calibration against twelve-month performance outcomes on 14,083 frontend engineers. Sorted by stage (screen, assessment, on-site) and level (IC1 to IC5). Each question comes with what to listen for, what to ignore, and the failure mode it is designed to catch.
30
questions
4
stages
5
levels
14k
hires of validity data
Screen ↓Role-fit ↓On-site ↓Anti-pattern questions ↓
Stage 01 · Screen
Twelve minutes. Ten questions.
The screening conversation. Picked runs this with an AI voice; this is what a human screen would look like with the same rubric. Time-box hard. 60 seconds per answer.
10 questions
01
Tell me about the last interface you owned past launch. What broke first in production, and what did you do?
ownershipspecificity
Listen for
A specific surface (checkout, onboarding, dashboard). A real failure (layout shift, slow paint, broken keyboard nav). A fix with a named trade-off.
Ignore
Adjective-heavy answers about "modern" or "clean" UI with no incident and no metric.
catches · CV inflation. Projects they styled but did not own.
02
Pick a part of your current frontend codebase you think is wrong. Why has it not been fixed?
judgementtaste
Listen for
A specific component or pattern. An honest reason for the delay (cost, dependency, fear of regression).
Ignore
"Everything is fine." Or a complaint about a teammate dressed up as architecture.
catches · Cannot hold a code opinion without making it personal.
03
Walk me through the most recent feature you took from Figma to production.
scopeagency
Listen for
The full arc: designer conversations, accessibility checks, who QA-ed it, what they cut. Specific dates.
Ignore
A list of npm packages used. Stack is downstream of scope.
catches · Engineers who only own the inside of the component file.
04
What is the smallest UI decision you have fought hardest for?
convictiontaste
Listen for
A real example. A button-state pattern, a focus order, an empty state. They say what they would do differently now.
Ignore
Big architecture flexes about state management. Usually rehearsed.
catches · No discrimination between large and small decisions.
05
Pick a website you use every day and tell me one thing about how its frontend probably works.
curiositysystems
Listen for
A reasonable guess at routing, hydration, asset strategy, or caching. They name what they do not know.
Ignore
Recital of marketing copy from a framework site.
catches · Engineers who have never opened devtools on a site they did not write.
06
Last time a designer pushed back on your implementation. Walk me through it.
commsdesign partnership
Listen for
A specific moment of disagreement. Whether they shifted, and what changed their mind.
Ignore
"I always listen to design." Means nothing.
catches · Engineers who treat design as an input and not a partner.
07
What is your favourite browser or rendering bug you have hunted down?
craftwar stories
Listen for
A specific bug with a specific repro. Their precise role. What they shipped after.
Ignore
A funny story about IE11. Usually folklore.
catches · Engineers who avoid the messy parts of the platform.
08
Tell me about a frontend framework or library you tried and rejected.
tastecritical thinking
Listen for
A real evaluation with a real reason. What they used instead and why it suited the team.
Ignore
A framework they are "looking at". Performative.
catches · CV as the boundary of what they have considered.
09
How do you onboard onto an unfamiliar frontend codebase?
judgementgenerality
Listen for
A sequence: run it, click around with devtools open, trace one route, find a recent PR, ask one specific question.
Ignore
"I read the readme then the components folder." Order-of-operations without judgement.
catches · Engineers who freeze without a styleguide.
10
What is one thing you want in your next role that you would not apply for a role without?
stage fitseriousness
Listen for
Something specific. A design partner. A real customer base. A particular product surface.
Ignore
"Impact." "Growth." "Ownership." Vague.
catches · Candidates who are not sure why they are looking.
Stage 02 · Role-fit assessment
A scoped task. A scored rubric.
One realistic task. We score the writeup, not the polish. The candidate has the take-home equivalent of 60 minutes.
8 questions
01
Take this Figma frame and a stub API. Build the component, including the loading and empty states. 60 minutes.
craftIC1+
Listen for
Sensible markup, sensible spacing tokens, an empty state that thinks about the user. Time spent on the real cases.
Ignore
Pixel-perfect chrome on the happy path with no thought for what happens when the API returns nothing.
catches · Engineers who cannot ship anything without a designer in the room.
02
Here is a 300-line React component from a real codebase. Refactor it. Three bullets on what you changed and why.
code qualityIC2+
Listen for
A real abstraction extracted, useful naming, props simplified. The three bullets reveal taste.
Ignore
Renaming variables and adding more memoisation than the component needs.
catches · Cargo-cult refactors. Lots of motion, no improvement.
03
Audit this page for accessibility. Send back the five issues you would fix first and why.
accessibilityIC2+
Listen for
Issues a screen-reader user would actually hit. Order that reflects severity, not what a linter flagged.
Ignore
A copy-paste of axe output with no opinion.
catches · Engineers who think accessibility is a checklist they outsource.
04
This page has a Largest Contentful Paint of 4.2 seconds. Tell me how you would investigate, then propose a fix.
performanceIC3+
Listen for
A real investigation order: network, then render-blocking, then bundle. Specific tools. A real first cut.
Ignore
Generic advice about lazy-loading everything.
catches · Engineers who reach for solutions before measurement.
05
Read this 2-page design spec. Write three questions you would ask the designer and one push-back.
design partnershipIC3+
Listen for
Questions that show they have actually read it. A push-back that engages with the user trade-off the designer made.
Ignore
Stylistic edits to the spec. Not useful.
catches · Engineers who cannot engage with a designer's intent.
06
Take this real PR. Decide if you would approve, request changes, or close. Write the review.
code reviewIC2+
Listen for
Substantive comments. They reach for the API shape, the accessibility implication, the test gap.
Ignore
Long reviews focused only on naming and formatting.
catches · Reviewers who treat every comment as equal weight.
07
Sketch a design-system primitive for a Button. Tell me what props it needs, what props it does not, and what it owns.
component thinkingIC3+
Listen for
A small surface. A clear separation between visual variant and behaviour. They name what should not be configurable.
Ignore
20 props and a story about flexibility.
catches · Engineers who pack every future requirement into the first abstraction.
08
In 200 words, why might the component you sketched in question 7 be the wrong primitive for our codebase?
humilityIC4+
Listen for
Genuine engagement with the alternative. A real "I might have started smaller" or "I should have asked first".
Ignore
A second pitch for the original design.
catches · Lack of perspective on their own decisions.
Stage 03 · On-site (after Picked)
Twelve questions you will still want to ask in person.
Picked screens, scores, and shortlists. These are the questions worth asking with a human in the room: the calibration questions, the dealbreakers, the chemistry probes.
12 questions
01
Where, in the work, do you want to grow most this year?
growthmanager fit
Listen for
A specific gap. A plan, even tentative. A name of someone they would learn from.
Ignore
"I want to become a staff engineer." Title-laddering is not growth.
catches · Engineers without a learning agenda.
02
Tell me about a time you disagreed with a manager. What happened?
authoritymanager fit
Listen for
A real disagreement. The mechanics, not the moral. What they took from it.
Ignore
"I have never disagreed with a manager."
catches · Engineers who cannot hold opinions in the face of authority.
03
What is the most uncomfortable feedback you have received and what did you do with it?
self-awareness
Listen for
A specific piece of feedback. The change they made. The thing they still wrestle with.
Ignore
"I take feedback well." Means nothing.
catches · Defended self-narrative.
04
Walk me through a project or feature you wish had failed faster.
judgementoperating
Listen for
Honesty. A specific moment they could have called it. What stopped them.
Ignore
A pitch for the project being secretly worth doing.
catches · Sunk-cost thinkers.
05
What is a strong opinion about frontend you have recently changed?
intellectual humility
Listen for
A specific opinion. A specific cause (a talk, a colleague, a bug). They name the source.
Ignore
"My mind is always open."
catches · Closed-loop thinkers.
06
Pick two senior engineers or designers you admire from your last role. What do they do differently?
taste
Listen for
Concrete habits. Habits they have adopted. Habits they have not.
Ignore
Pure praise with no differentiation.
catches · Engineers without taste for other engineers or designers.
07
Tell me the last technical thing you read about the web outside of work.
curiosity
Listen for
A specific blog, talk, or spec. They tell you what they thought, not just that they read it.
Ignore
A book they "always mean to get to".
catches · Engineers who do not think about the platform.
08
When are you most productive?
operating model
Listen for
A specific time-of-day and environment. A self-aware answer about energy.
Ignore
"I am always productive." Noise.
catches · Engineers without self-instrumentation.
09
Where would you rather be in three years?
careerretention
Listen for
A direction (deeper IC vs people-management, frontend specialist vs full-stack drift) and a reason.
Ignore
"Wherever the company needs me." Suspicious.
catches · Drifting engineers.
10
If you join, what would you want your first week to look like?
agencyonboarding
Listen for
A specific plan. Often: pair on a small PR, audit the design tokens, watch a user session, read three components end-to-end.
Ignore
"Whatever you suggest."
catches · Engineers without an onboarding instinct.
11
What would make you leave us within six months?
dealbreaker
Listen for
A specific irritant. A specific working condition. A specific kind of management.
Ignore
"As long as the work is good."
catches · Hidden dealbreakers, surfaced post-offer.
12
What is one question you want to ask our most cynical engineer?
probingcuriosity
Listen for
A real question. Often about a quiet thing: "Why is the build slow?" or "What component does nobody touch?"
Ignore
A softball or a re-pitch of their interest.
catches · Candidates who do not want to know what is wrong.
The anti-pattern set
Eight questions that look smart
but tell you nothing.
"What is your biggest weakness?"
You will get a strength-shaped weakness. We have asked this 47,000 times. It catches no-one. Replace with: "What is the most uncomfortable feedback you have received?".
"Where do you see yourself in five years?"
Either a rehearsed answer or a stalled one. Both useless. Replace with: "Where would you want to be in three years?"
"Tell me about yourself."
Wastes the first three minutes on the CV they already gave you. Replace with: "Walk me through the most recent thing you shipped end-to-end."
"Why this company?"
Generates polished mission-talk. Replace with: "What about this role made you apply that would not have made you apply elsewhere?"
"Are you a team player?"
No-one says no. Replace with: "Tell me about a time a teammate disagreed with you and how you handled it."
"How do you handle stress?"
No-one says badly. Replace with: "Tell me about your last production incident and your precise role."
"How would you reverse a linked list?"
Probes nothing we care about. We removed it from the bank in 2019. Replace with: "Refactor this 200-line file and tell me what you changed and why."
"If you were an animal, which animal would you be?"
You know what we are going to say. Replace with: anything else.
Or, let us ask
We will ask these for you.
By Friday.
Picked runs the screen, the assessment, and the first-round interview against this exact item bank. You meet the three finalists in person, with these on-site questions in hand.
$0.99 per AI-vetted candidate. First 50 free.
Companion pages
picked.
The AI-native replacement for inbound hiring. For the hiring manager, not HR.
© 2026 Picked · Made in London · Three finalists in forty-eight hours.
Frontend engineer interview questions · Picked.ai