Helmond, North Brabant, Netherlands
With over 9 years of professional experience in the automotive industry and high tech embedded system & IOT technology. Currently working on training assignments Advance embedded Linux development and IoT system programming on Coursera plus. My core competencies include expertise in safety critical and ASPICE driven environment. I have worked across the full V-cycle from requirements, design, unit & integration test phase to release with strong exposure to SWE.1 to SWE.5 and SYS.2 . Technically my strength is in C/C++ based embedded development, Object oriented prgramming, SOLID principles, Software integration and working efficiently with software development life cycle PROCESS. I’m not someone who just writes code — I help teams deliver predictable, compliant software. I worked under AGILE, SCRUM, ASPICE AND Hybrid methods with a strong focus on AUTOSAR standards, functional safety, and cybersecurity. At ICT Group, I specialize in developing CAN communication, diagnostics, and memory stacks, for microcontrollers such as Infineon, TTTech 2300, ST Chorus and TI CC2642. My commitment to continuous learning and collaboration drives my efforts in requirement engineering using DOORS and software design amd state machine through UML diagram. Experienced in C/C++ programming and testing of the embedded software which are running on TI CC2642 and Raspberry Pi.
Project Description: The MOTAR platform provides a toolbox for MATLAB/Simulink, plus an AUTOSAR based software stack. This allows you to flash your model directly to your target without manual coding. The entire software stack (from application to low-level drivers) is configured and generated from within MATLAB/Simulink. My work focused on requirements, software design, unit/integration testing, and test architecture, with safety and ASPICE compliance as core guardrails. Clients: Spierings Mobile Cranes, In Motion. Responsibilities: ✓ Wrote and refined software requirements for IOstack(Adc, Pwm, Dio drivers), SystemStack, TTC2000 (CDD component) and CAN communication(Com, PduR, CanIf and CAN) based on AUTOSAR based SRS(Software Requirements Specification), including clear verification criteria that later drove the testing phase. ✓ Created UML diagrams for NvM, MemIf, Fee and CAN Stack, included both structural diagrams and behavioral diagrams & implemented the Adc, Pwm, Com, CanIf, Can, NvM and complex device driver TTC200 using C language. ✓ Built unit tests for IOstack, SystemStack, MemoryStack, and CAN using TESSY, targeting functional coverage and robustness. Created approx. 2000 test cases in achieving 100% requirement coverage. ✓ Executed integration tests for MemoryStack, validating cross-module behavior under realistic scenarios (initialization sequences and error paths). PROJECT: Automotive Demonstrator blue car, Position: Senior Embedded software engineer • Built a real‑time TinyML gesture‑detection system on nRF52833, using Zephyr RTOS, TensorFlow Lite Micro, and a multi‑threaded architecture to achieve <20 ms hardware response for smart vehicle interactions inside ICT’s Software defined vehicle (SDV) demo platform. • Evaluated and integrated MCUs and Yocto‑based components by configuring meta‑layers, optimizing memory, and applying a structured MCU decision matrix to select the best hardware for AI‑at‑the‑edge automotive use cases.
Description: A next-generation digital display platform supporting flexible screens, LCD TFT and high-resolution rendering for modern EV and autonomous vehicle cockpits. The project focuses on software design & validation of Display control, Backlight & dimming, and Panel control components ensuring safety-critical performance(ASIL-B) for OEMs such as SEAT. Responsibilities: ✓ Designed & Developed the Display Control, Backlight & Dimming, and Panel Control software components using Enterprise Architect, ensuring 100% compliance with ASIL-B safety standards. ✓ Designed end-to-end Display Control, Panel Control, and Backlight & Dimming components in UML (static + dynamic diagrams), integrating both I2C and SPI communication layers seamlessly. ✓ Verified software reliability through SWE.4 unit testing using TESSY. Validated correct behavior using sequence-flow checks, boundary analysis, pointer safety tests, and external function behavior tests. ✓ Collaborated with CarUX/Innolux hardware teams to align software signaling with the panel's Smart Display+ architecture and its embedded mini controllers(Display processors & MicroChip maxTouch controller). ✓ Reduced the development time of SWE.3 and SWE.4 by 15% by working on multiple components within a short period. ✓ Participated in peer reviews of software components, contributing to quality assurance and continuous improvement of the display system. Client: SEAT
Description: DFVM(Dynamic Function Vehicle Manager) is an automotive software component designed to manage and enhance vehicle software functionality, focusing on managing different variants of functions within the car's software architecture. Clients: Volkswagen Responsibilities: ✓ Implemented MQTTManager with robust reconnect, retry, TTL, and publish/subscribe mechanisms; connected it with DFVM logic to process cloud messages and update ViWi server based resources accordingly, achieved real-time remote feature updates (e.g., Drive Mode, Lane Assist,) enhancing connected-vehicle functionality and reliability using Object oriented and SOLID principles. ✓ Multiple middleware events (MQTT, IPC, VI‑Connector) arrive concurrently. Used AsyncThreadHandler to queue heavy tasks; protected shared state with mutex/lock_guard; emitted notifications through observer callbacks, prevent race conditions. ✓ Created a composition root that wires all services and ensures safe IPC lifetime management. In DFVMMain, initialized Victor IPC (MessageRouting::init()), constructed/connected Persistency, VI-Connector, ActiveBackendConnectionHandler, MQTTManager, VCTLManager, Hashes/Settings, and installed signal handlers; ensured DFVManager shutdown happened before IPC deinit. ✓ Asynchronous middleware are difficult to simulate in unit test, implemented interface‑driven architecture and adapter layers for all middleware dependencies, enabling full mocking and deterministic unit testing using GoogleTest/GoogleMock, resulting in higher test coverage and more reliable CI.
Description: ECU configuration via Diagnosis – ECU is Online connectivity unit(OCU) ECU configuration via diagnostics is the process of coding and parameterizing connectivity ECUs (like OCU and ConMod) using UDS services, tested first on an OCU box (via PHY box) and then validated in a full‑vehicle system desk environment. Online connectivity unit(OCU): VW’s telematics box that provides cellular connectivity (GSM/LTE), eCall, and remote services; it bridges the Vehicle to VW backends and enables OTA/service data flows. Responsibilities: • Configured the ARXML master file(contains diagnostic component data) in SystemDesk, add feature‑flag admin data to control variant‑specific elements (ports, RTE events, runnables), and import the updated ARXML into EB Tresos to generate configuration files and ensure that only UNECE variant‑specific feature configurations are produced. • Worked in Diagnostic software component development (creation of P/R port interfaces, Plausibility check, DCM wrapper operations & functions ) using C programming language. • Responsible for E2E and Non-E2E Diagnostic component requirement to implement for configuration DIDs. • Implemented read and write operation functions of wrapper. Performed plausibility checks and adaptation update through the wrapper function, and executed unit tests to verify all updated changes, improving diagnostic component reliability by 15%. • Tested Configuration DIDs using PhyBox/Vector CANoe(diagnostic tool). • Successfully validated the SFD-protected workflows and E2E protection end-to-end, reducing risk of unauthorized access and message tampering. Client: Volkswagen
If driver is nearby the Vehicle with The key in his/her pocket, Vehicle doors must be unlocked automatically. ● Validated the bootloader process on TI CC2642 for secure firmware flashing and deterministic startup. ● Validated Over the air update in BLE and UWB and SPC58 with CAN-side controls for door unlock and engine start, optimizing for latency and reliability and arranged the debug session for communication issues between BLE/UWB and OTA master(SPC58). ● Built CAPL-driven test flows to execute diagnostic actions, logics and update sequences for secure flashing. ● Supported Bootloader team in Australia for validation of Bootloader flashing. I received the appreciation email from Australia bootloader team for the support. Also, our team received the recognition among global teams. ● Managed requirements in IBM DOORS and collaborated on software design update using IBM Rhapsody, maintaining traceability into test artifacts and deliveries. ● Worked on development testing of Boot manager execution. ● Implemented diagnostic components for Data Identifiers (DIDs)—covering read/write, range checks, and routine controls using Da vinci developer and Da vinci configurator. ✓ Conducted requirement analysis using IBM DOORS, performed MISRA compliance checks, and contributed to software design using IBM Rhapsody. ✓ Used Bluetooth Low Energy and UWB wireless technologies, Integrated with CAN Bus to control door unlocking and engine start. Client: Ford Bootloader development activities Autosar stack integration