01Introduction
Overview
Automotive software is defined by scale, regulation and long-term responsibility: many variants, many suppliers, and a vehicle that must remain safe and secure for its entire service life.
We contribute senior engineering to the parts of the vehicle where embedded software, communication and integration meet, and we produce the evidence that safety and cybersecurity processes require.
02Engineering challenges
What makes this sector difficult.
- 01
Architectures in transition
The move from dozens of ECUs to zonal and central compute changes where software runs, how it communicates and who owns which interface.
- 02
Safety and cybersecurity by regulation
Functional safety and cybersecurity are type-approval matters. Every architectural and process decision has to produce evidence for both.
- 03
Mixed criticality on shared hardware
Safety-relevant functions, infotainment and connectivity share compute platforms. Isolation and timing guarantees must be designed, not assumed.
- 04
Updating vehicles in the field
Over-the-air updates must be secure, robust against interruption and traceable across a fleet of software variants.
03Typical systems
The systems we work on.
- Telematics and connectivity units
- Infotainment and digital cockpit platforms on Embedded Linux
- Zonal and central compute architectures
- ECU software and gateways (CAN, CAN FD, Automotive Ethernet)
- Over-the-air update chains
- ADAS prototypes, test vehicles and test benches
04How we contribute
Capabilities applied to this sector.
- 02Software & Systems ArchitectureSoftware and E/E architecture work for zonal and central compute, with explicit interfaces and partitioning decisions.
- 01Embedded Software EngineeringEmbedded Linux and RTOS platforms for telematics, cockpit and gateway units, including secure boot and update clients.
- 03Systems IntegrationIntegration of in-vehicle networks and middleware (CAN, Automotive Ethernet, SOME/IP and DDS) on benches and in test vehicles.
- 04Verification & ValidationAutomated test infrastructure with traceability suitable for safety and cybersecurity evidence.
05Regulatory context
Standards and regulation that shape the work.
Listed as the regulatory context engineering work in this sector must respect. They are not certifications held.
- ISO 26262
- Functional safety for road vehicles.
- ISO/SAE 21434
- Cybersecurity engineering for road vehicles.
- UNECE R155 / R156
- Cybersecurity management and software update management systems, required for type approval.
- Automotive SPICE
- Process assessment model widely used by vehicle manufacturers to evaluate suppliers.
- Cyber Resilience Act (EU) 2024/2847
- Excludes vehicle products covered by type approval, but can apply to aftermarket devices, chargers and tooling.
Contact
Engineering challenges in automotive?
Describe the system and its constraints. We will tell you honestly whether and how we can help.
Start a conversation