Senior RAMS Engineer (Reliability, Availability, Maintainability & Safety)

Uppgiften

Define and own Satellite‑level Reliability and Availability targets, ensuring they are technically justified, demonstrably verifiable, and flexible enough to accommodate design evolution. Develop and maintain the system‑level Reliability model, including Fault Tree (FT) structures, allocations, and quantitative assessments used to verify compliance with Rel & Avail targets. Estimate and track Availability of the service, explicitly accounting for recoverable failures through MTBF and MTTR modelling, and ensuring assumptions are operationally credible. Identify and quantify the main contributors to mission failure, providing clear, prioritized inputs to system design, risk mitigation, and decision‑making. Lead and execute RAMS analyses across the program lifecycle, including FTA, Reliability Allocation, FMECA (including FMECA to support FDIR), sensitivity analyses, and formal RAMS reporting.

Vad vi förväntar oss

• 10+ years of hands‑on experience in RAMS engineering for complex space systems, with direct responsibility for Reliability and Availability assessments.
• Shall possess a foundational knowledge of electronic systems and electronic devices.
• Demonstrated experience on at least one space mission or flight‑critical program, where RAMS outputs directly influenced design decisions and risk acceptance.
• Proven capability to build and quantify Fault Tree models and perform Reliability Allocation from system level down to critical items.
• Solid experience performing FMECA at system and item level, including use of results to support FDIR and design mitigations.
• Strong background in data gathering and data analysis for RAMS purposes, including use of reliability databases, assumptions management, and uncertainty handling.
• Experience estimating service availability, including operational concepts, recovery strategies, and realistic MTTR assumptions.
• Prior involvement in early‑phase RAMS activities (pre‑SRR / SRR), where incomplete data and evolving architectures are the norm.
• Familiarity with Legacy & NewSpace programs, where RAMS must be pragmatic, not bureaucratic.
• Experience updating RAMS models to reflect design changes and optimization loops, not just producing static reports.
• Exposure to sensitivity analysis and trade‑off studies used to guide architecture or redundancy decisions.