Postdoctoral Scholar, EMS Overmatch
Northern Arizona University · Flagstaff, AZ · 1 mo ago
ResearchFull-time
We need to output HTML fragment with sections: headings for each section present. Must not repeat job title as heading. Must not include Job ID. Must preserve all substantive info. Remove boilerplate, navigation, etc. The posting includes:
- Special Information (but that's not a standard heading; we need to map to appropriate sections: maybe "About the Department/College", "About the Position", "Responsibilities Include". Also there is "Special Information" containing details about on-site, funding, driving, CUI, export control, citizenship, etc. This is substantive; we need to include it somewhere. Could be under a heading like "About the Position" or maybe "Qualifications"? But we must use headings only for sections that exist: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instructions: use
for each section present. Must not repeat job title as heading. Must not include Job ID. Must preserve all substantive info. Remove boilerplate, navigation, etc. The posting includes:
- Special Information (but that's not a standard heading; we need to map to appropriate sections: maybe "About the Department/College", "About the Position", "Responsibilities Include". Also there is "Special Information" containing details about on-site, funding, driving, CUI, export control, citizenship, etc. This is substantive; we need to include it somewhere. Could be under a heading like "About the Position" or maybe "Qualifications"? But we must use headings only for sections that exist: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if the posting has real specific content for them. We have "About the Department/College" and "About the Position". Those are not exactly the listed headings but similar to "About the role". Probably we can treat "About the Department/College" as "About the role"? Or we could create a heading "About the role" and put that content. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings if appropriate. The posting has "About the Department/College" and "About the Position". We could combine them under "About the role". Also there is "Responsibilities Include" which maps to Responsibilities.
We also have special information about citizenship, driving, CUI, export control, etc. That could go under "Requirements" or "Qualifications". Probably "Requirements" is appropriate: citizenship, ability to drive, handling CUI, export control compliance, etc. Also mention on-site requirement, funding availability, etc.
We also have details about work environment, fieldwork, occasional overtime, etc. That could be part of "About the Position" or maybe "Responsibilities"? But we already have responsibilities. Could include under "About the role" as well.
We must not create Pay/Schedule/Benefits unless posting actually states them. No pay, schedule, benefits mentioned. So omit those sections.
We must not include filler like "commensurate with experience". Not present.
We must output only HTML fragment.
Thus structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings if appropriate. The posting has "About the Department/College" and "About the Position". We could combine them under "About the role". Also there is "Responsibilities Include" which maps to Responsibilities.
We also have special information about citizenship, driving, CUI, export control, etc. That could go under "Requirements" or "Qualifications". Probably "Requirements" is appropriate: citizenship, ability to drive, handling CUI, export control compliance, etc. Also mention on-site requirement, funding availability, etc.
We also have details about work environment, fieldwork, occasional overtime, etc. That could be part of "About the Position" or maybe "Responsibilities"? But we already have responsibilities. Could include under "About the role" as well.
We must not create Pay/Schedule/Benefits unless posting actually states them. No pay, schedule, benefits mentioned. So omit those sections.
We must not include filler like "commensurate with experience". Not present.
We must output only HTML fragment.
Thus structure:
About the role
... content from About the Department/College and About the Position combined.
Responsibilities
- ... each bullet from Responsibilities Include (the percentages and descriptions).
Requirements
- ... items from Special Information: on-site requirement, funding availability, driving requirement, driver authorization, citizenship (US citizen or lawful permanent resident), ability to handle CUI, compliance with export control regulations (EAR, ITAR), ability to comply with project-specific technology control plan.
About the role
The Radiant Center for Remote Sensing, in partnership with the Dynamic and Active Systems Lab (DASL) in the Steve Sanghi College of Engineering at Northern Arizona University, seeks a Postdoctoral Research Associate to serve as lead technical researcher on a sponsored research project focused on radio source localization from unmanned aerial systems. This is one of several concurrent postdoctoral scholar recruitments at Radiant Center, and the successful candidate will collaborate closely with fellow postdoctoral researchers and faculty working simultaneously on related projects. The project, EMS Overmatch, develops and field-tests methods for locating radio-frequency sources using an aerial platform, combining signal-based position estimation with path-planning strategies that guide the UAV toward the vantage points that best resolve a source's location. The work builds on the lab's history of developing UAV-based radio-tracking systems, extending that foundation toward more capable localization and platform hardware for this new application area. The general research plan progresses from building out and validating a single-vehicle localization system. This will include hardware integration, field data collection, and flight testing across the varied terrain around Flagstaff. The program will progress toward more advanced localization and path-planning capabilities as the research matures. The postdoc will supervise graduate student researchers supporting the project, work closely with the PI, and contribute to technical reporting and manuscript preparation. The position is based in Flagstaff, AZ. Work Environment: This position requires a substantial amount of fieldwork, including UAV flight testing across Flagstaff-area terrain ranging from desert and canyon country to ponderosa pine, mixed conifer forest, and alpine tundra (spanning close to 8,000 feet of elevation change within about an hour of campus), as well as occasional overnight or multi-day travel for more distant field campaigns and for conference travel. Laboratory work involves electronics assembly/test equipment, RF signal generators and spectrum analyzers, 3D printers, and drone hardware. The position may require occasional overtime, particularly around field campaigns and sponsor reporting deadlines.
Responsibilities
- 45% - Radio Source Localization & Path Planning Research Lead development of algorithms and software development for real-time radio-frequency (RF) source localization from an aerial platform. Develop and evaluate path-planning strategies that optimize UAV positioning to improve localization accuracy and efficiency. Investigate RF propagation modeling approaches, including terrain-aware and simplified models, to characterize tradeoffs between prediction accuracy and computational cost in complex terrain. Contribute to the ongoing evolution of the project's research approach as findings develop, including potential extensions to additional operating scenarios.
- 25% - UAV Platform Development, Field Testing & Test Coordination Lead integration and adaptation of UAV hardware and RF-sensing payloads (hardware and software) to meet
Requirements
- On-site position requiring work primarily at an NAU site, campus, or facility; remote work opportunities are rare.
- Position subject to availability of funding.
- Regular driving of a vehicle on behalf of the university anticipated; must comply with Arizona Administrative Code Fleet Safety Policy (submit driver's license for monitoring, complete appropriate training).
- Open only to U.S. citizens and lawful permanent residents (green card holders) due to funding source.
- May require handling Controlled Unclassified Information (CUI) in accordance with sponsor and university data-security requirements.
- May involve technical data, hardware, or software subject to U.S. export control regulations (EAR, ITAR); incumbent must be able to comply with applicable export control requirements and any project-specific technology control plan.