Senior does not mean maximum depth in everything
A Senior engineer is expected to make strong decisions in their primary area and navigate adjacent domains. That does not mean expert knowledge of every technology listed in a job description.
Depth should depend on the technology's role in the job, how often it is used, and which decisions you will make independently.
Four levels of depth
- Fundamentals: explain the purpose, key terms, and common scenarios.
- Practical: apply the technology and solve common tasks.
- Advanced: understand production risks, limitations, and architectural trade-offs.
- Expert: know the internals, complex failure modes, and diagnostic methods.
Your primary stack requires greater depth
For a Senior Node.js Developer, Event Loop behavior, memory, threads, and performance diagnostics naturally belong at Advanced or Expert depth. For Redis, confidently discussing caching, TTL, and common failure modes at Practical or Advanced depth may be enough.
Treat the job description as a signal, not absolute truth
Repeated technologies and responsibilities raise a topic's priority. However, a long tool list often describes the company's entire system rather than one engineer's daily work. Validate requirements against the role's expected tasks.
Revise the map based on your answers
Your initial depth is a hypothesis. If fundamental cards are difficult, return to the basics temporarily. If you answer Advanced questions confidently, add internals and complex scenarios.
A good program does not lock a level forever. It helps you spend time where the next step will genuinely improve the quality of your answer.