Learn Computer Stuff
Home / Infrastructure & Advanced Computing / Robotics Software Engineer
Infrastructure & Advanced Computing

Robotics Software Engineer

You write the software that makes a machine perceive where it is and move without hitting anything.

Degree usually expected Hard. Geometry, probability and control theory are load-bearing.


Can I actually do this?

Marked not no-degree-friendly, honestly: postings routinely ask for engineering, robotics or a related quantitative degree, and the linear algebra and probability behind perception and planning are genuinely required rather than decorative. People do enter from software or electronics with strong self-taught maths, and simulation makes practice possible without a robot. But this is one of the harder doors on this site and we will not pretend otherwise.

Who it suits. People who enjoy the point where mathematics becomes a physical movement.

Runway. Years, and the mathematics is not optional.

Coming from another job?

Coming from embedded work or computer vision? Those are the two realistic approaches, and each gives you half of it. Embedded Systems Engineer Computer Vision Engineer

Also advertised as

  • Robotics Engineer
  • Autonomy Engineer
  • Motion Planning Engineer

The route

Four stations, in order. Each one is a thing you finish before the next matters.

  1. Station one

    Learn it free

    Only the best few, deliberately. Every one of these is free to use — the pill on each card says exactly what is and isn't free.

    ROS 2 — the project repository

    Free to learn · no certificate

    The Robot Operating System, which most of this field is built on. Free and open source. Note: the documentation site at docs.ros.org was behind a bot check when we looked, so this points at the project's own repository, which serves the same entry point and reads without one.

    OpenCV — tutorials

    Free to learn · no certificate

    Perception in practice. Free and open source.

    The Embedded Rust Book

    Free to learn · no certificate

    Robots have microcontrollers underneath the clever parts. Free.

    See the full catalog in the explorer →

  2. Station two

    Attest strategically

    Nothing worth buying. Robotics hires on demonstrated systems, and simulation is free — you can show meaningful work without owning a robot. If the maths is the gap, close the maths; no certificate substitutes for it.

    Nothing here is worth paying for

    No credential needed

    Nothing worth buying. Robotics hires on demonstrated systems, and simulation is free — you can show meaningful work without owning a robot. If the maths is the gap, close the maths; no certificate substitutes for it.

  3. Station three

    Prove it

    A certificate says you passed a test. These say you can do the job.

    Something autonomous in simulation

    A robot that navigates, avoids and recovers in a simulator. Free to build, and it demonstrates the whole stack.

    A perception pipeline you tuned

    Show it failing on a hard case and what you did about it. Robotics demos always work; engineering is the failure cases.

    A safety behaviour you designed

    What the machine does when a sensor lies to it. This is the question that gets asked.

  4. Station four

    Get hired

    Search these exact titles

    • robotics software engineer
    • robotics engineer
    • autonomy engineer
    • perception engineer

    Who hires for this. Warehouse and industrial automation, agriculture robotics, autonomous vehicles, defence, and research institutes.

    Interviews test the mathematics behind perception and planning directly, which is why we have not marked this as an open no-degree route. That is our reading of how the role is advertised, not a verified hiring statistic.

    On salary

    We don't publish salary estimates. Numbers copied between blogs drift from reality, and a wrong number costs you real negotiating power. When we have a verified public source, it goes here with its date.


Where this route continues

· How we verify