• Sits one level above the UAV System Architect (who leads architecture as a technical IC). The Director owns the SE function, process, team, and cross-platform consistency; the Architect owns the technical design synthesis on a given platform.
• Operates within the “Technology Ownership” doctrine — the division masters software, system design, power/thermal, BSP/RTOS, flight software/autonomy, and cybersecurity in-house, and deliberately does not self-manufacture commodity components (SoC, cells, ESCs at current volumes). The System Director is the guardian of this boundary.

Platform portfolio under scope:

• X-URBAN — urban multirotor; government and Japan-market entry platform
• X-FIELD — agricultural precision sprayer
• X-CARGO — long-range delivery (fixed-wing / VTOL)

▍ 3.1  System Architecture & Design Ownership

• Own the reference architecture across all three platforms — driving modularity, component reuse, and a common flight-controller / mission-computer core to maximize leverage across the portfolio.
• Translate product strategy, market requirements (Vietnam government, Japan, Korea), and regulatory constraints into a coherent set of system-level requirements, with full traceability from stakeholder need to verification.
• Own all Interface Control Documents (ICDs) between FC, MC, payload/gimbal, datalink/C2, Remote ID module, and ground control segment.
• Govern Reuse / Adapt / Build decisions across FC firmware, perception, autonomy, and hardware — keeping in-house mastery where it matters and avoiding reinvention where it does not.
• Own system-level budgets and allocations: mass/CG, power/thermal, endurance, link budget, reliability/availability, latency.

▍ 3.2  Systems Engineering Process & Verification

• Establish and run the full SE lifecycle aligned to ARP4754A/B: requirements → design → integration → verification → validation, with disciplined configuration and change management.
• Own the V&V strategy end to end — bench, HIL/SIL, ground integration, and flight-test campaigns — and the evidence chain that proves the system meets its requirements.
• Drive safety and reliability engineering: FHA / PSSA / SSA (ARP4761A), FMEA/FMECA, and hazard/risk closure.
• Institutionalize design-review governance: SRR, PDR, CDR, TRR as real decision gates, not formalities.

▍ 3.3  Certification, Airworthiness & Regulatory Interface

• Own design assurance for DO-178C (airborne software) and DO-254 (airborne hardware) where the product tier requires it.
• Lead JARUS SORA / SAIL safety-case development and the operational safety argument.
• Drive certification pathways: CAAV type acceptance (Vietnam), JCAB Level 4 (Japan), KC/RRA (Korea) — serving as engineering authority before these bodies.
• Ensure compliance posture across ASTM F3411 (Remote ID), Decree 288/2025/ND-CP, QCVN 53, and export-control regimes (NDAA, UFLPA traceability).

▍ 3.4  Cross-Functional & Business Engagement

• Convert product and go-to-market strategy into a technical roadmap and architecture the whole organization can execute against.
• Provide technical credibility and depth in customer, partner, and regulator engagements (government customers, NEXCO/JA in Japan, expressway/port/logistics operators in Korea).
• Own program-level technical risk — surfacing, quantifying, and driving mitigation of issues that threaten schedule, cost, certification, or performance.
• Be the engineering voice in make-vs-buy, supplier, and IP-boundary strategy at the leadership table.

▍ 3.5  Team Leadership & Capability Building

• Build, lead, and grow the systems-engineering team across Hanoi and the Shenzhen hub.
• Establish SE standards, templates, MBSE practice, and RASIC responsibility matrices that scale beyond the founding team.
• Mentor architects and V&V engineers; own recruiting, performance, and the long-term capability roadmap for the function.

▍ 3.6  Supplier Technical Governance & IP Protection

• Set and enforce technical requirements on suppliers (vehicle-design/manufacturing partners); review their designs; require SBOM disclosure and open-BOM cost transparency.
• Protect IP boundaries — FC source code, ESC FOC firmware, hardware design files, BSP — and ensure contracts carry correct technical assignment and carve-outs.

Enforce supply-chain traceability for export markets (non-China sourcing where required; UFLPA/NDAA documentation).


 

---

Your Safety and Data Security Matter to Us

Manpower is committed to a safe, secure, and transparent hiring process. We will never request any form of payment, banking details, or sensitive personal information at any stage of recruitment.

If you receive any suspicious communication claiming to be from Manpower, please report it immediately to: [email protected]

---

An toàn & Bảo mật Dữ liệu của bạn là ưu tiên của chúng tôi

Manpower cam kết mang đến quy trình tuyển dụng an toàn, minh bạch. Chúng tôi sẽ không bao giờ yêu cầu bất kỳ khoản phí nào, thông tin tài khoản ngân hàng hoặc dữ liệu cá nhân nhạy cảm trong suốt quá trình tuyển dụng.

Nếu bạn nhận được liên hệ đáng ngờ tự xưng là Manpower, vui lòng báo cáo ngay qua email: [email protected]