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
| Domain | Focus | Files |
|---|---|---|
| Backend / Node | built from a real interview โ p99 spikes, AZ vs deploy, retry storms, Promise.all, Buffer | 2 |
| Networking | layering โ TCP โ TLS โ debugging scenarios | 4 |
| Java | JVM, GC, memory model, concurrency โ the low-latency round | 3 |
| Python | the data model and the gotchas โ mutable defaults, the GIL, generators, EAFP | 1 |
| Architecture | the system design round + distributed systems depth | 2 |
| DSA | how to run a coding round + the pattern lookup | 1 |
| Databases | indexes, isolation levels, query plans, migrations | 1 |
| OS | processes, virtual memory, syscalls, scheduling | 1 |
| DevOps | Linux, containers, CI/CD, observability, incidents | 1 |
| Concepts | APIs, auth, OAuth + patterns, code review, testing theatre | 2 |
| Security | injection classes, crypto, SSRF, defence, IR | 1 |
| AI/ML | RAG, agents, evals, prompt injection + ML fundamentals | 2 |
| Game Dev | vectors, fixed timestep, frame budget, collision phases, lag compensation, ECS | 1 |
| Frontend | React model + the JS/TS language round + state, data, a11y, RSC | 3 |
| Hardware | decoupling, I2C/SPI, interrupts, board bring-up + RF, MQTT, battery life | 2 |
| Web3 | the double-spend problem, storage vs memory, the three reentrancy variants, flash loans, where the money actually went | 1 |
| Mobile | process death vs rotation, offline-first, the radio tail, permissions, no-rollback release | 1 |
| Data Engineering | operational vs analytical, ELT, CDC, idempotency, batch vs streaming, dimensional modelling | 1 |
| Data Analysis | the SQL screen (window functions, fan-out), the diagnostic case, metrics, communicating a decision | 1 |
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:
- Reciting definitions. Every answer here has a โdetail worth addingโ precisely because the definition alone is table stakes.
- 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:
- โWalk me through a p99 latency investigation.โ (Java Q11) โ the answer is a method, and it spans GC, locks, and the transport layer.
- โThe service is down โ what do you check?โ (Networking Q1) โ bisecting layers, the single most transferable skill in this vault.
- โDesign X.โ (Architecture) โ requirements before boxes, every time.
- โHow would you evaluate this?โ (AI Q4) โ separates engineers from demo-builders.
- โHow do you safely migrate a huge table?โ (Databases Q10) โ expand/migrate/contract; the fastest way to spot someone whoโs shipped.
Related
- Vault README ยท The Primetechie Path ยท Project Ideas
- The strongest answers cite your own code. projects/ is the raw material โ have one crisp story per project.
Software engineering
Infrastructure & security
AI & data
Computer science
Hardware & engineering