Skip to main content

Bot Auto

Algorithm Engineer, Autonomous Driving Validation

Houston, TX or San Francisco Bay AreamidAdded today

About this role

Bot Auto seeks an Algorithm Engineer to own the validation, testing, and operational health of its autonomous driving stack. You'll build and maintain the infrastructure that ensures code quality, catches regressions before deployment, and rapidly triages and resolves real-world issues.

What you'll do

  • Maintain and refactor core autonomy codebase for performance, scalability, and code hygiene
  • Design and operate the validation pipeline including scenario suites, metrics, and release-gating criteria
  • Improve simulation infrastructure for determinism, reproducibility, and regression diagnostics
  • Triage road and simulation issues—reproduce, root-cause, and either fix or escalate with clear documentation
  • Build debugging and observability tools (logging, replay, snapshots) for fast failure diagnosis
  • Collaborate with algorithm, simulation, and operations teams to streamline case resolution

What they're looking for

  • C++
  • Python
  • CI/CD and test infrastructure
  • Debugging and root-cause analysis
  • Simulation and validation pipelines
  • Data logging and observability
  • Code review and codebase maintenance
  • Autonomous systems or robotics (preferred)
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Bot Auto

Bot Auto builds autonomous truck technology, developing the mechanical systems, deep learning models, and operational software that power self-driving commercial freight vehicles. The company is hiring mechanical engineers, machine learning engineers, software engineers, and interns to work across hardware design, perception and control systems, ML infrastructure, and fleet management platforms.

View all jobs at Bot Auto

Likely interview questions

  • Walk us through a time you diagnosed and fixed a regression in a large, complex codebase—how did you approach it?
  • Describe your experience building or operating CI/validation infrastructure; what metrics or gates did you define?