> Markdown version of [/jobs/ext/3672073-payload-integration-engineer](https://www.wearedevelopers.com/jobs/ext/3672073-payload-integration-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Payload Integration Engineer

- **Company:** Aureus Greenway Holdings Inc.
- **Location:** United States
- **Contract:** Permanent contract
- **Skills:** Computer-Aided Design, Signals Intelligence, Embedded Software, Ethernet, Network Interface Controllers, Technical Data Management Systems, Lidar
- **Published:** October 10, 2026
- **Apply:** https://www.thejobnetwork.com/job/51af903d-d8e8-45d3-85b5-1e763388365e/payload-integration-engineer

## About the Role

* Degree in mechanical, electrical, or aerospace engineering, or a related field, or equivalent practical experience
\n

 * Experience integrating sensors, payloads, or subsystems onto a vehicle or other physically constrained platform, taking them from interface definition through working hardware
\n

 * Comfort working across the mechanical and electrical boundary - able to define a mount and a load path as readily as a power and data interface
\n

 * Experience with the interfaces payloads actually use, such as Ethernet, serial, CAN, USB, PPS or other timing signals, and common video and sensor data formats
\n

 * Experience authoring or working to interface control documents, and holding mass, power, or data budgets across a changing configuration
\n

 * Willingness to travel and to operate in the field, including standing a payload up under time pressure in front of a customer
\n

 * U.S. Person status required (U.S. citizen, lawful permanent resident, or protected individual under 8 U.S.C. 1324b(a)(3)); this role involves access to ITAR- and EAR-controlled technical data
\n, We are looking for an engineer who is comfortable being the connective tissue between disciplines and between companies. The people who do well here are specific about where a boundary sits and who owns each side of it, they ask the awkward interface question early rather than discovering it on the flight line, and they trust measured payload performance over vendor datasheets. You should be able to move between CAD, a wiring diagram, a spectral plot, and a vendor call without losing the thread, and to keep your composure when a payload arrives the night before a customer evaluation and does not behave the way the ICD said it would.

## Description

Payload integration is where the aircraft stops being a platform and starts being a capability, and this role owns that transition end to end. This position requires U.S. Person status, as the work involves access to export-controlled technical data. You will define the mechanical and electrical interfaces that EO/IR cameras, gimbals, LiDAR units, RF and SIGINT packages, and comms relays attach through, hold the mass, CG, power, and data budgets those payloads have to fit within, and carry each integration from bench bring-up through flight validation of actual payload performance. You will work across mechanical, avionics, embedded software, autonomy, and flight test, and directly with payload vendors on ICDs and bring-up support. Expect to be on-site in Charlotte, and expect some travel to support customer evaluations where a payload has to be working the same day it arrives.