Blog
No question lists to memorise. What interviewers are actually listening for, why the follow-up question decides most rounds, and how to prepare for the format you are facing rather than the one you read about.
Try a practice interviewA practical guide for working engineers: which round you are actually in, what interviewers really score, and how to answer so the follow-up goes your way.
How AI screens, live coding, take-homes and system design rounds actually run.
What actually happens in an automated technical screen, how it differs from a human phone screen, why strong engineers fail it, and how to prepare for one.
Eight recurring technical interview styles, what each one is really testing, and how to work out which one you are about to sit.
The three formats reward different skills, and preparation transfers badly between them. What each one scores, and where to spend your limited hours.
The six things a system design interviewer is listening for, the order to cover them in, and the failure modes that sink otherwise strong candidates.
What separates a senior answer from a correct one — and how interviewers test for it.
Eight interview questions with two correct answers each, one that reads junior and one that reads senior, plus what the interviewer asks next.
What strong senior candidates do differently: how they scope, what they volunteer, how they handle pushback, and how the level decision actually gets made.
The second question decides most technical rounds, because it is built from your own words. How drilling works, and how to prepare for a question nobody can predict.
It depends is usually the right answer and the worst way to say it. A four-part structure for committing to a decision while showing the nuance behind it.
What gets asked in React, Node, databases, security and AI engineering rounds.
The React topics that separate senior candidates: what really causes a re-render, effects, keys, state ownership and why a fast app still feels slow.
The event loop, blocking, streams and backpressure, error handling and memory leaks: the Node topics senior interviews keep returning to, and why.
Indexes, query plans, N+1, transactions and isolation, locking and zero-downtime migrations: what senior backend interviews actually test.
Auth, password storage, tokens, injection, XSS and CSRF, secrets and rate limiting: what a security-flavoured interview expects from a backend engineer.
What AI engineering interviews test now that everyone has shipped a demo: retrieval quality, evaluation, cost and latency, and handling untrusted text.
You find the gaps in your answers by being asked about them out loud, and then being asked again about whatever you just said. That is what a practice interview here does. The first one is free.