Bosch Embedded Interview Guide
- Roles
- Embedded Software Engineer, Embedded Developer, AUTOSAR Engineer
- Hiring hubs
- Bengaluru, Coimbatore, Stuttgart, Budapest, Ho Chi Minh City
- Focus
- CAN, AUTOSAR, Embedded C, RTOS, automotive testing
Processes differ by team, level and country, so treat this as a typical picture, not a guarantee. Last updated: November 2026.
At a glance
| Typical process | Hiring manager or phone screen → 1–2 technical rounds → senior manager → HR (often completed within a month) |
| Main focus | CAN in depth, AUTOSAR architecture, Embedded C and C++, RTOS, MISRA, testing (HIL) |
| Coding style | C and data-structure questions (linked lists, pointers) rather than long algorithm problems |
| Reported difficulty | Embedded Software Engineer candidates on Glassdoor rate it about 3.3 out of 5, with about three-quarters reporting a positive experience |
How the process usually runs
Candidates in India describe a technical phone round of about an hour focused on CAN and Embedded C, followed by a face-to-face technical round on their current work, then a senior manager discussion and HR. Other reports describe three rounds: a high-level hiring-manager conversation, a technical interview with the team, and HR. Interviewers tend to go deep into each project on your CV.
Topics that come up most
- CAN: frame fields, error management, voltage levels → Communication Protocols
- AUTOSAR: the layered architecture (application, RTE, BSW, MCAL) → Embedded C
- Embedded C and C++: pointers, arrays, OOP basics, memory types (RAM, flash, EEPROM) → C Programming, C++ for Embedded
- RTOS and synchronisation: mutexes, semaphores → RTOS
- Drivers: I2C drivers, integrating a sensor → Driver coding
- Quality and testing: MISRA C, hardware-in-the-loop testing → Debugging & Testing
Questions candidates reported (paraphrased)
- Explain each field of a CAN frame and how CAN handles errors.
- What voltage levels does CAN use?
- Describe the AUTOSAR layered architecture.
- How would you integrate a temperature sensor and build the RTOS application around it?
- Linked-list programs in C; mutex vs semaphore.
- Polymorphism and OOP examples in C++.
- Why do you want to work at Bosch?
Practice questions
These are the questions Bosch candidates most often report, or close variants of them. Each links to a full answer or a coding problem with tests on this site.
- How does a CAN frame look?
- How does CAN arbitration work?
- How does CAN handle errors?
- Why does a CAN bus need 120 Ω termination?
- What is AUTOSAR and what are its main layers?
- What is MISRA C?
- What is the difference between a mutex and a binary semaphore?
- Write I2C register read and write functions.
- How do virtual functions work? What is a vtable?
- How do you reverse a singly linked list?
- UART Packet Parser State Machine (coding)
- CRC-16/CCITT-FALSE (coding)
- Moving Average Filter (coding)
How to prepare
- Know CAN thoroughly: arbitration, bit stuffing, error counters, bus-off, CAN FD.
- Learn the AUTOSAR layers and what lives in each, even if you have not used AUTOSAR yet.
- Revise MISRA C rules you have applied, and be ready to discuss testing (unit, HIL).
- Practise UART Packet Parser and CRC-16 as proxies for protocol code.
Share your experience on the forum and help the next candidate.
Sources: summarised from candidates' public interview reports on Glassdoor, AmbitionBox [1] [2] [3] [4] [5] [6]