Software Integration Lead

Integration Leadership & HIL Enablement

• Lead software integration across flight software, avionics, and system interfaces.
• Partner day-to-day with the avionics engineer leading HIL bring-up to debug, isolate, and close cross-domain issues (HW/FW/SW).
• Define and implement HIL software integration components, harnesses, automation, and observability (logging/telemetry capture, instrumentation, reproducibility tooling).
• Drive structured triage and root-cause isolation using hypothesis → experiment → evidence → regression, including time-boxing and controlled experiments.
• Establish integration readiness criteria and “integratable build” standards for HIL and system-level testing (lightweight gates that enforce repeatability).
• Support bench-level debugging using invasive and non-invasive tools as needed (serial consoles, packet capture, loopbacks, fault injection; scope/logic analyzer familiarity strongly preferred).

External Delivery Interface & Release Discipline

• Serve as the primary day-to-day technical interface for software delivery coordination with external software vendors
• Own software delivery truth: require and curate release artifacts for each drop (versioning, release notes, hashes/manifests, known issues, environment assumptions) and map them to tested capabilities and defects.
• Validate external drops in Portal’s integration environment; identify environment deltas (libraries/config/hardware assumptions) and drive closure plans with clear owners and evidence.
• Communicate integration status, blockers, bounded risks, and schedule impacts to leadership and cross-functional stakeholders.
• Support go/no-go decisions for integration milestones using traceable test evidence and documented assumptions.

Foundational Practices & Program Memory

• Establish essential guardrails for repeatable integration: configuration baselines, build provenance, test evidence captures, and documentation that enables speed rather than process.
• Produce durable technical artifacts others can use without you (interface contracts, runbooks, failure catalogs, integration notes, debug playbooks).
• Partner with systems engineering to keep integration work aligned to requirements, interfaces, and mission constraints while maintaining a bias for action under ambiguity.
• Contribute to internal tooling and workflows (CI, artifact storage, issue tracking) as needed to support integration velocity and rigor.
• Provide technical mentorship and integration discipline to engineers interacting with HIL, test infrastructure, and external software deliveries.

• 8+ years of software engineering experience with significant responsibility for system integration, test infrastructure, or delivery in complex systems.
• Demonstrated experience operating at the HW/FW/SW boundary (embedded systems, avionics-like interfaces, distributed systems, or hardware-integrated software).
• Proven record of hands-on bench integration (HIL/test racks/system test benches) including building or operating integration harnesses and automation.
• Experience coordinating delivery across teams and/or external partners without direct authority, including driving to reproducible evidence.
• Strong debugging and root-cause isolation skills using disciplined, evidence-based workflows.

• Startup/small-team experience where you owned integration delivery under ambiguous requirements and limited resources.
• Aerospace/spacecraft, avionics, defense, robotics, or other mission-/safety-critical system experience.
• Release engineering experience (build provenance, artifact management, regression discipline).
• Familiarity with instrumentation and bring-up techniques (serial logs, packet capture, loopbacks, fault injection; oscilloscopes/logic analyzers are a plus).
• Ability to translate ambiguous integration failures into clear hypotheses, experiments, and actionable next steps (evidence over opinion).
• Strong cross-functional communication: can brief leadership crisply and collaborate deeply with engineers at the bench.
• Practical release discipline: build provenance, configuration control, and test evidence capture for repeatability.
• Boundary discipline and collaboration skills (clear ownership, respectful escalation, conflict navigation; works effectively with avionics and external partners).
• Strong prioritization and time-boxing under schedule pressure; knows when to escalate and when to iterate.