How to get job in Google? Google Jobs:

How do people get jobs at Google?

There’s primarily two ways people get jobs at somewhere like Google. These are the same ways most people get jobs at places like Amazon, Facebook, Apple etc.

For this answer, I’m going to assume you’re looking for a technical role like a software engineer.

1. Referrals. By far, referrals are the surest way to at least get an interview. In fact, referrals are also statistically one of the surest way to get an offer. In many cases, referrals can give you 10x the chance of actually getting an offer when you consider how many people a company like Google will talk to before making a hire. Unfortunately, it’s not super efficient but it’s also the nature of recruiting top tier talent; most won’t work out.
2. Recruiters. Google and every other big tech company has thousands of recruiters actively searching for the best talent. I’d say 90% or more of the candidates I’ve worked with (including this year) are all passive talent that I reached out to and began a conversation. Good talent doesn’t just apply because they don’t need to. I’m not saying that people who do apply are bad. What I’m saying is they’re a lot less likely to do so because of their current situation. There are a lot of bad recruiters but there are also a bunch of good ones. People can become desensitized to recruiters, especially if they seem to be a machine.

So let’s say you want to put yourself in the best situation to get referred? What can you do?

1. Network with current googlers.
2. Ask people you know if they can make an intro to someone who works at Google and form a relationship (professionally if possible).
3. Attend Google events like happy hours, dinners, conferences etc.
4. Get some experience and soon enough, you’ll likely know a few people at Google after a few years. Whether that be directly or through a friend of friend.

Want to get noticed by a recruiter? Here’s how:

1. Make yourself available. How? Have an up to date profile on places like Linkedin, Github and a personal website.
2. Respond to recruiters, even if you aren’t interested. Here’s a secret: recruiters remember you, even when they switch companies. I sure do. It’s a relationship that’s being built and while I’m trying to get you to interview, I’m perfectly okay with sending you a message in 6–12 months if you tell me to. If you happen to be interested sooner, now you have the contact info of the recruiters at companies you might want to talk to.
3. Contribute to the open source community. Speaking of conferences, both Google and Facebook attend a bunch of these. Here are a couple of links depending on what’s most relevant to you on the Facebook side: Android, iOS, Web, Backend and Hardware. Google’s can be found here. If you’re working on any open source projects, add them to your Github, Linkedin, portfolio or any other online sites you might have and mention them on your resume. Great for those conversations at campus recruiting or interviews too.
4. Build things. There’s nothing better to showcase your skills, passions, areas of interest or even potential, than by experimenting with projects. Basically, hack together whatever you’re interested in. You could build apps, websites, utilize data sets, apply ML or AI to something, build on top of existing platforms and more. The ideas are endless. Who knows, maybe you’ll turn one into a side hustle or a full blown startup. If you want to take this a level up, work with others on this and build something bigger, with more depth/breadth and showcase your team skills. These people could be friends or strangers and the best part, you’re building your network on a professional level at the same time.
5. Cold email a recruiter and not just any recruiter. You can reach out directly to a recruiter that focuses on your area of expertise - with an emphasis on area of expertise. Most recruiters will identify what areas of engineering or non-technical roles they hire for. Be strategic in who you reach out to and be personal. We love to meet people who might be actively looking and within our specific scope of recruiting. It literally makes our job that much easier. If you know someone who got recruited to google but don’t know them well enough, you can even ask them for an introduction to their facebook recruiter. Maybe they’ll be willing to help.

Finally, don’t wait to start preparing for your interview. Every day is a new day to improve your skills, pick up new ones and continue getting better at whatever you do, wherever you do it. When that day comes you’ll want to be as prepared as possible. Here are some tips on making it through the interview process at Facebook but also apply to Google.

In terms of technical areas to continue improving, I’d focus on systems, design/architecture and of course code.

1. Systems - More specifically, linux troubleshooting and debugging. Understanding things like memory, io, cpu, shell etc. would be pretty helpful. Knowing how to actually write a unix shell would also be a good idea. What tools might you use to debug something? On another note, this interview will likely push your boundaries of what you know (and how to implement it).
2. Design/Architecture - this interview is all about taking an ambiguous question of how you might build a system and letting you guide the way. Your interviewer will add in constraints when necessary and the idea is to get a simple, workable solution on the board. Things like load and monitoring are things you might consider. What you consider is just as important as to what you don’t. So ask clarifying questions and gather requirements when appropriate (which is much more often than you might think). A great resource to review here is Grokking the System Design Interview and focus on the areas of load balancing, caching, indexes and sharding. You can even practice designing a system like Instagram.  It’s important to note your interviewer isn’t expecting you to be incredibly fluent at system design but understanding this or having a leg up on other candidates will certainly set you apart than those who are just strong coders.
3. Coding - algorithms, data structures and clean production ready code is the end goal. Binary trees and link lists could be topics to review and you’re free to use whatever language you like. Google tends to be very algorithm heavy so I’d probably split my time 70/30 with that being algorithm/data structures. Remember, it’s even more critical to showcase your thought process and how you come to a solution and why. Take hints from your interviewer if they give them to you and run with it. In most cases it’s not a trick or anyone trying to stump you. Lastly, it’s okay to not know something. These interviews are meant to push your knowledge past your comfort zones and you should feel comfortable exploring the unknown.

Is it better to spend all my time on data structures and algorithms rather than side projects, in order to crack the Google and Facebook interviews

In Asian countries there tends to be this huge emphasis on “prestige of your university”. This appears to be a cultural phenomenon.

You can in fact get a good education at nearly any university, as long as it has equipment and a decent library, and you are motivated to learn, rather than just doing the minimum necessary to pass the classes to get the degree.

Just because you go to Harvard Law doesn’t mean that you’re a great lawyer. Just because you go to Johns Hopkins medical doesn’t mean you're​ not going to be a doctor with a high mortality rate.

This is not what’s going to get you the interview in the first place.

The thing that gets you the interview in the first place is being known. There are different paths to being known, but the most common ones are:

• Participate in a popular Open Source project; one of the BSDs or a Linux distribution, or just the Linux kernel are good options, because these projects are used or known at the companies you’ve indicated an interest in.
• While it’s great to have some things on GitHub, that’s not really a qualification for anything, if the projects aren’t popular; a popular project has multiple participants, and gets actively committed to on a rather regular basis; otherwise it’s just you publishing some sample code that maybe no one ever finds.
• Get published; one paper in one journal is not published; 5 papers published with coauthors known in the field is published. Papers presented at actual conferences people have heard of, and which are printed in the conference proceedings is published — unless it’s a bogus conference, of they type that’s put on by predatory publishers to enable people to pay to pad their resume.
• Get some work experience; this not only makes you reliably pinned as someone who can actually do work — it enables you to build your personal network. Your personal network will be how you get most of your jobs, throughout your career. You start this by being in contact with your fellow students, and your professors, so that you feel comfortable asking them “Say do you know anyone who works at Google/Apple/Facebook/Twitter that you can recommend me to?”.
• Do something singularly important to the field.
• Write a Book on a topic in the field.

So yes, learn data structures and algorithms.You won’t pass the technical interview otherwise.

Also do projects. Relevant projects, not just self-publication of your code on GitHub. That probably means working on someone else’s project. Get over it. Not everyone can be Linus Torvalds.

And build your personal network.

Getting known, and knowing people, is how you get the interview in the first place.

Answers are given by quora.com experts.