Robot Autonomy Engineer - Software
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content.
We need to parse the job posting.
Key sections:
- About the Job (or About the role) - we have "About the Job" paragraph: "At FieldAI, we build autonomous robotic systems...". That's prose.
- Responsibilities: "What You’ll Get To Do" bullet list: Drive strategic integration..., Build robust utilities..., Provide high-level technical expertise...
- Requirements/Qualifications: "What You Have" list: PhD degree..., Proven expertise..., Experience/Familiarity..., Ability..., Proven track record..., Excellent..., Strong analytical..., Ability to thrive...
- Skills: maybe "The Extras That Set You Apart" list: Experience deploying..., Experience using Jira..., Ability to work directly..., Excellent communication..., Willingness to travel...
- Benefits: "Part of our compensation package also includes full benefits, equity, and generous time off." Also maybe "Compensation" section: salary range $100,000-$200,000.
- Pay: salary range.
- Schedule: "Onsite Work Philosophy" mentions fully onsite role, flexible working hours. That's schedule info.
We need to avoid boilerplate: EEO, diversity statement, AI tools note, etc. Remove those.
We need to preserve all substantive info, not invent.
We need to output only HTML fragment, no /, no markdown fences.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which headings to include: About the role (or About the Job). Use "About the role" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. We need to map content.
- About the role: use the "About the Job" paragraph.
- Responsibilities: use "What You’ll Get To Do" list.
- Requirements: maybe combine "What You Have" (which includes qualifications). Could be Requirements heading.
- Qualifications: maybe separate? But we have overlapping. Could combine Requirements and Qualifications into one? But instruction says prefer few substantive sections over many thin ones. So we could have Requirements (including qualifications) and Skills (extras). Or we could have Requirements and Qualifications separate if content distinct. Let's see: "What You Have" includes degree, expertise, experience, ability, track record, communication, analytical, ability to thrive. That's qualifications. "The Extras That Set You Apart" includes additional desirable experience: deploying mission-critical systems, Jira, customer interaction, communication, travel. That could be Skills.
Thus:
- Requirements: the core qualifications list.
- Skills: the extras list.
- Benefits: "full benefits, equity, and generous time off." Also maybe mention "compensation package also includes full benefits, equity, and generous time off." That's benefits.
- Pay: salary range $100,000-$200,000.
- Schedule: fully onsite role, flexible working hours.
We need to ensure we don't include headings with filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO statement, diversity, AI tools note, etc.
Now craft HTML.
Structure:
About the role
At FieldAI, we build autonomous robotic systems that operate in demanding, real-world environments where tight integration between hardware and software is critical. We’re looking for a Software Engineer to support testing, deployment, and integration of wheeled robotic platforms across both federal and commercial programs As a Robot Autonomy Engineer - Software at Field AI, you’ll be at the forefront of bringing our autonomous systems to life in the real world, owning deployment, integration, and ongoing performance in the field. This role is equal parts engineering and problem-solving. You’ll work hands-on with both customers and our internal teams to ensure successful operations, rapidly incorporate field feedback to improve reliability and performance, and drive adoption so our systems become mission-critical from day one. If you thrive in fast-paced, high-impact environments and want to see your work directly enable the future of autonomy, this is the role where you’ll make it happen.
Note: The paragraph includes a run-on sentence; we keep as is.
Responsibilities
- Drive strategic integration, debugging, and rapid capability development while providing essential software support
- Build robust utilities and tools to facilitate integration and automated testing for system software builds
- Provide high-level technical expertise and analytical insights to advance the development of robust software architectures
Requirements
- PhD degree in Robotics, Computer Science, Electrical Engineering, or a related field or MS degree in a related field with 2+ years of industry or applied research
- Proven expertise in software engineering across the full program lifecycle, with a focus on early-stage system design and development
- Experience/Familiarity with robotics middleware such as ROS / ROS 2 or similar distributed robotics software systems
- Experience/Familiarity with distributed systems (multiple nodes, real-time comms)
- Experience/Familiarity with embedded systems (C/C++ on constrained hardware)
- Ability to work effectively across adjacent domains, including software, electronics, networking, and mechanical interfaces
- Proven track record managing complex programs with multiple dependencies in agile/hybrid frameworks
- Excellent written and verbal communication skills; comfortable presenting to executives and diverse audiences
- Strong analytical capabilities, with experience in financial modeling, ROI analysis, and tracking KPIs
- Ability to thrive in fast‑paced, high‑growth startup environments; proactive, adaptable, resilient
Skills
- Experience deploying, operating, or maintaining mission-critical systems in real-world environments
- Experience using Jira or Wrike or Confluence or other program management software tools
- Ability to work directly with customers in high-stakes, fast-paced settings, translating needs into technical solutions
- Excellent communication skills, with the ability to explain technical concepts to non-technical users
- Willingness to travel and work on-site with customers as needed
Benefits
Part of our compensation package also includes full benefits, equity, and generous time off.
Pay
The salary range for this role is $100,000-$200,000.
Schedule
This is a fully onsite role, and candidates will be expected to work from our HQ in Irvine, CA. In-person engagement is essential to our success, and we offer flexible working hours to support focus and work-life balance.
Check for any leftover boilerplate: we removed EEO, diversity, AI tools note, etc. Also removed "Learn more at https://fieldai.com." That's a link; maybe we should keep? It's part of "Who are We?" but it's a link; it's not boilerplate? It's a link to learn more. Might be considered navigation? It's a link to the company site. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not necessarily boilerplate; it's a reference. Could keep but it's a URL. Might be considered navigation? It's just a link. Safer to keep? The "Learn more at https://fieldai.com." is part of the "Who are We?" section. It's not a heading. It's a sentence. Could keep as part of About the role? Actually it's before About the Job. Might be considered part of company description. We could include it in About the role paragraph. But the About the role paragraph we used is from "About the Job". The "Learn more at https://fieldai.com." is separate. We could incorporate it into About the role paragraph after the first sentence? But we must preserve all substantive information. So we should include that link somewhere. Where does it belong? It's under "Who are We?" maybe we can add a sentence at the end of About the role: "Learn more at https://fieldai.com." That's substantive. Let's add it.
Thus modify About the role paragraph to include that sentence.
We need to ensure we don't duplicate content. The "Who are We?" 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. Learn more at https://fieldai.com."
That's also substantive. Should we include that? It's about the company. Could be part of About the role? The instruction says use headings for sections like About the role, Responsibilities, etc. The "Who are We?" is company overview, could be part of About the role. We could incorporate that paragraph as well. But we must not invent headings. We could add a paragraph under About the role that includes both the "Who are We?" and the "About the Job" content. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having multiple paragraphs under a heading. So we can put all company description and role description under About the role.
Thus we need to include the "Who are We?" paragraph plus the "About the Job" paragraph plus the "Learn more at https://fieldai.com." (which is already in the Who are We? paragraph). Actually the Learn more appears at end of Who are We? paragraph. So we just include that paragraph.
Thus About the role will contain:
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. Learn more at https://fieldai.com.
Then the About the Job paragraph.
We'll combine them into one
or two
? The instruction: use
for prose. Could have multiple
under same heading. We'll do two
elements.
Now check for any other substantive content: "Why Join Field AI?" section includes a lot of fluff but also some specifics: "We are solving one of the world’s most complex challenges: deploying robots in unstructured, previously unknown environments. Our Field Foundational Models™ set a new standard in perception, planning, localization, and manipulation, ensuring our approach is explainable and safe for deployment. You will have the opportunity to work with a world-class team that thrives on creativity, resilience, and bold thinking. With a decade-long track record of deploying solutions in the field, winning DARPA challenge segments, and bringing expertise from organizations like DeepMind, NASA JPL, Boston Dynamics, NVIDIA, Amazon, Tesla Autopilot, Cruise Self-Driving, Zoox, Toyota Research Institute, and SpaceX, we are set to achieve our ambitious goals." This is substantive but maybe could be considered part of About the
- for any list of duties/requirements/benefits. Use
for prose. We need to decide which headings to include: About the role (or About the Job). Use "About the role" as heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. We need to map content. - About the role: use the "About the Job" paragraph. - Responsibilities: use "What You’ll Get To Do" list. - Requirements: maybe combine "What You Have" (which includes qualifications). Could be Requirements heading. - Qualifications: maybe separate? But we have overlapping. Could combine Requirements and Qualifications into one? But instruction says prefer few substantive sections over many thin ones. So we could have Requirements (including qualifications) and Skills (extras). Or we could have Requirements and Qualifications separate if content distinct. Let's see: "What You Have" includes degree, expertise, experience, ability, track record, communication, analytical, ability to thrive. That's qualifications. "The Extras That Set You Apart" includes additional desirable experience: deploying mission-critical systems, Jira, customer interaction, communication, travel. That could be Skills. Thus: - Requirements: the core qualifications list. - Skills: the extras list. - Benefits: "full benefits, equity, and generous time off." Also maybe mention "compensation package also includes full benefits, equity, and generous time off." That's benefits. - Pay: salary range $100,000-$200,000. - Schedule: fully onsite role, flexible working hours. We need to ensure we don't include headings with filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO statement, diversity, AI tools note, etc. Now craft HTML. Structure:
About the role
At FieldAI, we build autonomous robotic systems that operate in demanding, real-world environments where tight integration between hardware and software is critical. We’re looking for a Software Engineer to support testing, deployment, and integration of wheeled robotic platforms across both federal and commercial programs As a Robot Autonomy Engineer - Software at Field AI, you’ll be at the forefront of bringing our autonomous systems to life in the real world, owning deployment, integration, and ongoing performance in the field. This role is equal parts engineering and problem-solving. You’ll work hands-on with both customers and our internal teams to ensure successful operations, rapidly incorporate field feedback to improve reliability and performance, and drive adoption so our systems become mission-critical from day one. If you thrive in fast-paced, high-impact environments and want to see your work directly enable the future of autonomy, this is the role where you’ll make it happen.
Note: The paragraph includes a run-on sentence; we keep as is.Responsibilities
- Drive strategic integration, debugging, and rapid capability development while providing essential software support
- Build robust utilities and tools to facilitate integration and automated testing for system software builds
- Provide high-level technical expertise and analytical insights to advance the development of robust software architectures
Requirements
- PhD degree in Robotics, Computer Science, Electrical Engineering, or a related field or MS degree in a related field with 2+ years of industry or applied research
- Proven expertise in software engineering across the full program lifecycle, with a focus on early-stage system design and development
- Experience/Familiarity with robotics middleware such as ROS / ROS 2 or similar distributed robotics software systems
- Experience/Familiarity with distributed systems (multiple nodes, real-time comms)
- Experience/Familiarity with embedded systems (C/C++ on constrained hardware)
- Ability to work effectively across adjacent domains, including software, electronics, networking, and mechanical interfaces
- Proven track record managing complex programs with multiple dependencies in agile/hybrid frameworks
- Excellent written and verbal communication skills; comfortable presenting to executives and diverse audiences
- Strong analytical capabilities, with experience in financial modeling, ROI analysis, and tracking KPIs
- Ability to thrive in fast‑paced, high‑growth startup environments; proactive, adaptable, resilient
Skills
- Experience deploying, operating, or maintaining mission-critical systems in real-world environments
- Experience using Jira or Wrike or Confluence or other program management software tools
- Ability to work directly with customers in high-stakes, fast-paced settings, translating needs into technical solutions
- Excellent communication skills, with the ability to explain technical concepts to non-technical users
- Willingness to travel and work on-site with customers as needed
Benefits
Part of our compensation package also includes full benefits, equity, and generous time off.
Pay
The salary range for this role is $100,000-$200,000.
Schedule
This is a fully onsite role, and candidates will be expected to work from our HQ in Irvine, CA. In-person engagement is essential to our success, and we offer flexible working hours to support focus and work-life balance.
Check for any leftover boilerplate: we removed EEO, diversity, AI tools note, etc. Also removed "Learn more at https://fieldai.com." That's a link; maybe we should keep? It's part of "Who are We?" but it's a link; it's not boilerplate? It's a link to learn more. Might be considered navigation? It's a link to the company site. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not necessarily boilerplate; it's a reference. Could keep but it's a URL. Might be considered navigation? It's just a link. Safer to keep? The "Learn more at https://fieldai.com." is part of the "Who are We?" section. It's not a heading. It's a sentence. Could keep as part of About the role? Actually it's before About the Job. Might be considered part of company description. We could include it in About the role paragraph. But the About the role paragraph we used is from "About the Job". The "Learn more at https://fieldai.com." is separate. We could incorporate it into About the role paragraph after the first sentence? But we must preserve all substantive information. So we should include that link somewhere. Where does it belong? It's under "Who are We?" maybe we can add a sentence at the end of About the role: "Learn more at https://fieldai.com." That's substantive. Let's add it. Thus modify About the role paragraph to include that sentence. We need to ensure we don't duplicate content. The "Who are We?" 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. Learn more at https://fieldai.com." That's also substantive. Should we include that? It's about the company. Could be part of About the role? The instruction says use headings for sections like About the role, Responsibilities, etc. The "Who are We?" is company overview, could be part of About the role. We could incorporate that paragraph as well. But we must not invent headings. We could add a paragraph under About the role that includes both the "Who are We?" and the "About the Job" content. However the instruction says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having multiple paragraphs under a heading. So we can put all company description and role description under About the role. Thus we need to include the "Who are We?" paragraph plus the "About the Job" paragraph plus the "Learn more at https://fieldai.com." (which is already in the Who are We? paragraph). Actually the Learn more appears at end of Who are We? paragraph. So we just include that paragraph. Thus About the role will contain: 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. Learn more at https://fieldai.com. Then the About the Job paragraph. We'll combine them into one
or two
? The instruction: use
for prose. Could have multiple
under same heading. We'll do two
elements. Now check for any other substantive content: "Why Join Field AI?" section includes a lot of fluff but also some specifics: "We are solving one of the world’s most complex challenges: deploying robots in unstructured, previously unknown environments. Our Field Foundational Models™ set a new standard in perception, planning, localization, and manipulation, ensuring our approach is explainable and safe for deployment. You will have the opportunity to work with a world-class team that thrives on creativity, resilience, and bold thinking. With a decade-long track record of deploying solutions in the field, winning DARPA challenge segments, and bringing expertise from organizations like DeepMind, NASA JPL, Boston Dynamics, NVIDIA, Amazon, Tesla Autopilot, Cruise Self-Driving, Zoox, Toyota Research Institute, and SpaceX, we are set to achieve our ambitious goals." This is substantive but maybe could be considered part of About the