Two tracks — pick one first
| Build track | Application track | |
|---|---|---|
| In one line | Build the robot | Make an existing robot do real work |
| Start from | Open-source body: structure, drives, control board, firmware | Commercial body + vendor SDK + demos |
| Core skills | Mechanical, motors and drives, motion control, embedded | SDK/ROS 2, calibration, upper-layer algorithms, integration |
| Typical courses | Mechanics, motor drives, embedded, motion control, simulation | ROS 2 apps, SLAM and navigation, vision and grasping, VLA |
| Output | A prototype that stands, walks and teleoperates | A working scenario task (code, parameters, calibration files) |
| Roles | Structure / drive / motion control / embedded | Robot application development, algorithms, integration |
| Employers | Robot-body companies, research institutes, hardware startups | Application companies, integrators, end users |
What this engineer does
- Build track: replicate an open-source body → remix structure and drives → reliability, cost and certification → producible product
- Application track: replicate vendor demos → change scenario and add algorithms → mapping, navigation, recognition, grasping/inspection → delivery and operations
Both tracks converge at productisation.
Where you go
Robot-body companies and hardware startups (build track); application companies, integrators and end users (application track); or turn a product into something sellable at Chuangsheng Works.
How you earn
Salary; licensing/share/equity for signed products (agreed by track).
Who it suits
- Mechanical/electronics background → build track
- Software/automation background → application track