WARM-UP VIDEO FOR FREQUENTLY USED NOUNS

Instructions. Fill the gaps with one of the following words: time(s)|year(s)|way(s)|thing(s)|world(s)|person

------------------------------------

Exercise. Complete each gap with suitable words and expressions you hear from the video.

Ben: Absolutely. So, what I always tell folks when I'm doing interviews, at least, is that the people that do programming, computer science. It's kind of, there's this long sliding scale of extreme practical experience all the (1) ………….. to extreme theoretical experience. Right? And at one end of the extreme you might have somebody who just got a Ph. D. in computer science to write essays on computational complexity, but you ask them to write five lines of code Fitz: Right. Ben: On the other extreme, you've got somebody who's maybe been programming on a microprocessor in a cell phone for 20 (2) ………….. and is so incredibly specialized and amazing at writing assembly language that they've forgotten all the theory they've ever learned. Right? And so, Google is looking for someone in the middle, who's got theory at their fingertips but also has Ben: Yeah so, we are going to look on your resume for proof of some sign of generalism, right? That you've got practical experience, you've got theoretical experience, and that you're able to learn new (3) ………….. and adapt. Fitz: Right. Ben: And then the theory is that if Google hires you they're hiring you as a generalist, okay? Someone- so skills and experience are important, but you've gotta be a good fit for the company, for the culture. I mean, we work in the internet, right? The internet (4) ………….. is a very disruptive (5) ………….. , a lot of change, a lot of new stuff's constantly coming up. You should have to be able to learn new (6) ………….. and roll with the punches, so to speak. Ben: And play well with others, which is not always a given. [laughing] Fitz: Right. Well, that's important, but the other (7) ………….. is that we want to look for something that is going to make you stand out. That's what we look for in a prospective candidate. Whether it's an interesting hobby or an accomplishment or some leadership (8) ………….. that you've done. Ben: Right. Because we see a lot of resumes that are just full of millions of generic acronyms, and they all kind of look the same after a while. So... Fitz: Right. Ben: ...figure out some (9) ………….. to distinguish yourself. That says, I not only know what I'm doing, but here's something interesting that proves I have a passion for computer science. Fitz: Right. Ben: That's another (10) ………….. I always say to folks... Fitz: Or not even just computer science...it could be anything just so... Ben: or anything, yeah. Engineering in general. Fitz: Yeah, engineering in general. Ben: So, you know, I always tell people, or I always I think to myself when I'm interviewing somebody, "If this (11) ………….. were a millionaire and did not have to work at all, would they still be playing around on a computer? Would they still be writing code or doing engineering (12) ………….. for fun?" And, if so, then that's the kind of (13) ………….. I want to work with. Fitz: Right, is it their passion? Ben: Is it their passion? Right. They're not just doing because they have to pay the rent. Fitz: And we come from the open source (14) ………….. , so that's something we are particularly looking out for in people. We find that people who write open source code are often a good fit for Google... Ben: They're passionate. [laughing] Fitz: ...because you're not going to spend you spare (15) ………….. writing software if you're not good at it. Right? Ben: Or if you're not passionate about it. Fitz: Or if you're not passionate about it. So those are two qualities that tend to fall in to people that write software in their spare (16) ………….. I'd say. Ben: It's not a requirement that you work on open sources... Fitz: Right. Ben: Yeah, great. Fitz: All right. Ben: We'll see you next (17) …………... Fitz: Come back soon.

Key: Look at the key and say aloud the script from the video to improve your English.

Ben: Absolutely. So, what I always tell folks when I'm doing interviews, at least, is that the people that do programming, computer science. It's kind of, there's this long sliding scale of extreme practical experience all the (1) (way) to extreme theoretical experience. Right? And at one end of the extreme you might have somebody who just got a Ph. D. in computer science to write essays on computational complexity, but you ask them to write five lines of code Fitz: Right. Ben: On the other extreme, you've got somebody who's maybe been programming on a microprocessor in a cell phone for 20 (2) (years) and is so incredibly specialized and amazing at writing assembly language that they've forgotten all the theory they've ever learned. Right? And so, Google is looking for someone in the middle, who's got theory at their fingertips but also has Ben: Yeah so, we are going to look on your resume for proof of some sign of generalism, right? That you've got practical experience, you've got theoretical experience, and that you're able to learn new (3) (things) and adapt. Fitz: Right. Ben: And then the theory is that if Google hires you they're hiring you as a generalist, okay? Someone- so skills and experience are important, but you've gotta be a good fit for the company, for the culture. I mean, we work in the internet, right? The internet (4) (world) is a very disruptive (5) (world) , a lot of change, a lot of new stuff's constantly coming up. You should have to be able to learn new (6) (things) and roll with the punches, so to speak. Ben: And play well with others, which is not always a given. [laughing] Fitz: Right. Well, that's important, but the other (7) (thing) is that we want to look for something that is going to make you stand out. That's what we look for in a prospective candidate. Whether it's an interesting hobby or an accomplishment or some leadership (8) (thing) that you've done. Ben: Right. Because we see a lot of resumes that are just full of millions of generic acronyms, and they all kind of look the same after a while. So... Fitz: Right. Ben: ...figure out some (9) (way) to distinguish yourself. That says, I not only know what I'm doing, but here's something interesting that proves I have a passion for computer science. Fitz: Right. Ben: That's another (10) (thing) I always say to folks... Fitz: Or not even just computer science...it could be anything just so... Ben: or anything, yeah. Engineering in general. Fitz: Yeah, engineering in general. Ben: So, you know, I always tell people, or I always I think to myself when I'm interviewing somebody, "If this (11) (person) were a millionaire and did not have to work at all, would they still be playing around on a computer? Would they still be writing code or doing engineering (12) (things) for fun?" And, if so, then that's the kind of (13) (person) I want to work with. Fitz: Right, is it their passion? Ben: Is it their passion? Right. They're not just doing because they have to pay the rent. Fitz: And we come from the open source (14) (world) , so that's something we are particularly looking out for in people. We find that people who write open source code are often a good fit for Google... Ben: They're passionate. [laughing] Fitz: ...because you're not going to spend you spare (15) (time) writing software if you're not good at it. Right? Ben: Or if you're not passionate about it. Fitz: Or if you're not passionate about it. So those are two qualities that tend to fall in to people that write software in their spare (16) (time) I'd say. Ben: It's not a requirement that you work on open sources... Fitz: Right. Ben: Yeah, great. Fitz: All right. Ben: We'll see you next (17) (time) . Fitz: Come back soon.

Sources: 

Channel: Life at Google. Ask a Google Engineer - Fitz and Ben from Chicago - Prospective Employee Qualities: https://www.youtube.com/watch?v=1BGAdJ_0FH0

---------------------------------------------

Compiled by Top Grade Edu