Making vehicle control software more testable and dependable.
Software-level verification, test design, analysis, automation, and mentoring across VCU/ECU components and HIL environments.
What this work was about
My automotive work connects requirements, test design, execution, evidence, and root-cause investigation. At Volvo Cars, I have worked with VCU component-level verification. At Zeekr, my HIL assignment covered steering, brakes, and propulsion-related domains.
The problem to solve
Modern vehicle software has many interacting conditions, services, and signals. The difficult part is not simply running a test—it is building reproducible test methods, maintaining traceability, recognizing failures early, and getting clear evidence to engineering teams.
How I approached it
- Created and maintained test cases using SystemWeaver / CarWeaver and implemented automated executions in vTESTstudio and CANoe.
- Used simulated conditions and mocked service interactions to verify component behavior across specific scenarios.
- Worked with HIL rigs and test benches; assessed nightly runs, analyzed signals, traces, and logs, and reported issues.
- Created documentation, visual onboarding guides, and test utilities to support other engineers and speed up adoption.
- Supported test coordination and mentoring for fellow testers across different vehicle programs.
The value and the result
What it taught me
High-quality verification is a connected practice: traceable intent, controlled conditions, repeatable automation, evidence-based analysis, and useful communication.
Let's build something
that actually works.
Verification, automation, software products, or simply a difficult technical problem.