Firmware Engineer applicants have rated the interview process at Google with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 29% positive. To compare, the company-average is 61.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Firmware Engineer roles take an average of 14 days to get hired, when considering 8 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 38 days.
Common stages of the interview process at Google as a Firmware Engineer according to 8 Glassdoor interviews include:
Phone interview: 29%
Skills test: 14%
Presentation: 14%
One on one interview: 14%
Drug test: 14%
Other: 14%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at Google (Mountain View, CA) in Jan 2016
Interview
Passed one phone screen with the task leader with a single C question which is wisely known among embedded and firmware engineers. When getting onsite, coding questions would not be able to tell whether candidate does firmware or not. Some features in C only apply to firmware/embedded engineers. Google and 90% companies do not know how to interview firmware engineer.
Interview questions [1]
Question 1
One C question related to constant/volatile attribute to value location or pointer.
I applied through a recruiter. I interviewed at Google (Kraków) in Jun 2024
Interview
after short communication I've selected timeslots for the interview
1) interwiev with the HR about role and skills;
2) technical inerview where you should solve the task (using IDE is prohibited)
company didn't provide you a feedback about you intervie and mistakes, but after all steges I've received some emails from company asking fill the feedback form
Interview questions [1]
Question 1
1st stage - data structures and algorithms
receive stream, sort it and send out with necessary frequency
I applied online. I interviewed at Google (Santa Clara, CA)
Interview
Phone interview followed by onsite with five engineers. Very firmware knowledge based questions and all coding. Need to know basics well and should be able to tackle system design questions
I applied online. I interviewed at Google (San Diego, CA)
Interview
Was long and drawn out and then never gave any feedback. Each interviewer was late. Learning about Google was interesting though. If I were to try again, I would have to be really convinced it would be worth it.
Interview questions [1]
Question 1
How does multi threading work in an embedded system?