Job Description and Requirements
Software system safety, an element of the total safety and software development program, cannot be allowed to function independently of the total effort of the product.
A software specification error, design flaw, or the lack of generic safety-critical requirements can contribute to or cause a system failure or erroneous human decision.
Once the "functional" software safety analyses are completed the software engineering team will know where to place safety emphasis and what functional threads, functional paths, domains and boundaries to focus on when designing in software safety attributes to ensure correct functionality and to detect malfunctions, failures, faults and to implement a host of mitigation strategies to control hazards.
Analyze customer requirements, SW architecture design and technical safety concept then identify product potential risks.
Perform Software Design Analysis (Critical path analysis and Freedom from Interference Analysis) on both architecture and code levels for projects from different product groups.
Perform Qualification of software components.
Perform Confidence in the use of software tools.
Participates in GEEDS Technical Development Plan.
Specifying software safety mechanisms for fault tolerance and fault avoidance on the architecture level and code levels.
Support in the Software integration with safety mechanisms in Software architecture.
Attend necessary customer meetings or Software team workshops to clarify and explain safety related issues.
B.Sc. in Communication or Computer Engineering or Computer science.
Basic hardware knowledge.
Strong analytical skills and root cause analysis.
Strong problem solving and debugging skills.
Good communication skills.
Excellent command of English language is a must.
Experience in safety-critical software development and ISO 26262 is a plus.
Experience in AutoSAR is a Plus.
From 0 to 2 years of relevant experience.