Skip to main content

Field AI

Robotics Autonomy Engineer - Triage

Irvine, CA$100k–$200kfull timemidAdded 6 days ago

About this role

FieldAI seeks a Robotics Autonomy Engineer to develop risk-aware AI systems for field-deployed robots in Irvine, CA. You'll combine rigorous engineering with machine learning to create reliable autonomy solutions that are tested on real hardware and continuously improved through live deployments.

What you'll do

  • Design and implement autonomy algorithms for field-deployed robotic systems
  • Develop risk-aware decision-making systems that operate reliably in real-world conditions
  • Integrate perception, learning, and control systems for embodied AI applications
  • Collaborate on hardware testing and validation of AI systems in field environments
  • Optimize AI models based on data from live robot deployments
  • Balance pure learning approaches with engineered robustness for production systems

What they're looking for

  • Robotics autonomy and motion planning
  • Machine learning and deep learning frameworks
  • Real-time systems and embedded software
  • Sensor integration and perception systems
  • Python and/or C++ programming
  • Hardware-software integration and testing
  • Risk assessment and safety-critical systems
  • Control systems theory
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.

Field AI

Field AI develops embodied AI and autonomous robotics systems for real-world deployment in industrial environments like oil & gas and mining. The company is hiring software engineers to build web-based systems, perception and validation pipelines, test infrastructure, ROS-based robotic software, and customer-facing products that integrate AI with field-deployed hardware.

View all jobs at Field AI

Likely interview questions

  • Describe your experience deploying AI systems on real robots and handling failures in production environments
  • How do you balance between pure learning-based approaches and rule-based engineering for mission-critical autonomy?