Job Summary

Role Purpose
Provide technical leadership for embedded firmware/platform development for Robotics and act as the technical interface to Kärcher architects and product engineering teams.
Key Responsibilities
• Architect and lead embedded firmware development (C/C++, Embedded Linux)
• Review requirements, define technical solutions, and guide implementation
• Lead design/code reviews, debugging, and performance optimization
• Mentor developers and ensure adherence to coding and quality standards
• Support integration, system testing, and release stabilization
• Collaborate closely with hardware, testing, and DevOps teams
Required Skills & Experience
• 12+ years in embedded software development
• Strong hands on experience in Embedded C / C++
• Microcontrollers, drivers, peripherals (UART, SPI, I2C, CAN)
• Debugging tools (JTAG, logic analyzers, oscilloscopes)
• Experience with Git/SVN, CI pipelines
Nice to Have
• Embedded Linux, TouchGFX / HMI frameworks
• IoT protocols (BLE, Wi Fi)
• Exposure to Kärcher platforms or similar appliance products

Key Responsibilities

1. To architect| design and develop (through Team) solution for product/project & sustenance delivery
2. To bridge the gap between client needs and business goals by gathering requirements, crafting innovative solutions with deep domain/technology expertise, and driving successful implementations that propel strategic initiatives.
3. To ensure knowledge up-gradation and work with new technologies so that the solution is current and meets quality standards and the client requirements
4. To review architecture and design deliverables and ensure solutions adhere to industry best practices ,architectural standards simultaneously establish and enforce governance /compliance measures.
5. To train and develop team so as to ensure that there is an adequate supply of trained manpower in the said technology and delivery risks are mitigated
6. To submit Whitepapers, participate in industry forums and file Patents

Skill Requirements

Role Summary
Responsible for RTOS enablement and firmware platform for RCW7 navigation PoC on MCU hardware: bring‑up, scheduler stability, task architecture, interrupts, timing, and integration of drivers + navigation application. Scope includes RTOS porting/validation, firmware framework, and system stability.

Key Responsibilities
•Port / configure RTOS (e.g., FreeRTOS), establish startup, memory layout, interrupt priorities, and deterministic scheduling.
•Define task architecture (Nav/Sensors/Safety/Diagnostics), IPC primitives (queues, semaphores, mutexes, timers).Integrate and stabilize BSP/HAL baseline (clocks, SysTick/timers, watchdog, debug hooks).
•Collaborate with driver engineers to ensure RTOS-safe driver APIs, ISR→task deferral, concurrency protection. (Role alignment)
•Enable lightweight diagnostics/logging hooks suitable for PoC validation.
•Support debugging on real hardware using JTAG/SWD, logic/protocol analyzers; resolve hard faults, timing bugs, starvation/deadlocks.
•Contribute to coding guideline compliance, reviews, and PoC documentation/handover as per process.
Must‑Have Skills
•Strong Embedded C/C++ on MCUs; bitwise operations, memory/performance awareness.
•Strong RTOS concepts: tasks, scheduling, interrupts, semaphores/mutex/queues/timers, critical sections.
•MCU architecture familiarity: ARM Cortex‑M class; datasheet interpretation.
•Debug proficiency: JTAG/SWD, J‑Link/OpenOCD style workflows, trace/log based debugging.
•BSP bring‑up experience: clocks, startup, linker scripts, ISR mapping.
Nice‑to‑Have
•Experience with CMSIS‑RTOS / Zephyr / ThreadX / QNX or multi‑RTOS migration.
•Static analysis / MISRA exposure, CI hooks.
Experience Level (suggested)
•12 years embedded firmware with RTOS bring‑up on Cortex‑M class MCUs (recommendation).

Other Requirements