Solicité el puesto a través de un captador. El proceso duró 1 semana. Acudí a una entrevista en Google
Entrevista
The interview began with an HR asking about my previous work and the usual stuff.
The second part of the interview surprised me.
The HR showed some contrived code and asked me for the output that will be generated!
I got it wrong. As it turned out, it was an obscure version of bubble sort!
It seemed like a 12th standard organic chemistry named reaction rote memorization check to me.
Expected better from google.
The interview was comprised of 5 smaller technical interviews, one with each person, one each focusing on a different topic. Topics include Graph Navigation, stacks, queues, basic system design and debugging.
Preguntas de entrevista [1]
Pregunta 1
Technical question about finding the quickest way to navigate an achievement tree.
2 Rounds of Interview (3 Coding and 1 Behavioural). Good Interview, really complex questions and interesting one as well. I enjoyed the process and. Although it was a bit stretch of 4 months but worth of experience.
Preguntas de entrevista [1]
Pregunta 1
Questions regarding IPs and connections as well as networking.
Five rounds of interviews, at least three technical. Much depends on whether you want the SRE-SA (System Admimnistrator) title or the SRE-SWE (Software Engineer) title. The latter requires more and deeper coding requirements. The former may go into greater depth with Linux or Window internals.
Preguntas de entrevista [1]
Pregunta 1
Persist a a binary tree to the filesystem -- and read it back again retaining the structure and any "balancing" stored with the nodes.
