Frontend interview guide
Practice explaining browser behavior, JavaScript and accessible interfaces with answer outlines.
Open resourceInterview guides / FREE RESOURCE
Turn coursework, club work and personal projects into truthful, specific interview stories.
Use 5 minutes for a project introduction, 15 minutes for three questions, 5 minutes for follow-ups and 5 minutes for feedback. Score clarity, correctness and concrete evidence from 0–2 each. This is self-review, not an employer score.
Question 1
Give a brief present focus, one relevant project and why this role fits your next step. Avoid reciting your entire biography.
Follow-up: Can you finish in about 60–90 seconds?
Question 2
Explain the symptom, hypotheses, evidence, fix and prevention. Mention what you ruled out and why.
Follow-up: What would you try first if it happened again?
Question 3
Describe the shared goal, competing options and how you gathered evidence or agreed on a decision. Focus on actions rather than blaming someone.
Follow-up: What did the other person’s perspective teach you?
Question 4
Own your contribution, explain early communication or its absence, and describe how you reduced scope or recovered.
Follow-up: What process did you change afterward?
Question 5
Separate the team outcome from your own implementation, tests, documentation or coordination. Link to evidence where possible.
Follow-up: Which decisions did you own?
Question 6
Name the task, the gap, your learning strategy and how you verified competence through a small result.
Follow-up: How did you know the source was reliable?
Question 7
Choose a real work-relevant limitation and describe a concrete practice with progress evidence. Avoid disguised strengths.
Follow-up: What feedback have you received recently?
Question 8
Ask how interns receive feedback, what a successful first month looks like and how code is reviewed. Use the answer to judge fit.
Follow-up: Which answer would change your interest in the role?
Notes save on this device. Avoid entering passwords or sensitive information.
Practice explaining browser behavior, JavaScript and accessible interfaces with answer outlines.
Open resourcePractice HTTP, database, authorization and reliability questions using concrete examples.
Open resourceAnswer practical test design, defect reporting and automation questions with evidence.
Open resource