1

Robotic Motion Planning Engineer Jobs in Ohio (NOW HIRING)

$120 - $160/hr

Looks like Open-RMF contributors, AMR fleet engineers (Locus Robotics, Otto Motors, MiR fleet ... RSS/ICRA/IROS publications in MRTA, multi-robot motion planning, swarm robotics, or fleet ...

New

$180 - $240/hr

... the motion planning pipeline that generates the trajectories robots execute, and the industrial device servers that connect robots to factory automation systems. As Staff Engineer for our Robot ...

New

Senior Robotics Software Engineer

Columbus, OH · On-site

$118K - $156K/yr

We're seeking a Senior Robotics Software Engineer who thrives on hard systems problems. Welding is ... motion planning - inverse kinematics and trajectory planning for robotic manipulators - and ...

Senior Robotics Software Engineer

Columbus, OH · On-site

$118K - $156K/yr

We're seeking a Senior Robotics Software Engineer who thrives on hard systems problems. Welding is ... motion planning - inverse kinematics and trajectory planning for robotic manipulators - and ...

$110 - $170/hr

Your Mission & Challenges As a Proof of Concept Engineer for Mobile Service Robots, you will lead ... motion planning for mobile robotic systems. * Experience working with multi‑sensor perception ...

next page

Showing results 1-20

Robotic Motion Planning Engineer information

See Ohio salary details

$27.6K

$100.4K

$160.7K

How much do robotic motion planning engineer jobs pay per year?

As of Sep 3, 2026, the average yearly pay for robotic motion planning engineer in Ohio is $100,398.00, according to ZipRecruiter salary data. Most workers in this role earn between $79,400.00 and $120,700.00 per year, depending on experience, location, and employer.

What does a robotic motion planning engineer do?

A Robotic Motion Planning Engineer is responsible for designing algorithms that enable robots to move efficiently and safely within their environment. This involves creating paths or trajectories for robots to follow while avoiding obstacles and optimizing for speed, energy, or other factors. They use knowledge from robotics, computer science, and mathematics to develop software that allows robots to perform complex tasks autonomously. These engineers often work with sensors, simulation software, and real-world robotic systems to test and refine their motion planning solutions.

What are the key skills and qualifications needed to thrive as a robotic motion planning engineer, and why are they important?

To thrive as a Robotic Motion Planning Engineer, you need a solid background in robotics, computer science, and mathematics, typically supported by a relevant bachelor's or master's degree. Familiarity with tools such as ROS (Robot Operating System), Python/C++, and simulation platforms like Gazebo, as well as experience with motion planning algorithms, is essential. Strong problem-solving abilities, effective communication, and teamwork skills set candidates apart in this field. These skills are crucial for developing reliable, efficient, and safe robotic systems that can operate in complex real-world environments.

What are some common challenges faced by robotic motion planning engineers when working on real-world robot deployment?

Robotic Motion Planning Engineers often encounter challenges translating simulation results to real-world environments due to factors like sensor noise, hardware limitations, and unpredictable obstacles. Ensuring that planned paths are both efficient and safe in dynamic settings requires close collaboration with hardware engineers and field testing teams. Additionally, balancing computational efficiency and motion accuracy, especially for complex robots or crowded spaces, is a frequent hurdle. Overcoming these issues typically involves iterative tuning, robust software development, and interdisciplinary teamwork.

What is the difference between Robotic Motion Planning Engineer vs Robotic Software Engineer?

AspectRobotic Motion Planning EngineerRobotic Software Engineer
Primary FocusDeveloping algorithms for robot path planning and navigationDesigning and implementing software for robotic systems
Required SkillsRobotics algorithms, motion planning, C++, PythonSoftware development, robotics frameworks, C++, Python
Work EnvironmentResearch labs, robotics companies, industrial automationRobotics companies, tech firms, automation industries
Common CertificationsRobotics certifications, programming certifications

Robotic Motion Planning Engineers focus on creating algorithms for robot navigation, while Robotic Software Engineers develop broader software solutions for robotic systems. Both roles require programming skills and often overlap in work environments, but their core responsibilities differ in scope and specialization.

Are robotic motion planning engineers in high demand?

Robotic motion planning engineers are in high demand due to the growth of automation, robotics, and AI across industries such as manufacturing, healthcare, and logistics. Their expertise in algorithms, kinematics, and programming tools like ROS and MATLAB makes them valuable as companies seek to develop advanced robotic systems and autonomous vehicles.

Do robotic motion planning engineers get paid well?

Robotic motion planning engineers typically earn competitive salaries due to their specialized skills in robotics, algorithms, and programming. Salaries vary based on experience, education, and industry, but they are generally above average compared to many engineering roles. Advanced knowledge of robotics frameworks and tools can also influence compensation levels.

What are popular job titles related to Robotic Motion Planning Engineer jobs in Ohio?

For Robotic Motion Planning Engineer jobs in Ohio, the most frequently searched job titles are:

What cities in Ohio are hiring for Robotic Motion Planning Engineer jobs?

Cities in Ohio with the most Robotic Motion Planning Engineer job openings:

Fleet Orchestration Engineer - Neuraverse (human)

NEURA Robotics

On-site

$120 - $160/hr

Other

Posted 2 days ago

New


Job description

Your Mission & Challenges
  • Multi-robot task allocation algorithms: auction-based (CBBA, market-based), MILP solvers for offline planning, Hungarian for simple bipartite matching, robot-capability matching, deadline-aware scheduling, priority queuing

  • Mission decomposition: facility-level goal ("deliver 50 trays from kitchen to floor 3 by 18:00") → per-robot behaviour-tree skill bundles + cross-robot dependency graph + handoff point definitions

  • Fleet traffic management beyond static geofencing: dynamic corridor allocation, intersection arbitration, shared resource pools (charging docks, narrow passages, elevators, doors), preemption rules

  • Cooperative-task primitives: synchronised place-pick handoffs (Robot A places, Robot B picks at coordinated time), coordinated bimanual across two physical robots holding the same object, leader/follower formations, multi-robot peg-in-hole

  • Fleet-level performance management: throughput dashboards, robot utilisation balancing, SLA tracking, predictive task rerouting when one robot slows down

  • VDA 5050 master mode: NEURA fleet orchestrator dispatches to NEURA + third-party robots in NEURA-managed humanoid/service facilities (hospitality, healthcare, mixed-fleet demos)

  • VDA 5050 client interop testing: confirm NEURA robots integrate cleanly with third-party fleet management systems (Open-RMF, Otto, MiR, Symovo) for industrial deployments — protocol layer owned by Robot Connectivity Engineer

  • Expose atomic skill primitives (MoveArmTo, Grasp, Release, Insert, etc.) as typed NodeGraph nodes — co-reviewed with platform Motion Planning Engineers

  • Skill primitive API surface design: port schemas, error types, pre/postcondition contracts for third-party developers

  • Pre-deployment behaviour-tree simulation in the Cognitive Twin: simulating full skill trees before on-robot deployment — Digital Twin & Multi-Sim Engineer provides the simulation infrastructure

  • NodeGraph node templates for cooperative-task primitives (the orchestrator's execution vocabulary)

What we can look forward to
  • Multi-robot systems background as the primary axis — has shipped task allocation, fleet coordination, or multi-robot orchestration in production. Looks like Open-RMF contributors, AMR fleet engineers (Locus Robotics, Otto Motors, MiR fleet, Symbotic, Geek+, Boston Dynamics Spot coordinator), or industrial automation FMS engineers (Dematic, Vanderlande, Swisslog)

  • Multi-robot task allocation algorithm fluency: auction-based, MILP, Hungarian, market-based; understanding of NP-hardness and approximation trade-offs in MRTA problems

  • Distributed systems engineering: consensus, leader election, eventual consistency, fault recovery — the orchestrator is a distributed system at heart

  • VDA 5050 (v2.0+) protocol-level fluency: order, instantAction, state, visualization messages; master and client mode

  • BehaviorTree.CPP v4 and Groot2 proficiency for the NodeGraph SDK side of the role

  • Python and C++; comfort with optimisation libraries (OR-tools, Gurobi, CPLEX) for algorithm prototyping

Nice to Have
  • Academic background in multi-robot systems: RSS/ICRA/IROS publications in MRTA, multi-robot motion planning, swarm robotics, or fleet coordination

  • Open-RMF maintainer or significant contributor — fleet_adapter authoring, dispatcher implementation, RMF Demos

  • Cooperative manipulation experience: bimanual across two physical robots, multi-robot assembly, leader/follower

  • Per-customer FMS adapter experience: writing integrations to plug NEURA robots into existing third-party fleet managers (Otto, MiR, Locus, Symovo)

  • Motion planning familiarity (MoveIt2, OMPL, or equivalent) sufficient to evaluate planner behaviour in pre-deployment simulation

  • Formal verification or model checking for behaviour tree skill trees

  • ROS 2 (Jazzy or Humble) — useful for ROS 2-based fleet tooling integration, but not a prerequisite for this role; multi-robot systems expertise and distributed systems depth matter more

#J-18808-Ljbffr