Curated for this specific career level.
Level path
Backend Practitioner
BE
Own features and services with solid implementation judgment across neighboring layers.
Concepts explicitly listed in this level.
Concepts span multiple tracks and layers.
Job description signals Typical responsibilities ↓
- Design and implement APIs, service logic, persistence boundaries, and core business workflows.
- Improve backend performance, reliability, data correctness, security, and operability.
- Own database access patterns, service integrations, and production debugging for backend systems.
- Own features end to end from design through implementation, testing, release, and support.
- Make local technical tradeoffs and explain them clearly to teammates.
- Improve reliability, maintainability, and observability of the systems you touch.
- Collaborate with product, design, QA, operations, and adjacent engineering teams.
Track / layer mastery Concept coverage by layer ↓
Software
24 concepts
Product
6 concepts
Operations
3 concepts
Software
160 concepts
Operations
31 concepts
Product
31 concepts
Management
19 concepts
Data
3 concepts
Theory
3 concepts
Learning scope Concepts by learning area ↓
Specific to this level
Concepts introduced by this level
Level concepts
Web & APIs
Understand how clients and servers communicate through stable service interfaces.
Level concepts
Databases
Store, query, and reason about persistent data correctly and efficiently.
Level concepts
Backend Design
Organize service code and boundaries so backend systems can evolve safely.
Level concepts
Service Development
Build the capabilities needed for this area.
Cumulative level expectation
All concepts expected at this level
Inherited path
Coding Foundations
Developers begin by learning to translate requirements into working, readable code.
Inherited path
Developer Tooling
Daily development depends on version control, language tooling, static checks, and repeatable local workflows.
Inherited path
Testing & Debugging
A developer owns not only writing code, but proving that it behaves as intended.
Inherited path
Software Systems Basics
Even implementation-focused developers need a working vocabulary for clients, servers, interfaces, web requests, and the lifecycle surrounding a change.
Inherited path
Employment Basics
Technical candidates benefit from understanding who employs them, how they are paid, and which terms govern the working relationship.
Inherited path
Programming Foundations
Learn the basic building blocks used to express behavior in code.
Inherited path
Software Design
Structure code so it remains readable, testable, and maintainable as it grows.
Inherited path
Data & Persistence
Understand how applications store, retrieve, and protect durable state.
Inherited path
Architecture & Systems
Design systems that handle growth, latency, failure, and multiple communicating components.
Inherited path
Production Awareness
Know how software is built, deployed, observed, and recovered in production.
Inherited path
Web & APIs
Understand how clients and servers communicate through stable service interfaces.
Inherited path
Databases
Store, query, and reason about persistent data correctly and efficiently.
Inherited path
Backend Design
Organize service code and boundaries so backend systems can evolve safely.
Inherited path
Production Backend
Understand how backend services are packaged, deployed, observed, and operated.
Inherited path
Application Design
Mid-level developers own complete features and make local design choices inside an established architecture.
Inherited path
Runtime & Data
Feature ownership requires practical knowledge of runtimes, memory management, and relational persistence.
Inherited path
Delivery & Collaboration
Professional development includes the complete implementation loop, not only editing source files.
Path concepts
Service Development
Build the capabilities needed for this area.