Nineteen domains have an interview/ folder โ€” the ones below. The theory and engineering tracks added since (engineering/, robotics/, and the CS-theory spine from discrete-math through programming-language-theory) deliberately donโ€™t: those are [reference] material with no reps behind them, and an interview bank for a subject you havenโ€™t practised would be memorisation, not preparation. The place to start with those is project-ideas, not a question list. Same format throughout, generalised from the arete interview notes: the question, what a strong answer covers, and the detail worth adding that separates memorised from understood. ๐Ÿ”ฅ marks questions that come up constantly.

The banks

DomainFocusFiles
Backend / Nodebuilt from a real interview โ€” p99 spikes, AZ vs deploy, retry storms, Promise.all, Buffer2
Networkinglayering โ†’ TCP โ†’ TLS โ†’ debugging scenarios4
JavaJVM, GC, memory model, concurrency โ€” the low-latency round3
Pythonthe data model and the gotchas โ€” mutable defaults, the GIL, generators, EAFP1
Architecturethe system design round + distributed systems depth2
DSAhow to run a coding round + the pattern lookup1
Databasesindexes, isolation levels, query plans, migrations1
OSprocesses, virtual memory, syscalls, scheduling1
DevOpsLinux, containers, CI/CD, observability, incidents1
ConceptsAPIs, auth, OAuth + patterns, code review, testing theatre2
Securityinjection classes, crypto, SSRF, defence, IR1
AI/MLRAG, agents, evals, prompt injection + ML fundamentals2
Game Devvectors, fixed timestep, frame budget, collision phases, lag compensation, ECS1
FrontendReact model + the JS/TS language round + state, data, a11y, RSC3
Hardwaredecoupling, I2C/SPI, interrupts, board bring-up + RF, MQTT, battery life2
Web3the double-spend problem, storage vs memory, the three reentrancy variants, flash loans, where the money actually went1
Mobileprocess death vs rotation, offline-first, the radio tail, permissions, no-rollback release1
Data Engineeringoperational vs analytical, ELT, CDC, idempotency, batch vs streaming, dimensional modelling1
Data Analysisthe SQL screen (window functions, fan-out), the diagnostic case, metrics, communicating a decision1

Plus the project-specific bank: arete/interview/ โ€” the original, and still the best template because every answer is anchored in code you actually wrote.

NextVibe has its own bank too: nextvibe/interview/ โ€” the largest one, including 06: wishlist, spin the wheel, multi-tenancy (race conditions, row locks, public vs private data, and four behavioural stories).

How to use these

Cover the answer. Say it out loud. Then compare. Recognition feels like knowledge and isnโ€™t โ€” the gap between โ€œI could follow thatโ€ and โ€œI could say thatโ€ is exactly what an interview measures.

Two failure modes these banks are written against:

  1. Reciting definitions. Every answer here has a โ€œdetail worth addingโ€ precisely because the definition alone is table stakes.
  2. Not committing. โ€œIt dependsโ€ is only good when followed by โ€œso Iโ€™d choose X because Y.โ€ An interviewer canโ€™t distinguish thoughtful hedging from not knowing.

If youโ€™re preparing for a specific role

Low-latency / systems (the current target in the Primetechie path):
Java: JVM & concurrency โ†’ OS โ†’ TCP โ†’ coding round โ†’ dist-sys depth

Backend / platform (Node):
production debugging โญ โ†’ Node runtime โ†’ APIs & auth โ†’ databases โ†’ system design โ†’ Linux & containers

โญ Start there โ€” itโ€™s reconstructed from a real interview, so itโ€™s the only file here that isnโ€™t a guess at what gets asked.

AI engineering:
AI engineering โ†’ ML fundamentals โ†’ databases (vector search) โ†’ APIs

Embedded / hardware:
Electronics & embedded โ†’ RF & IoT โ†’ OS (memory, interrupts) โ†’ TCP
โญ Lead with the IoT Bridge PCB โ€” a board you designed beats any prepared answer.

The five questions worth over-preparing

Across every bank, these carry the most weight per minute spent:

  1. โ€œWalk me through a p99 latency investigation.โ€ (Java Q11) โ€” the answer is a method, and it spans GC, locks, and the transport layer.
  2. โ€œThe service is down โ€” what do you check?โ€ (Networking Q1) โ€” bisecting layers, the single most transferable skill in this vault.
  3. โ€œDesign X.โ€ (Architecture) โ€” requirements before boxes, every time.
  4. โ€œHow would you evaluate this?โ€ (AI Q4) โ€” separates engineers from demo-builders.
  5. โ€œHow do you safely migrate a huge table?โ€ (Databases Q10) โ€” expand/migrate/contract; the fastest way to spot someone whoโ€™s shipped.
โ†‘ Back to Kingsley's Knowledge Base