System Engineer (Digital)

THALES SOLUTIONS ASIA PTE. LTD.; Singapore; On-site; SGD 80,000 - 120,000; Full time

Job summary

Thales Solutions Asia Pte. Ltd. seeks a systems and software requirements engineer to drive requirements engineering across the lifecycle, adhering to ISO/IEC/IEEE 29148 and INCOSE guidance.

The role emphasizes traceability from stakeholder needs to verification evidence, and operation within standard lifecycle processes. You will implement a digital requirements toolchain, maintain living traceability structures, and author verification strategies tied to defined acceptance criteria.

Responsibilities

• Elicit, analyse, specify, and manage system and software requirements across the lifecycle following ISO/IEC/IEEE 29148 and INCOSE guide.
• Maintain bidirectional traceability from stakeholder need to verification evidence.
• Operate the requirements process within an ISO/IEC/IEEE 15288 lifecycle frame.
• Run a digital requirements engineering toolchain with a managed repository and change control.
• Author and own verification & validation strategy: map each requirement to its verification method.

Job description

Responsibilities:

• Elicit, analyses, specify, and manage system and software requirements across the lifecycle, followingISO/IEC/IEEE 29148(requirements engineering) and theINCOSE Guide to Writing Requirements (GtWR) - every requirement necessary, unambiguous, singular, feasible, andverifiable, and every requirementsetcomplete, consistent, and able to be validated.
• Maintainbidirectional traceability: stakeholder need → system requirement → architectural element → implementation → verification evidence. This is the artefact an auditor asks for, and it must exist as a living structure, not a retrofit.
• Operate the requirements process within anISO/IEC/IEEE 15288lifecycle-process frame (as codified in theINCOSE Systems Engineering Handbook, 5th edition): stakeholder needs & requirements definition, system requirements definition, architecture definition, verification, validation, transition, operation.
• Run adigital requirements engineeringtoolchain rather thandocuments-in-a-folder:requirements held in a managed repository with change control, baselines, and query-able trace links (e.g. Jama Connect, Polarion, DOORS or an equivalent the organisation standardises on.
• Author and own verification & validation strategy: define acceptance criteria atrequirement-authoringtime (not after the fact), and map each requirement to its verification method - inspection, analysis, demonstration, or test.
• Following Thales processes and practises and contribute to their improvement
• Contribute production code across the stack - able to read, review, and where needed write both service-side and client-side code well enough to keep requirements honest against implementation reality.
• Design and reviewAPIs and service contractsas first-class interfaces (a system interface is a requirements artefact, not just a coding detail).
• Work fluently with the platform's delivery mechanics: version control, CI/CD pipelines, automated testing, and the review gates that make changes auditable.
• Translate abstract non-functional requirements (latency, availability, recoverability, security posture) into concrete, testable engineering targets and confirm they are met.
• Architect and review solutions on cloud infrastructure with an emphasis onsecurity, data residency, resilience, and cost - and record those decisions asArchitecture Decision Records (