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 interviewTechnical interview prep for working engineers: which round you are in, what the questions really test, and how to answer so the follow-up goes your way.
How AI screens, live coding, take-homes and system design rounds actually run.
Where AI interview assistants are accurate, where they quietly get it wrong, a ten-minute test you can run on any of them, and whether one is worth it.
What happens in a one-way or AI video interview, how HireVue-style recorded screens work, and how engineers can prepare for answers nobody follows up on.
What an AI coding interview looks like for software engineers, what changes when the reviewer is AI, and how to prepare for reading, fixing and explaining code.
Real-time AI assistants promise to feed you answers during an interview. Why they fail hardest in the round they're sold for, and what works instead.
The five AI interview platforms you are most likely to meet as a software engineer, what each round asks of you, and the one thing all of them reward.
What happens in an AI interview for engineers, how an AI interviewer differs from a human phone screen, why strong candidates fail it, and how to prepare.
Eight recurring technical interview styles, what each one is really testing, and how to work out which one you are about to sit.
What a live coding interview, a take-home and an AI screen each score, why preparation transfers badly between them, and where to spend your hours.
Common system design interview questions, the six things the interviewer is scoring in each, the order to cover them in, and the mistakes that sink candidates.
What separates a senior answer from a correct one, and how interviewers test for it.
Reading teaches you to recognise an idea. Being asked teaches you to produce it. How to use interview questions as a study method when no job hunt is on.
Naming a tool in an answer sets the next question. How interviewers test the technologies you list, and the four lines to prepare under each one.
Eight senior software engineer interview questions, each answered twice, once the junior way and once the senior way, 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, API design, databases, security and AI engineering rounds.
Nine AI engineering concepts every candidate should understand, explained in plain language with the one point interviewers want to hear about each.
The Python questions backend candidates really get: the GIL, async versus threads, mutable defaults, generators, ORM queries and what keeps an object alive.
The same backend role interviews differently in Python, Go and Java. What each round assumes, the questions each one reaches for, and what transfers.
The JavaScript questions senior candidates get: event loop ordering, closures, this binding, prototypes, and predicting what actually runs.
The DevOps questions senior candidates get: rolling back past a migration, what a health check gates, which alerts should page, SLOs, and incidents.
The testing questions senior candidates get: what to mock, why a test is flaky, what coverage actually measures, and testing behaviour instead of implementation.
The TypeScript questions senior candidates get: unknown at the boundary, structural typing, discriminated unions, satisfies, and where the checker is unsound.
Idempotency, pagination, versioning and error semantics: the four places an API answer stops being correct and starts sounding senior.
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.