
Systems Software Integration Engineer
Posted 2 days ago
The role in short
Builds and tests the C++/Python adapters that connect NODA's autonomy platform to Taiwanese partners' vehicles and sensors, on site with partners and in field exercises.
Location: Taiwan (Hybrid)
Travel: ~20% typical; increases during field exercises and partner engagements in Taiwan
Engagement: Full-time or contractor — open to both
Citizenship: Must be legally authorized to work in Taiwan. If not a Taiwanese citizen or permanent resident, the candidate must possess valid, independent authorization to work in Taiwan (e.g., a Taiwan Employment Gold Card or an Alien Permanent Resident Certificate (APRC)). Employer sponsorship is not available for this position.
About NODA
NODA is a veteran-owned, venture-backed technology company transforming how unmanned systems collaborate in complex, mission-critical environments. As NODA scales across products, partners, and deployment environments, keeping the system coherent in practice — not just on paper — is what separates a platform that works in the field from one that only works in a demo.
Our Systems Software Integration Engineers bridge NODA's autonomy orchestration platform with the hardware, protocols, and partner ecosystems our customers bring to the table — cutting through ambiguity on both sides, translating technical findings into actionable decisions, and making sure integration problems get resolved, not just escalated.
The Role
We are looking for a Systems Software Integration Engineer to be NODA's technical presence on the ground in Taiwan. You will own the integration layer between our autonomy orchestration platform and the vehicle platforms, sensors, and autonomy stacks our Taiwanese partners bring — onboarding new systems, debugging cross-system issues, and representing NODA technically in partner and government engagements. You will be the person who makes NODA's platform actually work with Taiwan's platforms in the field.
This is a software engineering role with an integration and liaison mandate. You will work alongside other Taiwan-based engineers and third-party contractors — this is a collaborative effort, not a solo one.
You will initially report to the Head of Engineering and transition to the Solutions Engineering team as the Taiwan program matures. The long-term trajectory for the right person is leading NODA's engineering presence in Taiwan.
What You'll Do
- Build and maintain adapters and translation layers connecting NODA's autonomy orchestration platform to Taiwan partner vehicle platforms, sensors, and third-party autonomy stacks
- Own integration testing end-to-end: from bench bring-up to HITL/SITL validation before live field deployment
- Debug cross-system issues spanning application software, messaging middleware, networking, embedded Linux, and RF — owning the investigation even when root cause sits below your primary depth
- Interface with partner firmware and BSP teams to isolate failures at the hardware/software boundary; you understand embedded Linux and OS constructs well enough to have that conversation credibly
- Act as NODA's primary technical interface in Taiwan — with OEMs, government partners, hardware vendors, and field teams — in both English and Mandarin
- Characterize system behavior under degraded, intermittent, or contested link conditions relevant to Taiwan's operational environment
- Translate partner and field requirements into system constraints the NODA U.S. engineering team can build against; maintain Interface Control Documents and integration contracts
- Build observability into integration components — logging, tracing, metrics — and support field exercises that validate NODA's platform in live conditions
Required Qualifications
- 4–8 years of professional software engineering experience, with meaningful time on systems integration, middleware, drivers, or robotics software
- Strong proficiency in C++ and/or Python; production-quality code, not scripting
- Working knowledge of embedded Linux and OS constructs — process scheduling, IPC, device architecture — sufficient to debug integration failures and hold a credible conversation with a partner firmware team; driver and BSP authorship not required
- Pub-sub middleware fluency — Zenoh or comparable; understanding of routing, key-expression patterns, and latency behavior in distributed multi-agent contexts
- Solid working knowledge of networking fundamentals — TCP/IP, multicast, basic routing — sufficient to debug connectivity and performance issues
- Working familiarity with RF/wireless concepts — link quality, interference, basic link budget reasoning — conversational depth, not specialist design
- Demonstrated ability to debug across layers — application, middleware, network, and hardware-adjacent — and to know when to pull in a specialist versus push through independently
- Experience with Linux systems and command-line debugging tooling
- Bilingual: English (professional fluency) and Mandarin Chinese (Traditional, professional fluency)
- Must be legally authorized to work in Taiwan. If not a Taiwanese citizen or permanent resident, the candidate must possess valid, independent authorization to work in Taiwan (e.g., a Taiwan Employment Gold Card or an Alien Permanent Resident Certificate (APRC)). Employer sponsorship is not available for this position. This role is 100% Taiwan-based.
- Due to the nature of this position, candidates must be legally authorized to work in Taiwan and must be eligible to access export-controlled technology and comply with all applicable U.S. export control laws, Taiwan regulations, and government security requirements.
- Able to travel within Taiwan for field exercises and partner/military deployments
Preferred Qualifications
- Hands-on with vehicle control protocols and autopilot software — MAVLink, ArduPilot, PX4 — with ability to debug at the message level
- Experience with autonomous systems or unmanned vehicles — UAV, UGV, USV — in an integration or field context
- Experience with real-time or low-latency messaging middleware — DDS, ROS/ROS2, ZeroMQ, MQTT — in distributed or multi-agent contexts
- Sensor integration experience: LIDAR, cameras, IMUs, GNSS, EO/IR
- Experience with HITL/SITL pipelines or sim-to-field validation workflows
- Prior work in Taiwan defense or government-adjacent programs
- Familiarity with GCS/C2 tooling: ATAK, QGroundControl, Mission Planner, or similar
- Experience authoring ICDs, requirements traceability, or integration test plans
- Exposure to tactical radios, MANET, or mesh networking in a support/integration capacity
Skills & Attributes
- Cuts through ambiguity — comfortable when the problem isn't fully defined and the answer requires pulling from multiple domains
- Effective bridge between technical teams and non-technical stakeholders — can explain a firmware timing issue to a government program manager and a schedule risk to a senior engineer, in two languages
- Strong ownership instinct: debugs to root cause, doesn't hand off at the first sign of unfamiliar territory
- Pragmatic with vendor partners; pushes back when partner-side decisions create downstream integration risk
- Documentation-disciplined: translates field and debugging findings into structured specs and crash reports the U.S. team can act on without being in the room
- Mission-driven with strong agency — NODA expects every hire to operate with ownership, not wait for direction
Benefits & Perks
Our culture fosters collaboration, respect, and trust, empowering passionate people to do their best work. We offer a competitive salary, comprehensive benefits, and opportunities for career growth. In addition to an opportunity to take part in an innovative, collaborative and fast-growing business with a highly motivated and skilled team, we also take pride in taking care of our employees. Here are just a few ways that we show our appreciation:
- Comprehensive National Health Insurance (NHI) coverage, including medical, dental, and vision care
- Pension plan + employer contributions to support your retirement and long-term savings goals
- Competitive time off and leave to support rest, recovery, and personal needs
- Paid parental leave (where eligible)
- Paid public holidays and holiday observance in accordance with Taiwan law
- Flexible working arrangements, where business needs permit
- Professional development and learning opportunities
Growth Path at NODA
Systems Software Integration Engineer (Taiwan): Reports to Head of Engineering. Owns vehicle and sensor onboarding, integration testing, and field technical support in Taiwan. Primary liaison between NODA's U.S. engineering team and Taiwan partners.
Senior Systems Software Integration Engineer / Solutions Engineer: Transitions to Solutions Engineering. Leads technical delivery for Taiwan customer programs; owns partner-facing integration architecture.
Engineering Lead — Taiwan: Builds and leads NODA's Taiwan engineering team. Owns technical direction, hiring, and partner relationships in-market.
Export Control Compliance
To conform to U.S. government export control regulations, including the International Traffic in Arms Regulations (ITAR) and Export Administration Regulations (EAR), you must be a U.S. citizen, lawful permanent resident of the U.S., protected individual as defined by 8 U.S.C. 1324b(a)(3), or otherwise eligible to obtain the required authorizations from the U.S. Department of State or U.S. Department of Commerce.
Equal Opportunity Statement
NODA AI is an Equal Opportunity Employer committed to fostering a diverse, inclusive, and respectful workplace and to maintaining equitable employment and hiring practices. We provide equal employment opportunities to all applicants and employees and make all employment decisions without regard to race, color, religion, sex (including pregnancy, childbirth, and related medical conditions), sexual orientation, gender identity or expression, national origin, age, disability, genetic information, protected veteran status, or any other characteristic protected by applicable federal, state, or local law.
As a federal contractor, NODA AI complies with all applicable equal employment opportunity and affirmative action requirements, including Section 503 of the Rehabilitation Act of 1973, as amended, and the Vietnam Era Veterans' Readjustment Assistance Act of 1974 (VEVRAA), as amended. We are committed to providing reasonable accommodations to qualified applicants and employees with disabilities throughout the recruiting, hiring, and employment process.
Consistent with applicable federal, state, and local laws, qualified applicants with criminal histories will be considered for employment in a manner consistent with applicable fair chance and ban-the-box laws, including the Fair Chance Initiative for Hiring Ordinance where applicable. We actively encourage qualified individuals of all backgrounds, including women, minorities, protected veterans, and individuals with disabilities, to apply.
NODA AI is committed to fostering an inclusive, supportive, and accessible work environment for all applicants and employees. If you require accommodations or assistance during the application process, please don’t hesitate to reach out to us at careers@NodaIntelligence.ai or contact your recruiter so we can provide the support you need.
Prep for this interview
5 questions likely to come up at NODA AI, each matched to a line in this posting.
- 1Discovery and scoping
They wrote: “Translate partner and field requirements into system constraints the NODA U.S. engineering team can build against; maintain Interface Control Documents and integration contracts”
Tell me about a time the customer asked for one thing but needed another.
How to answer
Why they ask: Good FDEs spot when a request is a guess at a solution. They want proof you can redirect a customer without losing their trust.
- What they asked for, and the detail that made you doubt it
- How you tested the doubt (shadowed users, looked at logs, ran a quick prototype)
- How you made the case to the customer
- What shipped and what changed for them
Tip: Pick a story where you checked your hunch with data or users before pushing back.
- 2Integrations and APIs
They wrote: “This is a software engineering role with an integration and liaison mandate. You will work alongside other Taiwan-based engineers and third-party contractors — this is a collaborative effort, not a solo one.”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 3Coding
They wrote: “4–8 years of professional software engineering experience, with meaningful time on systems integration, middleware, drivers, or robotics software”
Fetch every record from a paginated API that rate-limits you and sometimes fails.
How to answer
Why they ask: A very common practical exercise. It looks easy; the follow-ups are about failure.
- Loop on the next-page token until there isn't one
- Back off and retry on rate limits and temporary errors, with a limit
- Save progress so a crash resumes from the last page
- Test with a fake API that fails on purpose
Tip: Write the happy path quickly, then spend your time on retries and resuming.
- 4Ownership and working with customers
They wrote: “Build and maintain adapters and translation layers connecting NODA's autonomy orchestration platform to Taiwan partner vehicle platforms, sensors, and third-party autonomy stacks”
Tell me about a project where the requirements kept changing. What did you do?
How to answer
Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.
- The project and why requirements kept moving
- What you did to pin them down (short demos, written decisions)
- The trade-offs you made to keep shipping
- The result, with a number if you have one
Tip: Show how you reduced the change, beyond how you coped with it.
- 5Travel
They wrote: “Travel: ~20% typical; increases during field exercises and partner engagements in Taiwan”
How do you handle being on the road with customers for weeks at a time?
How to answer
Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.
- Your past travel or on-site experience
- How you stay productive away from the team
- What travel level works for you, said plainly
Tip: Be honest about what works for you. A mismatch here hurts both sides later.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.


