Avionics System Requirements Engineer

Tata Consultancy Services (TCS) is an equal opportunity employer, and embraces diversity in race, nationality, ethnicity, gender, age, physical ability, neurodiversity, and sexual orientation, to create a workforce that reflects the societies we operate in. Our continued commitment to Culture and Diversity is reflected in our people stories across our workforce and implemented through equitable workplace policies and processes.

Tata Consultancy Services (BSE: 532540, NSE: TCS) is the technology partner of choice for industry-leading organizations worldwide. Since its inception in 1968, TCS has upheld the highest standards of innovation, engineering excellence and customer service.

It has set an aspiration to become the world's largest AI-led technology services company and is enabling its clients to transform themselves across the full AI stack, from infrastructure to intelligence.

Rooted in the heritage of the Tata Group, TCS is focused on creating long term value for its clients, its investors, its employees, and the community at large. With a highly skilled workforce spread across 56 countries and 194 service delivery centers across the world, the company has been recognized as a top employer in six continents. With the ability to rapidly apply and scale new technologies, the company has built long term partnerships with its clients. Many of these relationships have endured into decades and navigated every technology cycle, from mainframes in the 1970s to artificial intelligence today.

Job Description :-

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
• HUD / Head-Up Display
• Air Data System
• Inertial Reference System / IRS / ADIRS
• Flight Control Interface Systems
• Displays / Crew Alerting
• Communication / Navigation / Identification Systems
• Mission or utility avionics systems

Responsibility of / Expectations from the Role

1

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
• Interface requirements
• Safety-related requirements

2

• Ensure requirements are clear, 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

3

• Develop requirements for avionics functions such as:
• Sensor input processing
• Data bus communication
• Display output behavior
• Failure annunciation
• Mode management
• Built-In Test / BIT behavior
• Interface monitoring
• Degraded mode operation

4

Translation of Stakeholder, Safety, and System Needs into Requirements

• Interpret stakeholder requirements and convert them into measurable avionics system requirements.
• Analyze inputs from:
• Preliminary System Safety Assessment — PSSA
• System Safety Assessment — SSA
• System architecture models
• Certification plans
• Customer standards and process guidelines

5

• 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.”

6

• Normal operation
• Abnormal operation
• Failure conditions
• Loss of input data
• Invalid data
• Degraded modes
• Power-up and initialization
• Reversionary modes
• Maintenance modes

7

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

8

• Support certification-oriented review of requirements to ensure:
• Verifiability
• Correctness
• Design independence where required
• Linkage to safety and compliance objectives
• 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.

9

• Use customer-designated requirements management tools such as:
• IBM DOORS / DOORS Next
• PTC Integrity
• Enterprise Architect / Cameo, where applicable
• Generate traceability reports, review packages, gap reports, and change impact summaries.

10

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.

11

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

12

Should have experience with one or more of the following tools

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.

Thank you for your interest in TCS.

Candidates that meet the qualifications for this position will be contacted within a 2-week period.

#J-18808-Ljbffr