Find Jobs
Find Jobs Near You – Available Work in Your Location
Skip to job details
A
ArcBest
Robotics Software Engineer III - Infrastructure - Vaux
Career Insights for Robotics Software Engineer
See where this job fits in the broader career landscape. Knowing your career path helps you see what's possible from here.
Scorecard
Based on Arkansas data
Review key factors to help you decide if this role fits your goals. How is this calculated?
What they do
A Robotics Software Engineer develops and builds software systems related to the operation and development of robots, typically for the manufacturing or transportation industries.
$146,369 / year median in Arkansas
+22% projected growth
Job Description
Job Description The Robotics Software Engineer III - Infrastructure is responsible for designing and enabling the foundational infrastructure that supports the full lifecycle of autonomous robotic systems, from source code to deployment and field observability. This position provides high leverage across perception, planning, controls, simulation, and safety teams by delivering durable platforms, shared workflows, and guardrails that allow product teams to move quickly without compromising reliability, traceability, or compliance. The Robotics Software Engineer III - Infrastructure sits at the intersection of robotics software, DevOps, simulation, and MLOps. This position focuses on building scalable systems and standards rather than acting as a first responder for day-to-day operational issues. Success is measured by reduced friction for autonomy engineers, improved release confidence, and infrastructure becoming a competitive advantage rather than a bottleneck. Responsibilities Design and enable shared infrastructure supporting the end-to-end robotics software lifecycle: Source, Build, Test, Simulate, Deploy, Monitor. Standardize build systems and CI/CD pipelines across robotics software, embedded systems, and simulation environments. Define and manage artifact versioning strategies for software binaries, firmware, configuration, calibration data, maps, and vehicle-specific parameters. Establish platform standards, reference architectures, and best practices used across multiple product teams. Enable large-scale Software-in-the-Loop (SIL), Hardware-in-the-Loop (HIL), and regression simulation workflows. Integrate simulation results into CI pipelines with clear pass/fail criteria and reporting. Support scenario-based testing, coverage tracking, and regression analysis. Provide infrastructure and tooling to improve correlation between simulation results and real-world vehicle behavior in collaboration with simulation and vehicle integration teams. Design and evolve shared infrastructure supporting the lifecycle of machine learning models used in autonomy systems. Enable dataset versioning, lineage tracking, training reproducibility, and model promotion workflows. Define standards for model packaging, deployment to vehicles, runtime monitoring, and rollback mechanisms. Partner with perception and autonomy teams to enable safe and performant model deployment, while domain teams retain ownership of model design and performance outcomes. Build and maintain reliable pipelines for deploying software and models to development vehicles, test fleets, and production systems. Enable vehicle-level observability through logging, metrics, and distributed tracing. Support rapid diagnosis of field issues and feedback loops into development, testing, and simulation environments. Enable traceability for safety-critical systems, including the ability to identify what software, model, and configuration ran on a specific vehicle at a given time. Support functional safety requirements by enabling reproducible builds, preserving validation evidence, and supporting audits and certification activities (e.g., ISO 3691-4, ISO 13849). Collaborate closely with Functional Safety Engineering to ensure infrastructure aligns with compliance and certification needs. Act as a force multiplier for autonomy engineers by reducing duplicated tooling and infrastructure maintenance overhead. Make pragmatic trade-offs between development velocity, system reliability, and safety requirements. Mentor engineers on platform usage, infrastructure best practices, and scalable system design. Influence technical direction across teams without direct people management responsibility. Other duties and projects, as assigned.