The JavaScript questions I ask in a frontend interview
The JavaScript questions I ask in frontend interviews, from stale closures and the event loop to async races, and what a good answer sounds like.
Read moreBlog
Practical interview prep advice and CodePrepped product news.
The JavaScript questions I ask in frontend interviews, from stale closures and the event loop to async races, and what a good answer sounds like.
Read moreThe CSS questions I ask in frontend interviews, from the cascade and stacking contexts to container queries, and what a good answer sounds like.
Read moreThe performance questions I ask in frontend interviews, what a good answer sounds like, and how to prepare with a real before and after.
Read moreThe accessibility questions I ask in frontend interviews, what a good answer sounds like, and how to prepare without memorising WCAG.
Read moreThe order I read a frontend CV in, the bullets that get you a screen, and the layout mistakes that quietly cost you.
Read moreSilent forks fail screens. Here are the state, async, empty, and a11y trade-offs I want said out loud.
Read moreMost take-homes fail when I lose trust early. Here is when I close the tab before a fair read.
Read moreIn my frontend screens, the questions you ask mid-problem are part of what I mark. Here is what changes the slice.
Read moreThe coding slice is the warm-up. Here are the follow-ups I use to judge ownership, failure modes, and shipping judgment.
Read moreHiring managers decide a live frontend pair early. Here is what I watch for in the first ten minutes — share, setup, and the first slice.
Read moreA frontend take-home is a short PR for a stranger. Here is what I actually open, mark, and reject — from scope and README to ugly paths and a five-minute run.
Read moreMake your portfolio, GitHub, and LinkedIn readable by recruiters, ATSs, search engines, and AI without turning them into a keyword dump.
Read moreI do not mark “solved it”. Here is what I actually mark in a 45-minute frontend screen — and how to practise it this week.
Read moreStop collecting courses. Here is the 2026 frontend interview stack I would actually use: scorecard, daily loop, optional question bank, LeetCode only when earned.
Read moreBehavioural rounds fail good engineers who sound like a template. Here is how to use STAR so the story is still yours, and how to practise it out loud this week.
Read moreGrinding LeetCode helps some loops. Most frontend screens test HTML, CSS, React, async, a11y, and how you narrate. Here is a better week of practice for UI roles.
Read moreLeetCode volume alone will not cover what most frontend screens actually test — here are seven skills that still matter in 2026.
Read moreBasic covers the daily loop. Pro adds the AI Trainer wedge for job-spec, algo, and behavioural prep.
Read moreInterview prep compounds when you show up every day — not the night before.
Read more