# Learning Paths (/docs/learning-paths)



The Software Engineering Map describes **what territory exists**. Learning paths answer a different question: **what sequence is useful for a particular engineering goal?**

Paths are curated, not generated from popularity or page count. They may include concepts the Atlas has not covered yet because removing an important gap would make the mental model less honest.

Available content links are derived from canonical MDX placement, so learning-path data does not maintain a second list of lesson URLs.

<LearningPathsOverview />

## Choose paths by outcome [#choose-paths-by-outcome]

Use **Modern Web Systems** to connect browser, network, rendering, frontend, and backend boundaries. Use **Backend Systems** for request processing, data correctness, async work, and distributed failure. Use **Cloud Architecture for Software Engineers** to connect application design to infrastructure and operations. Use **AI-Native Software Engineering** to design repositories and verification loops for humans and coding agents working together.