Senior Software Engineer, Robotics- Behavior & Interaction

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines and application instructions. We need to preserve all substantive info. Let's parse the posting: Location: Irvine, CA · Engineering – Autonomy · Full time · On-site First paragraph: "Field AI is transforming how robots interact with the real world. We are building risk-aware, reliable, and field-ready AI systems that address the most complex challenges in robotics, unlocking the full potential of embodied intelligence. We go beyond typical data-driven approaches or pure transformer-based architectures, and are charting a new course, with already-globally-deployed solutions delivering real-world results and rapidly improving models through real-field applications" Then: "As a Senior Software Engineer in Behavior & Interaction, you will own the software systems that turn raw autonomy into finished missions. You operationalize that autonomy into repeatable, user-facing missions, design how humans task and collaborate with our robots, and deliver the insights our customers actually act on. You will architect and ship the behavior orchestration, robot interaction, and mission-to-insight pipelines that operate in some of the world's challenging industrial environments. This is a senior role for an engineer who wants to own systems end to end,and see their work run in the field." Then "What You Will Get To Do" bullet list. Then "What You Have" bullet list (requirements/qualifications). Then "What Will Set You Apart" bullet list (preferred qualifications). Then "Compensation and Benefits" with salary range and description. Then "Why Join FieldAI in Irvine?" paragraph. Then "Be Part of the Next Robotics Revolution" paragraph. Then EEO etc (to remove). Also duplicate AI tools paragraph repeated. We need to produce sections: maybe About the role (intro), Responsibilities (What You Will Get To Do), Requirements (What You Have), Qualifications (maybe combine with Requirements? but we can have Requirements and Qualifications separate if content distinct). Skills maybe from requirements? Could embed. But we must not create sections with filler. So we need to decide which sections have content. We have: - About the role: could be the introductory paragraphs describing company and role overview. - Responsibilities: "What You Will Get To Do" list. - Requirements: "What You Have" list (master's/PhD, experience, Python/C++, ROS2, behavior orchestration, HRI, system design, shipping, problem solving, communication). - Qualifications: maybe "What Will Set You Apart" list (preferred qualifications). Could treat as Qualifications or Skills. But we have Skills section maybe for specific technical skills like Python, C++, ROS2, behavior trees, etc. However we already have those in Requirements. Could combine. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. We have compensation and benefits content: salary range and benefits description. So we can have Benefits section (maybe includes compensation). Pay section maybe separate if we have salary. But we could combine Pay and Benefits into one Benefits section. However instruction says include a section ONLY when posting has real, specific content for it. It gives examples: Pay, Schedule, Benefits. So we could have Benefits section with salary and benefits description. Could also have Pay section if we want to separate salary from benefits, but we have both salary and benefits description; we could put salary in Pay and benefits in Benefits. But we need to avoid thin sections. Might be okay to have Pay section with salary range, and Benefits section with equity participation, etc. Let's see. We have: "Compensation and Benefits $160,000 – $220,000 a year Our salary range is highly competitive with the market, but we take into consideration an individual's background and experience in determining final salary. Base pay offered may vary depending on geographic location, job-related knowledge, skills, and experience, and the Irvine, California market. In addition to competitive compensation, FieldAI offers comprehensive benefits, equity participation, and the opportunity to contribute to cutting-edge advancements in AI and robotics." Thus we have salary range and benefits description. So we could have Pay section with salary range, Benefits section with comprehensive benefits, equity participation, opportunity. Schedule: not mentioned (full-time on-site). Could we infer schedule? It says Full time · On-site. That's schedule info: full-time, on-site. Could we create Schedule section with "Full-time, on-site"? The posting includes that in the header line. It's substantive. So we can include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe from "What Will Set You Apart"), Skills (maybe we can extract specific skills from requirements: Expert-level Python and C++, ROS2, behavior orchestration, HRI, system design, APIs, IPC, networking, real-time data pipelines, problem solving, communication). But we already have those in Requirements. Could we avoid duplication by putting skills in Requirements and not have separate Skills? The instruction says we can include Skills section if we have real specific content. We could decide to not include Skills to avoid thin sections. But we have plenty of content for Requirements; we can keep Requirements as the main qualifications. Qualifications could be the "What Will Set You Apart" list. Thus sections: - About the role (intro paragraphs) - Responsibilities (What You Will Get To Do) - Requirements (What You Have) - Qualifications (What Will Set You Apart) - Benefits (maybe combine compensation and benefits? but we have Pay and Benefits separate) - Pay (salary range) - Schedule (Full-time, On-site) We need to ensure we don't repeat content. Let's extract each. About the role: combine first two paragraphs (company description and role overview). Could be: "Field AI is transforming how robots interact with the real world. We are building risk-aware, reliable, and field-ready AI systems that address the most complex challenges in robotics, unlocking the full potential of embodied intelligence. We go beyond typical data-driven approaches or pure transformer-based architectures, and are charting a new course, with already-globally-deployed solutions delivering real-world results and rapidly improving models through real-field applications. As a Senior Software Engineer in Behavior & Interaction, you will own the software systems that turn raw autonomy into finished missions. You operationalize that autonomy into repeatable, user-facing missions, design how humans task and collaborate with our robots, and deliver the insights our customers actually act on. You will architect and ship the behavior orchestration, robot interaction, and mission-to-insight pipelines that operate in some of the world's challenging industrial environments. This is a senior role for an engineer who wants to own systems end to end, and see their work run in the field." Responsibilities: list from "What You Will Get To Do". Items: - Own the behavior and mission layer that operationalizes autonomy: design and build the software that turns core autonomy capabilities into repeatable, reliable, customer-facing missions. - Architect behavior orchestration for autonomous missions: mission definition and execution, and robust fallback and recovery behaviors for unstructured environments. - Design and build human and robot interaction behavior. - Validate behaviors on physical platforms in real customer conditions, then close the loop from field data back into the product. - Lead design reviews, make architecture decisions, and raise the engineering bar across the team. - Mentor engineers and collaborate across autonomy, perception, product, field deployment, and customer-facing teams. We need to put each as

inside

. Requirements: from "What You Have". Items: - Master's degree or PhD degree in Computer Science, Electrical Engineering, Robotics, or a related technical field, and significant experience building and shipping production-quality software (senior-level; typically 5+ years, with meaningful robotics or autonomy work). - Expert-level Python and C++, writing clean, efficient, maintainable code using modern best practices. - Deep, hands-on experience with ROS2, designing, building, and deploying custom nodes and complex systems into production robots. - Proven experience building behavior orchestration systems (behavior trees, state machines, task/mission planning and execution). - Experience building human-in-the-loop or operator-facing systems: HRI, teleoperation, supervisory control, dashboards, or tasking and monitoring tools. - Strong system design skills across APIs, inter-process communication (IPC), middleware, networking, and real-time data pipelines. - A track record of shipping to production and iterating from real-world use, including turning field data into product improvements. - Strong problem-solving skills and attention to detail, able to lead independently while managing multiple priorities. - Highly self-motivated, with excellent written and verbal communication skills and a strong collaborative mindset. Qualifications: from "What Will Set You Apart". Items: - Experience deploying robotic software in production industrial environments - Background in robotics reasoning, planning, or HRI - Experience with fleet management or multi-robot coordination. - Familiarity with perception and machine learning - Background on computationally constrained platforms and optimizing for real-time performance. - Understanding of safety standards and compliance in robotics. Benefits: from "In addition to competitive compensation, FieldAI offers comprehensive benefits, equity participation, and the opportunity to contribute to cutting-edge advancements in AI and robotics." Could also mention maybe other benefits not detailed. We'll just put that. Pay: salary range: "$160,000 – $220,000 a year". Also note about base pay varying etc. We'll include that sentence. Schedule: "Full time · On-site". Could phrase as "Full-time, on-site". Now we need to output HTML fragment only, no markdown fences. Use

for each section heading. Use

• for lists. Use

  for prose. We must not include boilerplate like EEO, AI tools, etc. Also remove duplicated lines. Check for any duplicated content: The posting had duplicate AI tools paragraph twice; we removed. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  ...

  Pay

  ...

  Schedule

  Full-time, on-site

  Make sure to preserve all substantive information. Ensure we didn't miss any details: The intro also mentions "We go beyond typical data-driven approaches or pure transformer-based architectures, and are charting a new course, with already-globally-deployed solutions delivering real-world results and rapidly improving models through real-field applications". Include that. Also mention "We are building risk-aware, reliable, and field-ready AI systems that address the most complex challenges in robotics, unlocking the full potential of embodied intelligence." Include. Also mention "As a Senior Software Engineer in Behavior & Interaction, you will own the software systems that turn raw autonomy into finished missions. You operationalize that autonomy into repeatable, user-facing missions, design how humans task and collaborate with our robots, and deliver the insights our customers actually act on. You will architect and ship the behavior orchestration, robot interaction, and mission-to-insight pipelines that operate in some of the world's challenging industrial environments. This is a senior role for an engineer who wants to own systems end to end, and see their work run in the field." Include. Now responsibilities list: ensure we captured all six items. Check each bullet from original: "Own the behavior and mission layer that operationalizes autonomy: design and build the software that turns core autonomy capabilities into repeatable, reliable, customer-facing missions." "Architect behavior orchestration for autonomous missions: mission definition and execution, and robust fallback and recovery behaviors for unstructured environments." "Design and build human and robot interaction behavior." "Validate behaviors