Avionics System Requirements Engineer | DOORS | ARP4754A | DO-178C | Systems Engineering | Aerospace

Technical Skills

- Bachelor’s or Master’s degree in any one of the following:
- Aerospace Engineering
- Avionics Engineering
- Electronics Engineering
- Electrical Engineering
- Computer Science
- Systems Engineering
- Instrumentation Engineering
- 8–15+ years of avionics systems engineering experience.
- Prior work experience with at least one OEM, Tier-1 avionics supplier, aircraft integrator, or certified airborne systems program.
- Experience in one or more avionics subsystems such as:
- Flight Management System (FMS)
- Datalink
- Radio Navigation
- HUD
- Air Data
- IRS
- Displays
- Communication
- Surveillance
- IMA-hosted applications

Must Have

- An experienced Avionics System Requirements Engineer who has previously performed requirements engineering activities for one or more avionics subsystems on an aircraft development or modification program.
- Expected to support onsite system engineering activities including requirements development, authoring, traceability, validation, review support, and compliance alignment with customer engineering processes and applicable aviation certification standards.
- Should be a practitioner-level engineer, meaning they should have already executed similar work on prior aerospace/OEM programs and should be able to contribute with limited supervision after onboarding to the customer’s process, tools, and templates.

Good to Have

- Prior experience in avionics subsystems such as:
- Flight Management System (FMS)
- Datalink / Communication Management
- Radio Navigation
- HUD / Head-Up Display
- Air Data System
- Inertial Reference System (IRS / ADIRS)
- Flight Control Interface Systems
- Displays / Crew Alerting
- Surveillance Systems
- Communication / Navigation / Identification Systems
- Mission or Utility Avionics Systems

Responsibilities

Avionics System Requirements Development and Authoring

- Author avionics system requirements based on stakeholder inputs, system architecture, safety requirements, operational concepts, and interface needs.
- Develop requirements at appropriate abstraction levels, including:
- Aircraft-level allocated requirements
- System-level requirements
- Subsystem-level requirements
- Interface requirements
- Derived requirements
- Safety-related requirements
- Apply customer-specific requirements writing rules, templates, naming conventions, and Ensure requirements are transparent, concise, complete, correct, feasible, verifiable, and traceable.




- Apply customer-specific requirements writing rules, templates, naming conventions, and review checklists.
- Convert informal engineering into structured requirements suitable for design, implementation, integration, and verification.
- Support refinement of existing requirements to remove ambiguity, duplication, inconsistency, or non-verifiable wording.
- Develop requirements for avionics functions such as:
- Navigation data processing
- Flight plan management
- Sensor input processing
- Data bus communication
- Display output behavior
- Failure annunciation
- Mode management
- Built-In Test (BIT) behavior
- Interface monitoring
- Degraded mode operation

Translation of Stakeholder, Safety, and System Needs into Requirements

- Interpret stakeholder requirements and convert them into measurable avionics system requirements.
- Analyze inputs from:
- Aircraft-level requirements
- Operational scenarios
- Functional Hazard Assessment (FHA)
- Preliminary System Safety Assessment (PSSA)
- System Safety Assessment (SSA)
- Interface Control Documents (ICDs)
- System architecture models
- Certification plans
- Customer standards and process guidelines
- Translate safety objectives and failure condition classifications into system-level design and verification requirements.
- Identify missing, incomplete, conflicting, or unclear stakeholder and system inputs.
- Capture derived requirements generated from architecture, design constraints, interface behavior, or safety analysis.
- Ensure each requirement is stated in a verifiable manner using appropriate language such as "shall."
- Define expected system behavior for:
- Normal operation
- Abnormal operation
- Failure conditions
- Loss of input data
- Invalid data
- Degraded modes
- Power-up and initialization
- Reversionary modes
- Maintenance modes

Certification and Process Compliance Support

- Support development of requirements in alignment with system development lifecycle processes such as ARP4754A.
- Ensure requirements are suitable for downstream compliance with applicable standards such as:
- ARP4754A for aircraft and system development
- ARP4761 / ARP4761A for safety assessment inputs




- DO-178C for software-related requirements allocation
- DO-254 for airborne electronic hardware-related requirements allocation
- DO-160 for environmental qualification considerations
- DO-297, where IMA platform allocation is applicable
- Support certification-oriented review of requirements to ensure:
- Traceability
- Verifiability
- Completeness
- Correctness
- Design independence where required
- Linkage to safety and compliance objectives
- Participate in certification Ensure requirements are aligned with customer/OEM methodology and certification artifact expectations.
- Support preparation and review of evidence required for certification audits and internal quality gates.
- Participate in certification and quality reviews related to system requirements.
- Use customer-designated requirements management tools such as:
- IBM DOORS / DOORS Next
- Polarion
- Jama Connect
- Siemens Teamcenter
- PTC Integrity
- Codebeamer
- Enterprise Architect / Cameo, where applicable
- Generate traceability reports, review packages, gap reports, and change impact summaries.
- Should have hands-on working experience in at least one industry-standard requirements management tool and should understand how traceability is used during reviews, audits, verification planning, and change control.

Requirements Review, Validation, and Quality Support

- Participate in requirements review meetings with customer/OEM teams, suppliers, and cross-functional engineering stakeholders.
- Support validation of requirements against stakeholder needs and operational use cases.
- Support review of requirements with:
- System engineering teams
- Safety teams
- Software teams
- Hardware teams
- Integration and test teams
- Certification representatives
- Supplier engineering teams
- Provide comments, dispositions, and technical justifications during peer reviews and formal reviews.
- Support requirements baseline creation and change control activities.
- Assist in defect resolution related to requirement ambiguity, interface mismatch, or verification failure.

Tools

- Requirements Management Tools:
- IBM DOORS
- DOORS Next Generation
- Polarion
- Jama Connect
- Codebeamer
- PTC Integrity
- Teamcenter Requirements
- Architecture / Modeling Tools:
- Cameo Systems Modeler
- MagicDraw
- Enterprise Architect
- Rhapsody
- MATLAB / Simulink (where applicable)
- Review and Lifecycle Tools:
- JIRA
- Azure DevOps
- Git / Configuration Management Tools
- Change Control and Problem Reporting Tools
- Customer-specific PLM or ALM Tools

📌 Avionics Systems Requirements EngineerA, DOORS,C,IBM DOORS, Polarion) (Montreal)
🏢 Astra North Infoteck
📍 Montreal