J'ai postulé via un recruteur. J'ai passé un entretien chez Google
Entretien
Onsite interviews, each of 45mins. Each interviewer checks a different aspect of what they think important to the job role. Like coding, concepts, and system designs.
The negative rating is really about the interview has nothing to do with firmware. OK, maybe one or two questions somewhat related to firmware. I get the idea that once someone is hired, he/she may move around among different groups, so it is important to make interviews generic enough. Google is overall a software company, and there's no doubt that it's pioneering the software industry. But, it's a waste of effort for me. If I've known about it, I wouldn't apply at all. The job description itself is somewhat deceptive.
J'ai postulé via un recruteur. J'ai passé un entretien chez Google (Kraków) en juin 2024
Entretien
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
Questions d'entretien [1]
Question 1
1st stage - data structures and algorithms
receive stream, sort it and send out with necessary frequency
J'ai postulé en ligne. J'ai passé un entretien chez Google (Santa Clara, CA)
Entretien
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
J'ai postulé en ligne. J'ai passé un entretien chez Google (San Diego, CA)
Entretien
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.
Questions d'entretien [1]
Question 1
How does multi threading work in an embedded system?