I recently interviewed for a Firmware Developer role at Google, and the process consisted of two rounds: one technical and one behavioral. Overall, the experience was well-structured and aligned with expectations for a senior-level firmware position.

Technical Round: The technical interview focused heavily on embedded fundamentals and system-level thinking. The question involved working with a memory-mapped register space, understanding offsets within hardware blocks, and identifying duplicate UIDs across multiple blocks using bit manipulation and pointer arithmetic. The interviewer expected a clear mental model of how register spaces are organized, along with correct handling of pointers, offsets, and bit fields. It tested low-level thinking, attention to detail, and ability to reason about hardware-software interaction rather than just writing code.

Behavioral Round: The behavioral interview was very smooth and conversational. The interviewer asked questions about handling conflicts with teammates, disagreements with managers, working with suppliers/teams under constraints, and situations where I had to go beyond initial commitments. The focus was on real-world experiences, communication style, leadership, and how I approach collaboration and decision-making. I was able to share examples from my automotive domain experience, and the discussion was engaging and easy to follow.

Overall: The process felt fair, practical, and relevant to the role. The technical round emphasized core firmware and embedded concepts, while the behavioral round assessed communication, ownership, and teamwork. The interviewer in the behavioral round was particularly engaged and receptive. I would recommend preparing thoroughly on low-level programming concepts (pointers, memory layout, bit operations, register access) as well as having structured real-world examples for behavioral questions. Overall, a solid interview experience.