Autonomous Systems Engineer
for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Sections present:
- About The Role (intro paragraph)
- What You'll Do (list of duties)
- Required Qualifications (list)
- Desired Qualifications (list)
- About Integer Technologies (company description)
- Company Benefits (list)
- Company Perks (list)
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can combine: "About the role" for intro paragraph. "Responsibilities" for What You'll Do. "Requirements" could include Required Qualifications? Or we could have "Qualifications" for Required and Desired? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide.
We have both Required and Desired qualifications; could put under "Qualifications" heading with sublists? But we must use
- for any list. Could have two separate lists under same heading? Probably okay.
We also have "About Integer Technologies" maybe could be under "About the role"? But that's company description; maybe we can include as a separate section? Not in allowed headings. Could fold into "About the role" or maybe omit? But we must preserve ALL substantive information; cannot drop company description. Could include as a
under "About the role" heading? The heading "About the role" is for role description; but we could add a paragraph about company after role description. However the heading is specific; we could still have a
after the heading that includes both role description and company description. That would preserve info.
Alternatively, we could create a heading "About Integer Technologies" but not allowed. So we must incorporate into allowed headings. Perhaps we can put under "About the role" as a paragraph after role description.
Similarly, "Company Perks" could go under "Benefits" heading? But Benefits heading is for benefits like insurance, relocation, salary, bonuses, 401k, vacation etc. Perks could be considered part of Benefits? Might be okay to include under Benefits heading as additional list items. However we must not create a Benefits section unless posting actually states them; they do state benefits and perks. So we can have Benefits heading with both benefits and perks lists.
Pay and Schedule: Not mentioned explicitly. No pay details besides "Base salaries which exceed local & national industry averages." That's a statement about pay but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state base salaries exceed averages, which is a statement about pay. So we could include a Pay section with that statement. However they also say "Year-end performance-based bonuses." That's compensation. So we could include Pay section with those statements. Schedule: not mentioned; do not create Schedule section.
Skills: Could we have a Skills heading? Not explicitly listed but we could include under Qualifications? Probably not needed.
We need to avoid filler like "commensurate with experience". Not present.
We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We must not repeat job title as heading. Not.
We must not put Job ID/requisition numbers as headings. Not present.
Now craft HTML.
Structure:
About the role
... role description paragraph(s) ... plus company description paragraph(s) maybe.
Responsibilities
- ...
...
Required Qualifications
- ...
...
Desired Qualifications
- ...
...
Benefits
- ...
...
Optionally Pay section: but we could incorporate pay statements into Benefits? Might be better to have Pay heading.
But we have Benefits heading already; we could add Pay as separate heading.
Let's see: Benefits includes medical, prescription, vision, dental, relocation assistance, base salaries exceed averages, year-end bonuses, 401k matching, paid vacation, sick leave, holidays. Perks: startup culture, stability, direct access to leadership, friendly atmosphere, waterfront office view.
We could combine all under Benefits heading; but Pay is part of benefits. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Benefits and Pay into one Benefits section. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits and also pay statements. So we could have a Benefits section that includes pay statements. That seems acceptable.
Thus we will have:
- About the role
- Responsibilities
- Required Qualifications
- Desired Qualifications
- Benefits (includes compensation, insurance, perks)
We must not create Skills, Requirements, Schedule, Pay separate.
But we have Required Qualifications and Desired Qualifications; we could combine under Qualifications heading with two sublists? But we have headings list includes Qualifications. Could do:
Qualifications
then two maybe with headings inside? But we cannot add extra headings inside? Could add Required etc. But maybe better to keep separate headings: Required Qualifications and Desired Qualifications are not in allowed list but they are close to Qualifications. The allowed list includes Qualifications (singular). Could we use Required Qualifications as a heading? It's not in the list but similar. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those exact headings when appropriate. So we should map content to those headings. So we need to decide which of those headings match our sections.
We have:
- About the role -> matches About the role.
- Responsibilities -> matches Responsibilities.
- Requirements -> could map to Required Qualifications.
- Qualifications -> could map to Desired Qualifications? Or we could combine both under Qualifications? But we have both required and desired; maybe we put Required under Requirements, Desired under Qualifications.
- Skills -> maybe not needed.
- Benefits -> matches Benefits.
- Pay -> we have pay statements; could put under Pay.
- Schedule -> none.
Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We must not create sections with filler. All have content.
Now we need to extract content.
About the role paragraph: The first paragraph after "About The Role". It includes several sentences. We'll capture that as prose.
We also have company description "About Integer Technologies". We'll incorporate after role description maybe as another paragraph under same heading.
Responsibilities: bullet list from "What You'll Do". Let's extract each bullet:
- Serve as an Autonomous Systems Engineer for submersible systems, with an emphasis on sensor data fusion algorithms for autonomous systems.
- Identify and develop methods of optimization for edge processing of sensor data used onboard autonomous platforms
- Contribute meaningfully to the technical deliverables of industry-academia research projects aimed at intelligent operation of unmanned and autonomous maritime systems.
- Assist with the development of autonomous strategies that balance speed, cost, and value of alternative approaches depending on system and project objectives.
- Engage with partners and customers to understand customer or user needs and elicit project requirements.
- Work collaboratively with software engineering and business development team members to develop new products and services using modeling and simulation tools and insights derived from their application.
Requirements (Required Qualifications): list:
- Must be a U.S. Citizen with the ability to obtain and maintain a U.S. DoD Secret Clearance.
- Bachelor’s degree in relevant field (e.g., computer science, computer engineering, electrical engineering, mechanical engineering, or other related field) and 6+ years of experience relevant to primary responsibilities outlined above.
- OR Master’s degree in relevant field and 4+ years of relevant experience.
- Experience using data from various perception sensor types (sonar, magnetic, cameras, lidar, etc.) to enhance a robotic platform's perception of its surrounding environmental and potential navigational hazards.
- Background in mathematics, and understanding of robotic algorithms such as, linear algebra, trigonometry, Bayesian statistics, and Kalman Filters
- Understanding of the Navy and Department of Defense’s mission, problem set, and strategy for the integration of autonomous systems.
- Experience with numerical methods and scientific software development in general purpose programming languages (e.g., Python, C++, Matlab).
Qualifications (Desired Qualifications): list:
- Ph.D. in relevant field (e.g., computer science, computer engineering, electrical engineering, mechanical engineering, or other related field) and 2+ years of relevant experience.
- Experience with unmanned and autonomous systems research involving maritime autonomous systems such as uncrewed surface vessels and uncrewed underwater vessels.
- Familiarity with maritime sensors (acoustics, magnetic, positioning, etc.)
- Experience with edge processing
- Familiarity with ROS (Robot Operating System)
- Experience in using AI/ML frameworks (e.g., PyTorch, TensorFlow, Flux, or similar).
Benefits: list from "Company Benefits" and "Company Perks". Combine.
Company Benefits bullet points:
- Integer fully covers medical, prescription, vision, and dental insurance costs for the employee and dependents.
- Meaning Integer standard plan pays 100% of health insurance premiums for your entire family from a well-known national insurer, saving its employee’s thousands of dollars annually.
- Relocation assistance available.
- Base salaries which exceed local & national industry averages.
- Year-end performance-based bonuses.
- 401(k) with company matching that vest immediately; no funny business.
- Paid Vacation
- Paid Sick Leave
- Paid Holidays
Company Perks bullet points:
- Startup culture with the stability of a large company.
- Integer’s business plan has years of time phased contracted work, alleviating the would-be risk from a traditional small company.
- Direct access to company leadership, prioritization of people over process, and a stellar team with a shared desire for personal and professional growth.
- Friendly atmosphere where people enjoy not only their work and what they're creating but enjoy helping each other as well.
- Waterfront office view!
We could keep them as separate lists under Benefits heading, but we could combine into one list.
Pay section: Not needed if we included base salaries and bonuses in Benefits. But we have a Pay heading available; we could put pay statements there. However we already put base salaries and bonuses in Benefits. To avoid duplication, maybe we put pay statements under Pay heading and keep Benefits for insurance, relocation, vacation etc. Let's see.
We have Pay heading allowed. So we can create Pay section with:
- Base salaries which exceed local & national industry averages.
- Year-end performance-based bonuses.
- 401(k) with company matching that vest immediately; no funny business.
But the 401k is more retirement benefit; could be under Benefits. However we can put under Pay.
Better to follow instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay may be thin. But we have substantive content for both. Could combine.
Given the instruction to include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Both Benefits and Pay have specific content. So
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Sections present: - About The Role (intro paragraph) - What You'll Do (list of duties) - Required Qualifications (list) - Desired Qualifications (list) - About Integer Technologies (company description) - Company Benefits (list) - Company Perks (list) We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine: "About the role" for intro paragraph. "Responsibilities" for What You'll Do. "Requirements" could include Required Qualifications? Or we could have "Qualifications" for Required and Desired? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide. We have both Required and Desired qualifications; could put under "Qualifications" heading with sublists? But we must use
- for any list. Could have two separate lists under same heading? Probably okay.
We also have "About Integer Technologies" maybe could be under "About the role"? But that's company description; maybe we can include as a separate section? Not in allowed headings. Could fold into "About the role" or maybe omit? But we must preserve ALL substantive information; cannot drop company description. Could include as a
under "About the role" heading? The heading "About the role" is for role description; but we could add a paragraph about company after role description. However the heading is specific; we could still have a
after the heading that includes both role description and company description. That would preserve info. Alternatively, we could create a heading "About Integer Technologies" but not allowed. So we must incorporate into allowed headings. Perhaps we can put under "About the role" as a paragraph after role description. Similarly, "Company Perks" could go under "Benefits" heading? But Benefits heading is for benefits like insurance, relocation, salary, bonuses, 401k, vacation etc. Perks could be considered part of Benefits? Might be okay to include under Benefits heading as additional list items. However we must not create a Benefits section unless posting actually states them; they do state benefits and perks. So we can have Benefits heading with both benefits and perks lists. Pay and Schedule: Not mentioned explicitly. No pay details besides "Base salaries which exceed local & national industry averages." That's a statement about pay but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state base salaries exceed averages, which is a statement about pay. So we could include a Pay section with that statement. However they also say "Year-end performance-based bonuses." That's compensation. So we could include Pay section with those statements. Schedule: not mentioned; do not create Schedule section. Skills: Could we have a Skills heading? Not explicitly listed but we could include under Qualifications? Probably not needed. We need to avoid filler like "commensurate with experience". Not present. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must not repeat job title as heading. Not. We must not put Job ID/requisition numbers as headings. Not present. Now craft HTML. Structure:
About the role
... role description paragraph(s) ... plus company description paragraph(s) maybe.
Responsibilities
- ... ...
Required Qualifications
- ... ...
Desired Qualifications
- ... ...
Benefits
- ... ...
Qualifications
then two- maybe with headings inside? But we cannot add extra headings inside? Could add Required etc. But maybe better to keep separate headings: Required Qualifications and Desired Qualifications are not in allowed list but they are close to Qualifications. The allowed list includes Qualifications (singular). Could we use Required Qualifications as a heading? It's not in the list but similar. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those exact headings when appropriate. So we should map content to those headings. So we need to decide which of those headings match our sections. We have: - About the role -> matches About the role. - Responsibilities -> matches Responsibilities. - Requirements -> could map to Required Qualifications. - Qualifications -> could map to Desired Qualifications? Or we could combine both under Qualifications? But we have both required and desired; maybe we put Required under Requirements, Desired under Qualifications. - Skills -> maybe not needed. - Benefits -> matches Benefits. - Pay -> we have pay statements; could put under Pay. - Schedule -> none. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not create sections with filler. All have content. Now we need to extract content. About the role paragraph: The first paragraph after "About The Role". It includes several sentences. We'll capture that as prose. We also have company description "About Integer Technologies". We'll incorporate after role description maybe as another paragraph under same heading. Responsibilities: bullet list from "What You'll Do". Let's extract each bullet: - Serve as an Autonomous Systems Engineer for submersible systems, with an emphasis on sensor data fusion algorithms for autonomous systems. - Identify and develop methods of optimization for edge processing of sensor data used onboard autonomous platforms - Contribute meaningfully to the technical deliverables of industry-academia research projects aimed at intelligent operation of unmanned and autonomous maritime systems. - Assist with the development of autonomous strategies that balance speed, cost, and value of alternative approaches depending on system and project objectives. - Engage with partners and customers to understand customer or user needs and elicit project requirements. - Work collaboratively with software engineering and business development team members to develop new products and services using modeling and simulation tools and insights derived from their application. Requirements (Required Qualifications): list: - Must be a U.S. Citizen with the ability to obtain and maintain a U.S. DoD Secret Clearance. - Bachelor’s degree in relevant field (e.g., computer science, computer engineering, electrical engineering, mechanical engineering, or other related field) and 6+ years of experience relevant to primary responsibilities outlined above. - OR Master’s degree in relevant field and 4+ years of relevant experience. - Experience using data from various perception sensor types (sonar, magnetic, cameras, lidar, etc.) to enhance a robotic platform's perception of its surrounding environmental and potential navigational hazards. - Background in mathematics, and understanding of robotic algorithms such as, linear algebra, trigonometry, Bayesian statistics, and Kalman Filters - Understanding of the Navy and Department of Defense’s mission, problem set, and strategy for the integration of autonomous systems. - Experience with numerical methods and scientific software development in general purpose programming languages (e.g., Python, C++, Matlab). Qualifications (Desired Qualifications): list: - Ph.D. in relevant field (e.g., computer science, computer engineering, electrical engineering, mechanical engineering, or other related field) and 2+ years of relevant experience. - Experience with unmanned and autonomous systems research involving maritime autonomous systems such as uncrewed surface vessels and uncrewed underwater vessels. - Familiarity with maritime sensors (acoustics, magnetic, positioning, etc.) - Experience with edge processing - Familiarity with ROS (Robot Operating System) - Experience in using AI/ML frameworks (e.g., PyTorch, TensorFlow, Flux, or similar). Benefits: list from "Company Benefits" and "Company Perks". Combine. Company Benefits bullet points: - Integer fully covers medical, prescription, vision, and dental insurance costs for the employee and dependents. - Meaning Integer standard plan pays 100% of health insurance premiums for your entire family from a well-known national insurer, saving its employee’s thousands of dollars annually. - Relocation assistance available. - Base salaries which exceed local & national industry averages. - Year-end performance-based bonuses. - 401(k) with company matching that vest immediately; no funny business. - Paid Vacation - Paid Sick Leave - Paid Holidays Company Perks bullet points: - Startup culture with the stability of a large company. - Integer’s business plan has years of time phased contracted work, alleviating the would-be risk from a traditional small company. - Direct access to company leadership, prioritization of people over process, and a stellar team with a shared desire for personal and professional growth. - Friendly atmosphere where people enjoy not only their work and what they're creating but enjoy helping each other as well. - Waterfront office view! We could keep them as separate lists under Benefits heading, but we could combine into one list. Pay section: Not needed if we included base salaries and bonuses in Benefits. But we have a Pay heading available; we could put pay statements there. However we already put base salaries and bonuses in Benefits. To avoid duplication, maybe we put pay statements under Pay heading and keep Benefits for insurance, relocation, vacation etc. Let's see. We have Pay heading allowed. So we can create Pay section with: - Base salaries which exceed local & national industry averages. - Year-end performance-based bonuses. - 401(k) with company matching that vest immediately; no funny business. But the 401k is more retirement benefit; could be under Benefits. However we can put under Pay. Better to follow instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay may be thin. But we have substantive content for both. Could combine. Given the instruction to include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Both Benefits and Pay have specific content. So