Me postulé a través de un reclutador. El proceso tomó 2 semanas. Acudí a una entrevista en Google (Tel Aviv)
Entrevista
Recruiter contact me via LinkedIn ,
He was super nice .
The interviewer was not professional.
The interview was about system administrator and scripting . He foucesd on one subject . So That was bad because if you don't have experience in this subject you will fail.
Overall:
the recruiter was great , he really cared about me succeeding in the interview.
Done his job right.
The interviewer was not professional and was not responsive did not give hints.
First phase questions specific about kernel :
He expected from me to know about kernel in depth which is not possible if you are not working in that field .
Btw i have interview with the team leader of this role before this interview to ask him questions about the role he did not mention anything about kernel ..
So ..?
Second phase scripting :
he expected that i remember linux commands with their flags which is not possible to do without using man guides. Or at least terminal.
The interview went on using google docs which maybe works for coding but not for linux that's for sure.
Virtual interview, standard google meet. The interviewer gave there back ground explained their career journey, what to look for from Google. Then I was asked my background information. Next preceded the interview
Me postulé en línea. El proceso tomó 4 meses. Acudí a una entrevista en Google (Dublín, Dublín) en may 2023
Entrevista
Interview was online with 6 rounds of interview. 1st was with engineering manager and was a filtering round, heavily focused on Linux and system debugging with performance issues. Based on multiple scenario based questions. Followed by a series of interviews focusing on Linux Administration, Network Administration, System Internals (IPC), Programming Round, Googlyness Round. Hiring Team review stage and Offer stage. It took around 3 to 4 months for the entire process and the HR was fantastic and prepared well. The interviewers were top notch and went really deep into the areas. They wanted the candidates to succeed.
Preguntas de entrevista [1]
Pregunta 1
System performance debugging HTTP Proxy - how does it work strace, truss- System calls and how commands interact with kernel IPC (how threading and process interacts with Kernel in linux) Where does file-names get stored File-name descriptors CPU steal, nice, affinity with examples Real-time performance issue that you solved recently and what tools were used and motivation behind using those Disk i/o and its related tools and issues Good practices for Linux hardening (many questions related to this) Networking and firewalls, Subnetting TTL and how does it affect TCP vs UDP (Why UDP is preferred for video streaming and disadvantage), Why DNS relies on UDP not TCP TTL hop counter load in top with extensive detail and its relation to the CPU core count How does TCP connection establish How does TCP connection finish (browser close) Programming round with Language of choice - Interacting with API, building parser to play on the API output, how you change your code with dynamic requirements Lots of Behavioral questions during the Googlyness round, found it to be hard to be honest. Interviewer was keen on why I made a decision and motivation behind it and if I did a risk assessment before it.
Me postulé en línea. Acudí a una entrevista en Google (Dublín, Dublín) en mar 2023
Entrevista
The Interview process is great if you know what are you doing. After 5 interviews I received a letter that Google suspended all the new employments. About 3 months later, I contacted them again because they opened the position for hire and I was told to apply again. I am happy that I met very nice people and skilled engineers but is a waste of time when it comes to the hiring process.
Preguntas de entrevista [1]
Pregunta 1
Linux, starting from when you switch on the computer, down to the system calls
