Learning & teaching · SCENARIO ROADMAP

Build a robotics career-transition portfolio

Turn existing skills into a small set of inspectable robotics projects and role-specific evidence.

Reviewed October 26, 2026 · Editorial learning and project guidance. Professional means project depth, not an accredited qualification.

THE DESTINATION

What you will produce

A polished project dossier and a role-specific skills gap plan. Make the work reviewable by someone who did not build it.

Before you begin

Starting knowledge

  • List existing programming, mechanical, electrical or domain skills.
  • Choose one target role before choosing a large hardware purchase.

Equipment & environment

Use publicly shareable simulation and small datasets. Keep confidential employer information out of the portfolio.

No fixed completion time: use the evidence gates below to decide when to advance. Resource links open the botstest directory entry; check its publisher documentation for the exact version and configuration.

01

Beginner

Choose a role and one tractable project

Translate a job direction into observable technical work.

Learn in this order

  1. Software, mechatronics, research and operations role boundaries
  2. Task briefs and evidence of contribution
  3. Basic robot-system vocabulary

Put it into practice

  1. Map your existing skills to a small robot task.
  2. Choose a simulation project with an input, output and measurable completion rule.
Produce this

A role map and a one-page portfolio project brief.

Ready for the next step when…

Resources for this stage

IFR Robot Definitions →

Establish vocabulary and distinguish robot types before choosing a platform.

CMU Robotics Institute →

Explore research areas and educational material to position a robotics study or learning plan.

Webots →

Create a small simulated robot and inspect sensor/controller behavior without purchasing hardware.

02

Intermediate

Build evidence of integration and debugging

Show how you investigate a problem and improve the system.

Learn in this order

  1. ROS components, recordings and configuration
  2. Issue logs and controlled comparisons
  3. Readable setup and test instructions

Put it into practice

  1. Implement a navigation or manipulation example in simulation.
  2. Record one failure, its diagnosis and a test that exposes it.
Produce this

A working project with an issue log and reproducible test.

Ready for the next step when…

Resources for this stage

ROS 2 →

Follow the official middleware learning path; use documentation matching your installed distribution.

Nav2 →

Study navigation components, maps, localization, behavior orchestration and recovery in the matching release.

MoveIt →

Explore robot motion planning, planning scenes and manipulation integration in a version-matched example.

03

Professional

Prepare a professional technical handover

Make the work reviewable by someone who did not build it.

Learn in this order

  1. Architecture, limitations and ownership
  2. Performance evidence and uncertainty
  3. Licenses, attribution and interview communication

Put it into practice

  1. Ask a peer to run the project from a clean setup.
  2. Prepare a short technical walkthrough of an engineering trade-off.
Produce this

A polished project dossier and a role-specific skills gap plan.

Ready for the next step when…

Resources for this stage

Foxglove →

Inspect recorded robot signals and build views that expose timing and system failures.

Rerun →

Visualize spatial observations and compare them with model and trajectory outputs.

Modern Robotics →

Study the mechanics, coordinate frames, kinematics and control foundations relevant to the exercise.

Common pitfalls

  • Collecting many unfinished tutorial repositories.
  • Claiming production or research expertise from a single demonstration.

Where to go next

Use the development and research roadmaps to deepen the weakest skill exposed by your portfolio review.

Explore other learn paths →