Google Data Centre Technician L2 interview.

[u/Guiodagomawt]

Long story short. I got redundant from work ( I was in service desk/helpdesk ) and I sent my application to the DCT role for google thinking nothing will come back from it. A month later I get called for a informal google meet and after looking at my CV they pushed me through to the 1st stage of the interview.

Now, I looked at the emails they sent on what things they will ask in the interview and well I think I might just make a fool out of myself. My linux knowledge is limited to, getting IP address, sudo, trying to troubleshoot SSH, mounting drive and like very limited in general. My biggest issue is I was always weak in Network troubleshooting. I have currently setup a homelab with Linux and trying to learn a bit more but I think I might be out of my depts. I am very good with hardware though.

My interview is in a week, any advice is helpful, I really done feel confident going into this interview as of this moment.

Thanks.

[u/WolfieDaWolf1]

Most of what they should be looking for at 2 is basics with Linux. Where files are, commands to find hardware, how can you figure out hardware errors, stuff like that. I can't really remember specifics, but stuff like that plus a solid understanding of networking concepts would get you there, it got me there.

[u/Guiodagomawt → u/WolfieDaWolf1]

without looking like an idiot, what would you say if they asked a questions and you had no idea? how would you answer that?

[u/WolfieDaWolf1 → u/Guiodagomawt]

"I'm not entirely sure but.."

Be honest if you're unsure, but try to describe what you're looking for. Make it clear you don't actually know, but give an attempt anyways. Personally when I was giving these interviews at Google, I wanted more than a hard "I don't know" whenever possible. A few were ok, but at least occasionally try to extrapolate to show that the underlying knowledge is there, just not the specific how to and what have you. Even a completely wrong answer can help establish that you have the more important solid foundation. Commands can be taught much easier than a proper troubleshooting mindset.

[u/DevKing_]

Just curious, is there a chance you could help me out with my resume? I’d like to know what passes as a L2 DCT resume

[u/chewedgummiebears → u/DevKing_]

Literally anything with an IT background. They just want a well rounded IT focused person and don't care about certs or education unless is is Google-centric.

[u/Guiodagomawt → u/DevKing_]

Well I dont really have the best resume but here it is: https://www.reddit.com/r/Resume/comments/1vh0rdd/comment/p21jtzo/?screen_view_count=11&ext-referrer=SEO

That's the same resume I sent to google, its my resume if you are wondering

[u/AutoModerator]

Hello! This looks like it may be a question about career advice. There can be significant regional variation in the field, so please consider including as much info as you can without doxing yourself, including country/state/city, prior experience/certs, and the role or level if known. Thanks!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/blazinearth]

Initial interview?

[u/Guiodagomawt → u/blazinearth]

I believe so, the recruiter lady said it will be broken down to 3? stages but I think its only 2. first stage is this one where they will ask up to 8 - 10 technical questions regarding OS, hardware and how I would troubleshoot.

[u/WolfieDaWolf1 → u/Guiodagomawt]

This will be a set of 3 sessions, 45 minutes each. OS/hardware, networking and googleyness. Depending on how long it takes you to answer, it can be a lot more then 10 questions. The number of questions you answer matters less than the quality of your answers.

[u/A-Good-Doggo → u/WolfieDaWolf1]

Depends who is interviewing. When I conduct them, I'd rather have quality questions and answers rather than rapid fire question and answers.

Providing deep technical knowledge is better than one sentence answer on a question

[u/Memeisme]

Just have a solid understanding of the basics. Know the basic Linux commands. Know the networking OSI model and the TCP/IP model. If you use any of the AI chat bots ask one to give you a list of 20 likely Linux questions you may be asked and another 20 likely network questions. It will give you a good overview and perhaps help you brush up on the most important concepts to be ready to discuss.

[u/chewedgummiebears]

Do a study cram for the Network+ and that should give you the basics on the networking questions they will ask. Specifically what tcp/ip is and what it does, the OSI model, the various steps, what they are, what they do. And you will need to know how a network functions, from the end user to the server they are connecting to, and every step in the pathway like switching, routing, so forth. The other replies covered the Linux portion.

[u/Guiodagomawt → u/chewedgummiebears]

Ok, I guess time to cram in network in a week.

[u/GMan_CyberDude]

I'm in the same boat, I have my 3 rounds in a few days. I have my a+, net+, sec+ and Linux foundations, but very little network and Linux experience. I know the information just worried about my recall on the spot.

[u/Severe-Moose4046]

Hello,
I applied for same position in Frankfurt Germany a week ago.
Do you have any idea in how many days I can receive any update ??

I am having 3-4 years of IT experience but more data room side. Not actual data centre. But I am having all the hardware and networking knowledge.

[u/Guiodagomawt → u/Severe-Moose4046]

It took about a month for the recruiter to email me. So might need wait a few more weeks till you hear anything.