How 22 Years of Software Evolution Taught One Industry Veteran That Safety Standards Save Lives—And Why That Human Story Matters More Than Ever
In an industry obsessed with buzzwords like “software-defined vehicles” and “autonomous driving,” it’s refreshing to hear someone cut through the hype and focus on what truly matters: keeping people safe. Alexander Much, who spent 22 years at Elektrobit navigating everything from 8-bit microcontrollers to multi-million-line codebases, brings a perspective that’s both deeply technical and profoundly human.
“When managers start to talk about open source, I get the creeps,” Much candidly admits in our “Automotive Storytelling” episode. “They should talk about business, business cases and things.” This no-nonsense approach defines his entire philosophy—one that prioritizes substance over buzzwords and human safety over technological showmanship.
With expertise spanning ISO 26262 functional safety, Automotive SPICE, cybersecurity engineering, and open source strategy, Much has witnessed the complete transformation of automotive software. More importantly, he’s helped shape the safety standards that prevent injuries and save lives. In our conversation, he reveals why functional safety resonates so powerfully with people, challenges the software-defined vehicle narrative, and shares what it really takes to build safe, reliable automotive systems in an increasingly complex world.
The Accidental Beginning: How Linux and Mathematics Led to Automotive Software
Much’s journey into automotive software wasn’t driven by childhood dreams of working on cars—it was almost accidental, shaped by curiosity, opportunity, and yes, student loans.
“I studied mathematics in Erlangen,” Much explains. “I don’t know if you know SUSE Linux… the people who were founders of SUSE were also at the math department there.” Working with SUSE Linux version 0.9 on a Finnish keyboard, Much entered the software world at its most foundational level. When Elektrobit offered him a position, he needed to pay back his father’s loan from studying at Cambridge. “Money is also motivation,” he admits with characteristic honesty.
What he discovered changed everything. “Wherever you went, everyone talked about whatever in cars, no one talked about software. But it was immediately clear that this is going to be the important topic for them.”
The Explosion of Functions
Much witnessed firsthand what he calls “the explosion of functions” in automotive:
- Ubiquitous software deployment: From airbags to every control unit in the vehicle
- Operating systems everywhere: Small OSEK operating systems proliferating across automotive systems
- Industry transformation: The realization that software would become automotive’s defining battleground
“I suddenly realized, this is everywhere,” Much recalls. “It’s in your airbag. The explosion of functions led to unbelievable amounts of control units in cars. And each of those had our stuff or stuff of our competition in it. And that was big.”
One of his first major projects was AUTOSAR—the Automotive Open System Architecture initiative that emerged about 20 years ago.
From Proprietary Chaos to AUTOSAR: The Standardization Imperative
When Much joined the automotive software industry, chaos reigned. Every Tier 1 supplier had proprietary solutions, every OEM spoke a different technical language, and interoperability was a nightmare.
“If you want to communicate between OEM, Tier 1, you need to speak, let’s say, similar language,” Much explains. AUTOSAR emerged as that common language, creating standards that allowed different players in the automotive ecosystem to collaborate effectively.
This early experience with standardization would prove foundational for Much’s later work in functional safety, where common frameworks and shared understanding literally mean the difference between life and death.
The Emergence of ISO 26262
The conversation then turns to what Much calls his true passion: functional safety. The ISO 26262 standard, introduced to ensure that automotive electrical and electronic systems function safely, became the framework that would define much of his career.
“Functional safety… its critical role in preventing injuries… truly resonates with people,” Much emphasizes. Unlike abstract technical concepts, safety has an immediate, visceral impact. Everyone understands what’s at stake.
But implementing functional safety isn’t just about following a checklist. It requires:
- Deep understanding of both hardware and software systems
- Recognition that safety is a process, not just a product feature
- Commitment to documentation, verification, and continuous improvement
- Cultural shift within organizations to prioritize safety over speed
Much’s role at Elektrobit spanned the entire spectrum—from writing code to establishing compliance frameworks, giving him what he calls the ability to “go from code to compliance.” This comprehensive perspective is rare in an industry where specialists often stay siloed in their domains.
The Software-Defined Vehicle Hype: A Reality Check
One of the most refreshing aspects of our conversation is Much’s candid skepticism about current industry buzzwords. When the topic of software-defined vehicles comes up, he doesn’t mince words.
The term has become ubiquitous at automotive conferences and in executive presentations, but Much sees it as “an overhyped buzzword lacking clear business model.” His passion? “Good software.”
What does “good software” mean in automotive context?
According to Much, it means:
- Reliable: Software that works consistently under all conditions
- Safe: Systems designed with functional safety principles from the ground up
- Maintainable: Code that can be understood, updated, and improved over time
- Secure: Protection against cybersecurity threats that could compromise safety
“When the CEO says open source is cool, I say, no, no, no, no, don’t really know what you’re talking about,” Much states bluntly. It’s not that open source doesn’t have value—Much led open source strategy at Elektrobit—but rather that executives need to understand the business case, the licensing implications, and the engineering realities before making declarations.
This cuts to a broader problem: the disconnect between executive enthusiasm for trends and the engineering reality of implementation. Much has seen too many initiatives launched with fanfare only to falter because the fundamentals weren’t in place.
From High-Performance Computing to Open Source: Spanning the Technical Spectrum
Much’s career at Elektrobit took him through an extraordinary range of projects. He played a key role in establishing one of the first automotive High-Performance Computing (HPC) projects—technology that’s now on the road with a major manufacturer.
This progression from simple 8-bit microcontrollers to sophisticated multi-core systems running millions of lines of code illustrates the industry’s transformation. But with increased complexity comes increased risk—which is why Much’s work in functional safety, cybersecurity, and quality management became ever more critical.
The Open Source Challenge
As Director of Quality, Functional Safety, Cybersecurity, and Open Source, Much navigated one of the industry’s most complex challenges: how to safely integrate open source software into safety-critical automotive systems.
Open source offers tremendous benefits—proven code, community support, faster development cycles—but it also requires rigorous management:
- License compliance: Understanding and adhering to various open source licenses
- Security scanning: Identifying vulnerabilities in third-party code
- Safety assessment: Ensuring open source components meet functional safety requirements
- Long-term maintenance: Planning for updates and support over automotive lifecycles
Much’s approach combines technical rigor with business pragmatism. It’s not about whether to use open source, but how to use it responsibly and safely.
The Regulation Question: Industry Self-Governance or Government Intervention?
Toward the end of our conversation, Much raises a critical question facing the automotive industry: who should regulate automotive software safety?
“Where does safety go? More towards regulation,” Much observes. “If we’re careful, it will be an industry effort. If we’re not careful, governments will step in because society doesn’t accept this.”
This tension defines much of the current automotive landscape. The industry has developed sophisticated self-regulatory frameworks like ISO 26262, Automotive SPICE, and MISRA-C guidelines. But as software becomes more complex and vehicle autonomy increases, will self-regulation be enough?
The challenge is scale: “How many thousands of people do you need to regulate this?” Much asks. With software updates becoming continuous and vehicles increasingly connected, traditional regulatory models may not suffice.
Much suggests the answer lies in the industry’s ability to demonstrate responsible self-governance. If automotive companies can show they’re prioritizing safety, maintaining rigorous standards, and learning from failures, they can preserve their autonomy. But any major safety failures could trigger government intervention.
The Human Element: Education, Presence, and Passing Knowledge Forward
Beyond his technical contributions, Much has distinguished himself as an educator. He’s given more training sessions than anyone else at Elektrobit, sharing his knowledge of functional safety, software architecture, and quality management with countless engineers and managers.
This commitment to education reflects a deeper philosophy: that senior executives and experienced professionals have an obligation to share their knowledge, especially as software companies grow and new engineers enter the field.
When asked for his number one storytelling advice, Much’s answer is simple but profound: “Be present.”
“When you enter a room, training room, whatever you nowadays have, an audience that is not capable of listening to something longer than, I don’t know, two minutes. They’re all TikTokers and Instagrammers. They don’t read books anymore,” Much observes. “So when I do workshops and trainings, I try to be as present as possible for them, but also for me. If you lose your focus, they lose their focus immediately. They notice it.”
This advice transcends training sessions. Whether you’re presenting a technical concept, making a business case, or explaining safety requirements, presence matters. Full attention, genuine engagement, and authentic interaction create connection—and connection drives understanding.
“If you get this done, this is magic,” Much says. “And I really like that. When I fail to do that, it’s ugly. But the point is: be present. If you create this presence in the room, you can guide people through complex topics for eight hours straight.”
Conclusion: The Story Behind the Code
Alexander Much’s career offers a masterclass in how to build expertise across the entire spectrum of automotive software development. From his accidental entry into the field through Linux and mathematics, to his leadership roles managing quality, safety, and open source strategy at Elektrobit, he’s witnessed and shaped the industry’s transformation.
But what makes his story truly compelling is his unwavering focus on what matters: keeping people safe. While others chase buzzwords and trends, Much remains grounded in the fundamentals—good software, rigorous processes, and the human responsibility that comes with building safety-critical systems.
As he embarks on his next chapter founding his own company, Much carries forward this philosophy. His message to the industry is clear: substance over hype, safety over speed, and human lives over technological showmanship.
Ready to hear the full conversation? Listen to this episode of Under the Hood: Automotive Storytelling wherever you get your podcasts. Alexander Much shares decades of insights on functional safety, the evolution of automotive software, and why being present is the most important skill in technical communication.
Connect with Alexander Much on LinkedIn to follow his new venture and continue learning from one of the industry’s most experienced voices in functional safety and automotive software development.
Remember: Behind every dashboard and every feature lies a human story—and those are the stories we’re committed to uncovering here on Under the Hood.
This episode is available on Apple Podcasts, Spotify, Deezer, and all major podcast platforms.