RobotGuide

Track 2 / 4

System software

Middleware, real-time systems, architecture, integration. Few openings but chronically scarce: the best entry point for a software background.

18 topics · about 685 hours end to end, 14 of them to master level.

Stage 3 is the watershed of this track: D13 explains how ROS 2 schedules work internally, D14 explains which layers can be swapped and what each swap costs. Application-only developers can stop at D13 (35 h); platform and real-time-control work cannot skip the 45 h of D14.

Algorithm System software Embedded & controls Mechanical

Learning order

Walk the stages in order: each stage is the prerequisite of the next. Skipping ahead is paid back with interest around stage three.

Topic names link to their full topic page on the Chinese edition: what to learn, how to verify you have learned enough, the common mistakes, and an interactive figure you can drag.

The classic trap

The classic mistake on this line is "only learning ROS 2". Architecture interviews test judgment: latency budgets, fault isolation, degradation strategy — none of that comes from tutorials; it needs deliberate practice.

Jobs this track leads to

Pay figures are JD-stated ranges from Chinese recruiting platforms (CNY thousands per month × months per year). They describe the China market this curriculum is grounded in, not a promise anywhere.

Labs to build along the way

Interactive benches you can drag directly in the browser, on the Chinese edition.