Interview topics you can practice
Go, React, system design, and the other engineering subjects technical interviews actually cover. Each page is a path into the app.
- Go
Go interview questions
Go interviews rarely stop at syntax. They check whether you can reason about concurrency, interfaces, and the code you would ship.
- React
React interview questions
React interviews are less about writing a component and more about explaining why it renders, what you would memoize, and how you would structure state.
- System design
System design interview practice
There is rarely one perfect design. Interviews check whether you can name the trade-offs and walk through a system you would actually run.
- Databases
Database interview questions
Database rounds check whether you can pick a store, explain an index, and talk about what happens when two writes collide.
- APIs
API interview questions
API interviews are about the contract you would publish, not only the handler you would write.
- Concurrency
Concurrency interview questions
Concurrency interviews are less about naming primitives and more about explaining a race and how you would shut work down cleanly.
- Backend
Backend interview questions
Backend interviews go past writing a handler. They check whether you can talk about data, load, and failure.
- Frontend
Frontend interview questions
Frontend interviews are also more than writing components. They check the decisions you would make when the UI is real.
- Architecture
Software architecture interview questions
Architecture interviews check whether you can draw a boundary and live with it, not whether you can name a pattern.
- Performance
Performance interview questions
Performance interviews start with a symptom. They check whether you measure before you rewrite.
- Debugging
Debugging interview questions
Debugging interviews are a story: something is wrong, and they watch how you narrow it.