The in-school timeline
Same four years: some graduates hold three projects they can present for 30 minutes, others hold a transcript. The difference is not cleverness — it is whether each year had a concrete output goal.
Freshman year
Lay foundations; don't rush to touch robots
Math (linear algebra, calculus) + one language (C++ or Python) + build a small car or servo gimbal by hand. The goal is 'being able to build something that moves on your own' and building intuition.
Sophomore year
Catch up on robotics; join a team or a lab
Theoretical mechanics / intro to robotics + modern C++ + join a robotics team (RoboMaster etc.) or enter a lab. The goal is 'owning one module in a real project'.
Junior year
Pick a track, build deep projects, find a summer internship
Pick one of the four tracks and bring its core topics to L2. Build one project you can present for 30 minutes. The summer internship is the key milestone — many offers start there.
Senior year, first semester
Turn your thesis into a portfolio piece; sprint through autumn recruiting
Point your thesis topic straight at the target role. Rewrite the 'course projects' on your resume into 'engineering experience'. Autumn recruiting (Sep-Nov) is the main battlefield.
First-year master's
Go deep on your direction and produce results
Algorithm track: read top-conference papers, reproduce them, find novelty. Engineering track: join industry joint projects and build real systems. Don't just stay in the lab on either path.
Second-year master's
Internship + papers + job hunt in parallel
Aim to convert your summer internship into a return offer. Wrap up both papers and engineering projects. This year determines your starting point at graduation.
Already graduated?
Compress the sequence into six months: month 1, language and math; months 2–3, robotics fundamentals + real-time systems; months 4–5, one complete project; month 6, applications. Students have time to fail cheaply; working people have engineering experience to trade on — do not run on each other's schedule.