Interview guide
Frontend Engineer interview questions
Frontend interviews test JavaScript/TypeScript fundamentals, framework knowledge (often React), performance, accessibility and how you collaborate with design. Expect a practical coding exercise building a small UI.
Role-specific questions
1.How would you make a slow page faster?
Why they ask: Performance is one of the most-cited frontend skills in job posts.
How to answer: Measure first (Lighthouse, Web Vitals, profiler). Then the usual suspects: bundle size and code splitting, render-blocking resources, images, unnecessary re-renders, caching. Share a real before/after.
2.Explain how React decides when to re-render.
Why they ask: Framework depth beyond copying patterns.
How to answer: State or props change → component and children re-render; memoisation and stable references avoid wasted work. Mention when you’d reach for memo and when it’s premature.
3.How do you make a component accessible?
Why they ask: Accessibility is increasingly a hard requirement.
How to answer: Semantic HTML first, keyboard support and visible focus, labels and ARIA only where needed, colour contrast, testing with a screen reader. Give an example you fixed.
4.How do you manage state in a large app?
Why they ask: Architecture judgment.
How to answer: Keep state as local as possible; server state in a data-fetching cache; global client state only for truly shared UI. Explain a trade-off you’ve lived with.
5.How do you work with designers when a design is hard to build?
Why they ask: Collaboration and pragmatism.
How to answer: Raise it early with options and costs, prototype the risky part, agree on what matters to the user. Show you respect the design intent.
6.What’s your approach to building a design system?
Why they ask: Common in senior roles.
How to answer: Start from repeated patterns, tokens before components, document with real usage, version carefully. Mention adoption — a design system nobody uses has failed.
Reading answers isn’t practising them
Get questions built from your résumé and a real job post, answer out loud, and get STAR scoring, follow-up questions and pace feedback. Free to start.
Behavioral questions
Every frontend engineer interview includes these. Answer with STAR: the Situation, your Task, the Actions you took, and the Result — with a number where you can.
7.Tell me about yourself.
Why they ask: It sets the frame for the whole interview and tests whether you can summarise your career around what they need.
How to answer: 90 seconds: present (current role and one proud result), past (the path that got you here), future (why this role is the logical next step). Skip your life story.
8.Tell me about a time you disagreed with a teammate or manager.
Why they ask: They want to see that you can push back with evidence and still commit once a decision is made.
How to answer: Use STAR. Show how you understood their view, what data you brought, how it was resolved — and what you did if you lost the argument.
9.Describe a project that failed or didn’t go to plan.
Why they ask: Ownership and learning matter more than a perfect track record.
How to answer: Pick a real failure you contributed to. Spend most of the answer on what you changed afterwards — ideally with a later result that proves it.
10.Tell me about a time you had to deliver under a tight deadline.
Why they ask: They’re testing prioritisation and communication, not heroics.
How to answer: Explain what you cut or re-scoped, who you told and when, and the outcome. Mention the trade-off you consciously accepted.
11.What’s an accomplishment you’re most proud of?
Why they ask: It shows what you value and the scale you operate at.
How to answer: Choose one relevant to this role. Make your personal contribution clear (“I”, not “we”) and end with a number.
12.Why do you want to work here?
Why they ask: They want evidence you chose them — not just any job.
How to answer: Connect something specific (their product, a recent launch, how the team works) to your experience and what you want to do next.