Me postulé a través de un reclutador. El proceso tomó 2 semanas. Acudí a una entrevista en Google en mar 2018
Entrevista
Phone interview. The interview was pretty rude and not interested in learning much of anything regarding my background, interests, or unique professional experiences. They're more focused on technically grilling candidates with random but usual EE questions.
Asked about trace impedance control in a PCB fab. What tolerance do I design for on impedance controlled traces and what would I do if the fab house couldn't meet the specified tolerance.
Acudí a una entrevista en Google (Mountain View, CA)
Entrevista
I was invited to have an interview with two engineers for the Google Watch team, had 2 rounds in one day, 30 min apart. Each took 60 min to complete. Didn't tell me the result for 2 months and no feedbacks were provided.
Me postulé a través de una facultad o universidad. Acudí a una entrevista en Google (Kānpur, Uttar Pradesh) en jul 2025
Entrevista
2 technical rounds after an OA. Tested digital design fundamentals and focused also on my past projects. They really emphasize on basics. They ask for a preferred programming language beforehand (I chose Verilog) and then they would ask you to code up some circuit in verilog in a google doc.
Preguntas de entrevista [1]
Pregunta 1
Difference between FPGA and ASIC development cycles?
II was shortlisted for the position based on my resume, which aligned well with the role requirements. Following that, I successfully cleared two rounds of interviews that evaluated my technical and communication skills.
Preguntas de entrevista [1]
Pregunta 1
Write verilog code for synchronous and asynchronous counter