Developer Interview Preparation
Real interview questions with worked answers across 40 technologies — and structured paths for the role you are actually applying for. Free, no sign-up.
Prepare by role
Each path orders the technologies the way interviews actually weight them.
Backend Developer
Backend interviews weight data modelling and failure behaviour heavily. Being able to write a query is assumed; explaining what happens when a downstream service is slow, or why a request hangs, is what actually gets assessed.
5 stages · sql, nodejs, express…
Data / ML Engineer
Data interviews split into two halves: SQL and Python fluency, then framework depth. The SQL half is where most candidates are filtered out, and it is also the most learnable — window functions and query plans repay preparation more than anything else here.
5 stages · sql, python, pandas…
DevOps Engineer
DevOps interviews focus on operational reasoning: what happens during a deploy, how a rollout fails, and how you would find out. Tool familiarity is table stakes — the differentiator is being able to describe failure modes and recovery.
5 stages · docker, kubernetes, git…
Frontend Developer
Frontend interviews test the language before the framework. Most candidates who struggle do so on JavaScript fundamentals — closures, the event loop, coercion — not on React specifics. This path works through the language first, then TypeScript, then the framework layer.
5 stages · javascript, typescript, react…
Full-Stack Developer
Full-stack interviews go broad rather than deep, but they do probe the seams — how data moves between the database and the browser, and where the responsibility for validation, caching and error handling sits. Expect to be asked to justify choices on both sides.
5 stages · javascript, typescript, react…
Curated topics
Hand-written question sets, each with a worked answer.
Questions by technology
Worked questions and answers, then a timed quiz to check what stuck.