0: Hi, I'm Brinleigh and I'm a Business Recruiter at Google.
3: And I'm Okwus, a Technical Recruiter at Google.
5: We're going to take a couple minutes to walk you through how we hire at Google for
9: all of our jobs, and share helpful details to prepare you for the experience!
13: The first step is getting your application to us.
15: Start by browsing open jobs around the world on our Careers site and find up to three jobs
19: that match your skills and interests.
21: Try to focus on roles where you meet all of the minimum qualifications, and ideally some
25: of the preferred.
26: Now, it's time to get your resume ready.
29: Check out the video in the description for our tips on how to make your resume stand
32: out!
33: One thing to point out here is that we don't require degrees from certain universities
37: (or a university at all, depending on the role) and your GPA is only part of your application
43: if you're a recent grad.
45: After you submit your application, we have a team of highly-trained pros who look over
49: your resume and connect the dots between your experience and roles at Google.
53: There's no one kind of Googler, so we're always looking for people who bring new perspectives
57: and life experiences that'll help us build stronger teams, products, and services for
61: all of our users.
63: We really care about making this part of the process fair and effective, so these reviewers
68: focus on each candidate instead of each application for a specific job.
73: Once your resume is reviewed, you may hear from a recruiter.
76: If you don't hear from us in a few weeks, you can assume that we're moving forward with
81: other candidates unless otherwise noted - but we might reach out in the future if another
85: role is a match.
87: After a recruiter reaches out to you, phone calls are usually next.
91: Typically, we'll chat and learn more about you, your interests, experience, etc.
95: You may then have phone interviews with Googlers that are more specific to the job or team.
102: For technical roles, this often means coding interviews, and for business roles they'll
106: focus on skills and experience specific to the job you applied for.
109: The next step is onsite interviews at Google - a really exciting day.
115: You'll usually have four 45-minute interviews where you meet a variety of Googlers, demonstrate
121: your abilities, and have time to ask questions about your interviewer, the role, and the team.
126: You may also have lunch with a Googler to learn more about what it's like to work here.
130: Now, let's talk through other important things to know about interviews.
134: We use vetted, high-quality questions that are tailored to the job you've applied for
137: and challenging (in a good way).
139: So don't worry, you won't be asked any brainteaser questions - our research shows
144: these types of questions aren't useful for assessing you!
147: All interviewers are trained and use standardized rubrics so that they're consistent and confident
152: in their assessments.
153: Regardless of the job you've applied for, there are four attributes we look for.
157: First is general cognitive ability.
159: We want to hire smart people who can learn and adapt to new situations, so this is about
164: how you learn and solve hard problems in real life, not about GPAs or test scores.
169: Second is role-related knowledge.
171: It's pretty straightforward - we want to make sure you have the experience, background,
174: and skills that'll set you up for success in the role.
179: Third is leadership.
180: We don't just look at job titles, since different team members will need to step into
183: leadership roles and contribute.
185: We look for examples of things like being a team player and navigating challenges to
189: make an impact.
190: And last, but not least, is Googleyness.
193: We want to make sure you can thrive here, so we look for signs of comfort with ambiguity,
198: bias to action, and a collaborative nature.
201: After interviews, your recruiter will share your interview feedback and scores, resume,
206: references, and any work samples you submitted with a hiring committee.
210: Hiring committees bring together Googlers who know the role best, but haven't met
213: any of the applicants, to offer a comprehensive, unbiased review.
218: If the committee recommends we hire you, that recommendation and all of your info is sent
222: to a senior leader-who provides another layer of objectivity-for final review.
227: If everything is approved, your recruiter will get in touch to make an offer!
232: And that's how we hire here at Google!
233: Check out the links in the description for more resources to help you prepare, and head
237: over to the Careers site to see our open jobs.
239: We hope to see your application soon!
What do Google's recruiters look for in a candidate? If you want to work for Google or another large software company it's a good idea to learn about their recruitment process and what qualities they look for in job candidates.
Register with Business English 23 to save words and phrases: Login