ZipRecruiter

Log In

1

Swarm Robot Jobs in Ohio (NOW HIRING)

NEURA Robotics

$125 - $150/hr

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 ...

BTAS

UAS Hardware Engineer

Dayton, OH · On-site

$115K - $151K/yr

Contribute to the development and evaluation of collaborative autonomous systems and swarm ... Experience: * 2-4 years of relevant engineering experience in UAS systems, robotics, embedded ...

BTAS, Inc.

UAS Hardware Engineer

Dayton, OH · On-site

$120K - $158K/yr

Contribute to the development and evaluation of collaborative autonomous systems and swarm ... Experience: * 2-4 years of relevant engineering experience in UAS systems, robotics, embedded ...

All JobsSwarm Robot JobsSwarm Robot Jobs in Ohio

Swarm Robot information

What is a swarm robot?

Swarm robots are groups of simple, relatively inexpensive robots that work together to accomplish tasks by following decentralized, collaborative behaviors inspired by social insects like ants or bees. Each robot operates using basic rules and local information, but collectively they can perform complex tasks such as exploration, mapping, or object transportation. This approach enhances flexibility, scalability, and robustness, making swarm robots useful in applications where adaptability and fault tolerance are important. Swarm robotics is a growing field in robotics research and engineering, with potential uses in agriculture, environmental monitoring, and search-and-rescue operations.

What are some common challenges faced when working on swarm robotics projects, and how can they be addressed?

Professionals working in swarm robotics often encounter challenges related to coordination, communication, and scalability. Ensuring reliable communication among a large number of robots can be complex, especially in dynamic environments. Additionally, developing algorithms that allow the swarm to adapt to new tasks or unexpected obstacles requires strong problem-solving skills. Collaborating closely with interdisciplinary teams—such as software engineers, hardware specialists, and researchers—can help address these challenges through regular testing, simulation, and iterative development.

What are the key skills and qualifications needed to thrive as a swarm robotics engineer, and why are they important?

To excel as a Swarm Robotics Engineer, you need a solid background in robotics, computer science, and algorithms, often supported by a relevant engineering degree. Experience with programming languages (such as Python, C++), robotics simulation tools (like ROS, Gazebo), and familiarity with multi-agent systems are crucial, along with certifications in robotics or AI being advantageous. Strong problem-solving, teamwork, and analytical thinking skills help you design and coordinate large-scale robot behaviors effectively. These competencies are essential for developing robust, scalable, and efficient swarm robotic systems that operate collaboratively in real-world environments.

What is the difference between Swarm Robot vs Robot Programmer?

AspectSwarm RobotRobot Programmer
CredentialsBasic robotics knowledge, programming skillsAdvanced programming certifications, robotics degrees
Work EnvironmentResearch labs, manufacturing, field testingSoftware development environments, offices, labs
Industry UsageSwarm robotics, automation, researchRobotics software development, automation systems
Search IntentUnderstanding swarm robotics applicationsLearning robot programming skills

Swarm Robots are physical devices used in automation and research, focusing on collective behavior. Robot Programmers develop software to control robots, including swarm systems. While both roles involve robotics, Swarm Robots are hardware-focused, whereas Robot Programmers specialize in coding and software development for robotic systems.

What are popular job titles related to Swarm Robot jobs in Ohio?

For Swarm Robot jobs in Ohio, the most frequently searched job titles are:

What job categories do people searching Swarm Robot jobs in Ohio look for?

The top searched job categories for Swarm Robot jobs in Ohio are:

What cities in Ohio are hiring for Swarm Robot jobs?

Cities in Ohio with the most Swarm Robot job openings:

Swarm Robot jobs near you

Fleet Orchestration Engineer - Neuraverse (human)

NEURA Robotics

On-site

$125 - $150/hr

Other

Posted 6 days ago

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

Apply