
Functional safety explained: a practical introduction for engineers
Modern products are full of systems that keep people safe: the brakes in an electric truck, the signalling on a railway, the emergency stop on an industrial robot. When those systems depend on electronics and software, a single fault can have serious consequences. Functional safety is the discipline that makes sure they do not.
The IEC describes functional safety as the part of overall safety that depends on a system working correctly in response to its inputs. A classic example is a sensor that detects overheating in a motor and cuts the power before it fails. The motor is not made safer by insulation or guards, but by a function that has to work every time.
For engineers in automotive, rail, energy and industrial automation, functional safety is no longer a niche. It shapes how systems are designed, built, tested and documented. This article explains the key concepts, the main standards and what it means for your daily work and career.
Key concepts
Hazard analysis and risk assessment
Everything starts with the question: what could go wrong, and how bad would it be? Engineers identify hazards, such as unintended acceleration or a motor that does not stop, and assess how severe, how likely and how controllable each one is. The result decides how much rigour the rest of the work needs.
Safety integrity levels
The higher the risk, the stricter the requirements. Standards express this as integrity levels:
- IEC 61508 (general): SIL 1–4, with SIL 4 the highest.
- ISO 26262 (road vehicles): ASIL A–D, plus QM for no safety requirement, with ASIL D the highest.
- EN 50126/50128/50129 (rail): SIL 1–4, with SIL 4 the highest.
A higher level means more demanding methods for design, verification and independent assessment, not just more testing at the end.
The safety lifecycle
Functional safety is not a final check. It runs through the entire development:
- Define the system and its hazards.
- Set safety goals and assign integrity levels.
- Break the goals down into technical safety requirements for hardware and software.
- Design and implement against those requirements.
- Verify and validate that each requirement is met.
- Assess and document the result in a safety case, and maintain safety through production and operation.
Many teams follow a V-model, where each design step on the way down has a matching verification step on the way up.
Standards by industry
IEC 61508 is the foundation. Many industries have their own standards built on the same principles.
- General / basis for others: IEC 61508
- Road vehicles: ISO 26262
- Rail: EN 50126, EN 50128 (software), EN 50129 (electronics)
- Process industry: IEC 61511
- Machinery: ISO 13849 and IEC 62061
- Aerospace: DO-178C (software) and DO-254 (hardware)
- Medical devices: IEC 62304 (software)
The concepts carry over well between them. An engineer with ISO 26262 experience can usually get up to speed on EN 50128 or IEC 61511 much faster than someone starting from scratch.
Cybersecurity is increasingly linked to safety. In automotive, ISO/SAE 21434 is often applied alongside ISO 26262, since a security weakness can become a safety risk.
What it means in your daily work
You do not have to be a safety specialist to work on a safety-critical project. But functional safety affects how every engineer on the team works.
- Requirements come first. Every piece of design and code should trace back to a requirement, and every requirement to a test. Tools such as IBM DOORS, Polarion or Jama are common for managing this traceability.
- Coding rules are stricter. Software usually follows a coding standard such as MISRA C/C++, with static analysis to enforce it.
- Verification is planned, not improvised. Unit tests, integration tests, hardware-in-the-loop and code coverage targets are defined up front, and at higher integrity levels they must be reviewed independently.
- Hardware is analysed for faults. Hardware engineers use methods such as FMEA, FMEDA and fault tree analysis to show how the system behaves when components fail.
- Documentation is part of the product. Design decisions, reviews and test results are collected as evidence in a safety case. If it is not documented, it did not happen.
- Tools need to be trusted. Compilers, code generators and test tools may need to be qualified, so that a tool error cannot introduce a hidden fault.
For many engineers, this is what makes the work rewarding. You know exactly why every part of the system is there, and that it works.
Functional safety as a career
Experience with functional safety is valuable in almost every engineering role in safety-critical industries:
- Embedded software engineers who know ISO 26262 or EN 50128 are sought after in automotive, rail and industry. See our Embedded Software Engineer role.
- Electronics and hardware engineers who can run FMEDA and design for diagnostic coverage. See our Electronic Engineer role.
- Automation engineers working with safety PLCs, safety functions on machines and IEC 61511 in process industry. See our Automation Engineer role.
- Functional safety engineers and managers who own the safety analyses, the safety plan and the safety case.
How to get started
- Learn the basics of the standard in your industry. Start with the concepts: hazard analysis, integrity levels and the safety lifecycle.
- Get involved in a safety-critical project. The fastest way to learn is to work in a team that already follows the process.
- Practise traceability and structured testing. These habits matter as much as knowing the standard itself.
- Consider a certification. Organisations such as TÜV offer functional safety engineer programmes. They are not required, but they are a clear signal on a CV.
Read more about embedded systems and the mobility and aerospace industry.
Want to work on safety-critical systems?
We have open roles for engineers in Stockholm, Gothenburg and Mälardalen, with assignments in vehicles, rail, energy and industry where safety matters. Whether you already work with functional safety or want to take the step, we would like to hear from you.
See all open roles or send an open application.
FAQ
What is functional safety?
Functional safety is the part of overall safety that depends on a system working correctly, for example a sensor and control unit that stop a motor before it overheats. It applies to electrical, electronic and software-based systems.
What is the difference between SIL and ASIL?
SIL (Safety Integrity Level) is used in IEC 61508 and many related standards, from SIL 1 to SIL 4. ASIL (Automotive Safety Integrity Level) is used in ISO 26262 for road vehicles, from ASIL A to ASIL D. Both express how strict the requirements are, but they are defined differently and are not directly interchangeable.
Do I need a certification to work with functional safety?
No. Most engineers learn it through projects. A certification can strengthen your CV, especially for dedicated functional safety roles.
Is functional safety the same as cybersecurity?
No, but they are closely linked. Functional safety protects against faults, while cybersecurity protects against attacks. In connected vehicles and industrial systems, both are needed.
Which industries need functional safety engineers in Sweden?
Mainly automotive and heavy vehicles, rail, aerospace and defence, energy and process industry, and industrial automation.

