Autonomy Test & Integration Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. The posting includes role overview, responsibilities (What You'll Do), qualifications (What You'll Bring), Who We're Looking For (maybe attributes), What We Offer (benefits). No explicit Pay or Schedule. So we should not create Pay or Schedule sections. We need sections: About the role (maybe role overview), Responsibilities, Requirements (or Qualifications), Skills (maybe combine), Benefits (What We Offer). Also maybe "Who We're Looking For" could be part of Qualifications or Skills. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include those that have content. We have role overview: "Role Overview ..." That's about the role. So

About the role

with paragraph. Responsibilities: "What You'll Do" list. Use

• . Requirements: maybe "What You'll Bring" includes experience, eligibility, etc. Could be Requirements. Also "Who We're Looking For" could be Qualifications or Skills. We need to decide. We have skills: strong C/C++, Python, Linux, etc. Also bonus items. We have benefits: "What We Offer" list. We should not repeat job title. No metadata like Job ID. We must preserve all substantive information. So we need to include all details from the posting, but we can reorganize into sections. We must not invent or summarize away detail. Must keep specifics like "180 miles at 180 mph", "Seaglider", etc. Must keep eligibility ITAR, etc. We must remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, scam-warning, application instructions. The posting includes "Equal Opportunity Employer REGENT is an Equal Opportunity Employer..." That's boilerplate; remove. Also remove "If you’re ready to take on an exciting challenge..." maybe that's a call to action; but it's not boilerplate? It's more like encouragement to apply. Might be considered application instruction? It says "we want to hear from you." That's application encouragement; maybe we should remove as it's application instruction. The instruction says remove application instructions. So we should remove that paragraph. Also remove "Even if you don’t meet every requirement..." that's also encouragement. Remove. Also remove "We value diverse skillsets..." maybe also encouragement. Remove. We need to keep all substantive info: mission description, role overview, responsibilities list, what you'll bring list, who we're looking for attributes, what we offer list. We need to format as HTML fragment only. Let's extract content. Mission description paragraph: "At REGENT, we’re on a mission to revolutionize regional transportation between coastal cities. We're not just building vehicles, we're creating a new category of transportation: the Seaglider. These groundbreaking wing-in-ground-effect craft travel just above the water’s surface, combining the speed of an airplane with the low operating costs of a boat. Capable of 180 miles at 180 mph on today's battery tech (and up to 400 miles with next-gen batteries), Seagliders will unlock fast, affordable, and sustainable coastal transit for passengers and cargo - connecting cities, islands, and communities like never before. Backed by leading investors and powered by a team of passionate, forward-thinking engineers, builders, and operators, we’re now scaling from a breakthrough prototype to full production - and building the team to make it happen." That's about the company; could be part of About the role? Might be separate but we can include in About the role. Role Overview paragraph: "We're looking for an Autonomy Test & Integration Engineer to take our perception system from the bench to the open ocean and build the test infrastructure that connects the two. The system detects and tracks vessel traffic for a wing-in-ground-effect craft that takes off and lands on the water. Testing perception on this class of vehicle is a problem very few people have worked on. Half the job happens on the water. You'll go out with our test and operations team, who run the vessels and the campaigns, and handle the perception side: mounting and cabling cameras and radar on boats, calibrating dockside, and collecting data against live vessel traffic. No two sea days give you the same weather, light, and traffic. The job is planning each one tightly, adapting when hardware or the sea won't cooperate, and coming back with data worth keeping. The other half is onshore, building what the field work depends on: replay and hardware-in-the-loop setups that let us rerun a sea day on the bench, calibration tooling that keeps sensor data usable, and the integration path that carries new perception software onto our vehicles. Whether a day's results can be trusted comes down to calibration and process, and both are yours. The team iterates as fast as this infrastructure lets it. Major perception test campaigns are on the calendar for the next year. They'll run on infrastructure and process this role builds between now and then. If you’re energized by working at the intersection of cutting-edge innovation, real-world impact, and hands-on engineering, you’ll be in the right place - and we’d be thrilled to have you on the team!" We could keep that as About the role. Responsibilities: "What You'll Do" bullet list: - Run perception field tests. Define what a test day must produce, set up and calibrate the perception sensor rigs, and run sensor tests on surrogate vessels with our test and operations team. - Do hands-on integration work. Bring software changes onto real vehicle hardware and troubleshoot what breaks in that transition, across every platform the team supports. - Own the replay tooling. Operate and extend the hardware-in-the-loop and data-replay infrastructure the team's testing runs on, building on existing recording and evaluation tooling. - Keep perception reliable. Track and maintain perception system reliability across every platform the team supports. - Test and sign off on software changes. Review changes and decide when they're ready to move from the bench, to hardware-in-the-loop replay, to a surrogate vessel, to a vehicle. - Carry capability to missions. Take the perception capabilities the team builds and apply them to customer and U.S. defense missions, working with our mission software team to define the mission-specific functions needed and bringing those needs back to the perception team. - Define autonomy test scenarios. As our autonomy work grows beyond alerting, design the scenarios that prove out new autonomy algorithms and run them with our test and operations team. We need to keep each as
• . What You'll Bring (requirements/qualifications/skills): - Demonstrated professional experience in robotics, autonomy, or perception software, including hands-on hardware-in-the-loop or data-replay work. - Field deployment experience, ideally including sensor testing on boats or a comparable surrogate vehicle. - Experience testing software on real hardware, from code review through deployment. - Strong C/C++ for real-time or embedded systems, working Python, and comfort administering Linux systems. - Eligibility: this position is subject to U.S. export control regulations; applicants must be U.S. persons as defined by ITAR (22 CFR 120.62). - Bonus: familiarity with autonomy algorithm concepts, ARPA radar tracking experience, boating or sea-trials background, ground-truth system experience, basic electrical troubleshooting, DO-178C familiarity. We could split: Requirements (mandatory) and Skills (technical) and Bonus as maybe Skills? But we have headings: Requirements, Qualifications, Skills. We could put mandatory experience under Requirements, technical skills under Skills, and bonus under Skills as well? Or Qualifications could be the bonus? Let's think. Better: Requirements = mandatory experience items (first four). Skills = technical skills (C/C++, Python, Linux) plus maybe bonus items? But we also have eligibility which is a requirement. We could do:

  Requirements

  • Demonstrated professional experience in robotics, autonomy, or perception software, including hands-on hardware-in-the-loop or data-replay work.
  • Field deployment experience, ideally including sensor testing on boats or a comparable surrogate vehicle.
  • Experience testing software on real hardware, from code review through deployment.
  • Eligibility: this position is subject to U.S. export control regulations; applicants must be U.S. persons as defined by ITAR (22 CFR 120.62).

  Skills

  • Strong C/C++ for real-time or embedded systems, working Python, and comfort administering Linux systems.
  • Familiarity with autonomy algorithm concepts, ARPA radar tracking experience, boating or sea-trials background, ground-truth system experience, basic electrical troubleshooting, DO-178C familiarity (bonus).
  But we also have "Who We're Looking For" attributes: Collaborative Team Player, Creative Problem Solver, Adaptable & Agile, Innovative Mindset. Those could be Qualifications or maybe Skills? They are more like behavioral competencies. Could put under Qualifications. Thus:

  Qualifications

  • Collaborative Team Player: You know field testing is a team effort. You work closely with perception, autonomy, test, operations, and mission software teams to plan effectively, solve problems in real time, and make sure what you learn on the water gets back to the people building the system. You communicate clearly, especially when conditions change or something isn't ready to move forward.
  • Creative Problem Solver: You’re hands-on and like getting to the bottom of why something isn’t working. Whether it’s a sensor, calibration issue, software integration problem, or test setup, you dig in yourself, troubleshoot across hardware and software, and look for ways to make the underlying tooling or process better — not just get through the test day.
  • Adaptable & Agile: You’re comfortable on a boat, not just at a desk. You know field testing rarely goes exactly as planned and can adapt when weather, hardware, vessel traffic, or test conditions change. You stay focused on what the test needs to prove and make good calls about when to adjust, keep going, or stop and regroup.
  • Innovative Mindset: You see the whole path from the bench to hardware-in-the-loop testing to a surrogate vessel and ultimately the vehicle, and you’re always looking for ways to make that path faster, more reliable, and more repeatable. You hold a high bar for testing and validation and don’t sign off on something simply because the team is in a hurry — you want the data and evidence to know it’s ready.
  Benefits: "What We Offer" list: - Competitive compensation including a robust equity incentive plan. - Comprehensive health, dental, and vision insurance - we cover 100% of your premiums. - 401(k) with company matching, so you can plan for the future. - Generous flexible time off, paid parental leave, and company-wide holiday breaks. - Relocation packages available for those moving to join our team. - Daily, free catered lunches - Learning & professional development opportunities We'll put under

  Benefits

  . We should not include Pay or Schedule sections as not present. We need to ensure we preserve all substantive info. Did we miss any? The mission description paragraph at start is included in About the role? We included role overview but not the initial mission paragraph. We should include that as part of About the role maybe preceding the role overview. Let's combine: About the role includes both mission description and role overview. Thus About the role paragraph(s) could be two paragraphs: first mission description, second role overview. We must not repeat job title. Good. Now ensure we removed boilerplate: EEO, equal opportunity, etc. Also removed encouraging paragraphs. Check if any other boilerplate: "If you’re ready to take on an exciting challenge..." we removed. "