ZipRecruiter

Log In

1

Orchestration Jobs in Ohio (NOW HIRING)

NEURA Robotics

$120 - $160/hr

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

Accenture

$100 - $130/hr

Product Orchestration: Partner with business and technical stakeholders to frame problems, align priorities, and translate needs into orchestrated AI workflows. * Agent Architecture & Engineering:

next page

Showing results 1-20

All JobsOrchestration JobsOrchestration Jobs in Ohio

Orchestration information

See Ohio salary details

$10

$68

$89

How much do orchestration jobs pay per hour?

As of Sep 6, 2026, the average hourly pay for orchestration in Ohio is $68.05, according to ZipRecruiter salary data. Most workers in this role earn between $65.34 and $77.45 per hour, depending on experience, location, and employer.

What is orchestration in the context of IT and business operations?

Orchestration refers to the automated arrangement, coordination, and management of complex computer systems, middleware, and services. In IT, orchestration is key for streamlining workflows, especially in cloud computing and containerized environments, ensuring that different services and applications work together seamlessly. It helps businesses efficiently deploy, manage, and scale applications by automating repetitive tasks and optimizing resource utilization. Orchestration tools, such as Kubernetes or Apache Airflow, are commonly used to manage these processes. Ultimately, orchestration improves efficiency, reduces manual errors, and enhances IT agility.

How does an orchestration engineer typically collaborate with development and operations teams to streamline workflow automation?

Orchestration engineers work closely with both development (Dev) and operations (Ops) teams to design and implement automated workflows that manage complex systems and application deployments. They facilitate communication between teams by translating business requirements into technical automation scripts and ensuring seamless integration of various tools and platforms. Daily responsibilities often include troubleshooting deployment issues, optimizing automation pipelines, and maintaining documentation. This collaborative approach not only reduces manual intervention but also accelerates delivery cycles and improves system reliability.

What are the key skills and qualifications needed to thrive as an orchestration engineer, and why are they important?

To thrive as an Orchestration Engineer, you need a solid background in IT infrastructure, automation, and cloud technologies, often supported by a degree in computer science or related field. Experience with orchestration tools such as Kubernetes, Docker Swarm, Ansible, or Terraform, as well as relevant certifications (e.g., Certified Kubernetes Administrator), is typically required. Strong problem-solving skills, effective communication, and the ability to collaborate across teams are vital soft skills. These competencies are crucial for efficiently automating complex workflows, ensuring system reliability, and supporting scalable, agile IT environments.

What is the difference between Orchestration vs Automation?

AspectOrchestrationAutomation
DefinitionCoordination of multiple automated processes to achieve a complex goalExecution of a single task or process automatically
ScopeIntegrates various systems and workflowsFocuses on individual tasks
ComplexityHandles complex, multi-step workflowsTypically simple, repetitive tasks
ToolsOrchestration platforms (e.g., Kubernetes, Ansible Tower)Automation scripts and tools (e.g., scripts, RPA tools)

While automation involves executing specific tasks automatically, orchestration manages and coordinates multiple automated processes to streamline complex workflows across systems. Orchestration provides a higher-level view, ensuring different automated tasks work together efficiently to achieve broader objectives.

What is an orchestration job?

An orchestration job involves coordinating and managing automated workflows across multiple systems or services to ensure efficient and reliable operation. It often requires knowledge of orchestration tools like Kubernetes, Ansible, or Apache Airflow, and typically involves tasks such as deployment, scaling, and process automation.

What are popular job titles related to Orchestration jobs in Ohio?

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

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

The top searched job categories for Orchestration jobs in Ohio are:

Orchestration jobs near you
Infographic showing various Orchestration job openings in Ohio as of August 2026, with employment types broken down into 62% Full Time, 16% Part Time, and 22% Contract. Highlights an 74% In-person, and 26% Remote job distribution, with an average salary of $141,554 per year, or $68.1 per hour.

Fleet Orchestration Engineer - Neuraverse (human)

NEURA Robotics

On-site

$120 - $160/hr

Other

Posted 4 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