On this page
What a typical technical interview looks like
Theory questionsThe difference between var/let/const, closures, working with arrays and objects — language fundamentals.
A practical taskA small algorithmic or logic problem, solved live on the call or beforehand.
Walking through your codeExplaining your decisions — why you chose one approach over another.
Questions about your projectsA discussion of real projects from your portfolio — what you built and what problems you solved.
How to prepare
- Review the fundamentals: data types, comparisons, arrays, the DOM, asynchronous code.
- Work through practice problems ahead of time — not for the first time during the actual interview.
- Prepare a short story about 2–3 of your projects in advance: what you built, why, and what challenges came up.
- Practice explaining your code out loud — it's a different skill from just writing it.
What to do if you don't know the answer
Don't stay silent — think out loud, even if you're not fully sure. Interviewers often care more about your reasoning process than a perfect final answer. Saying "I'm not sure, but here's my guess" sounds better than complete silence.
Frequently Asked Questions
What if I can't solve a task in the interview?
One unsolved problem rarely decides the whole interview — showing your thought process and willingness to work through it matters more.
How much prep time do I need?
With a solid foundation already in place, a few days of focused review of key topics is usually enough.
What's next
Prepare for interviews systematically
The JavaScript course covers exactly the fundamentals most often checked in technical interviews.