쉐도잉 연습: Interview Tips from a Senior Software Engineer... and a 4 year old - 영상으로 영어 말하기 배우기

연습 모드 선택

각 모드는 전체 화면 연습실로 열립니다.

171 문장

문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.

Hey everybody, it's Jesse, and I'm making this video today from a bunk bed.

This is my friend Ambrose And this is Taggy!

Oh, and my robot hand.

I really love robots!

This is my son

and today I want to talk a little bit about what I did to prepare for my interviews

So the last two videos on my channel were about my Google interview specifically

and then another video just more in general of my whole experience of interviewing.

So I had several questions about what I did to prepare.

So I'm going to go over some of the websites I used

and books and resources and I'm going to let you know which ones I think were the most helpful.

So just to start out, I interviewed for front-end developer positions,

front-end engineer, software engineer positions.

And so my, it was more front-end based for me, all of my interviews, interview questions, and my preparation.

So depending on whether you're front-end, back-end, or full-stack, and what languages you use, this may be a little bit different.

But one service that I think was really valuable was called Pramp.

It's P-R-A-M-P.

I'll make sure I put links to everything I talk about in the description.

So, PRAMP is a service where you sign up and you get paired up with someone else for a time slot.

So, I think it was like an hour time slot.

In the first half hour, one of you takes the role of the interviewer and the other one is the interviewee.

And then, for the second half of the time slot, you switch places.

so it gives you not only do you have a practice question

but you also have a time limit

and you have someone else that's asking the question

that you have to explain yourself to

that was really helpful they have it broken down by different categories so you can just do front-end related stuff

data structures and algorithms.

It can just blast.

Yeah.

Whoa.

I flew it.

And I love tagging.

Because of that, it stood out as being really unique and offering something that some of the other resources didn't.

If I can go to sleep, eat when I sleep without tagging.

If you don't have any experience, like a lot of experience with actual interviews.

Shhh, okay, let's be quiet.

If you don't have experience with interviews, then I definitely recommend PRAMP.

They may have like a free tier.

I'm not sure.

I think it is a paid service, but there may be some way to get some free things.

I'll find out and put more info in the description.

So the next thing that I used that was very, very helpful was a book called Cracking the Coding Interview.

And I know I mentioned this in some of my other videos, and I mentioned it to some of you that ask me questions directly.

It's a huge book.

It has a lot of information in it.

It was written by a woman who actually interviewed a lot of people at Google.

It goes through and explains what interviewers are thinking, what they're looking for when they actually interview you.

Just being able to get into that mindset of what interviewers are actually thinking helped me so much.

It helps me.

You know, there's so many things you could talk about or focus on when you're in an interview.

So just knowing what these people want to hear is great.

Okay, Darth Vader.

Actually, I'm a boss Thomas Spiegel and my last name's Weiger.

That's right.

So, I definitely recommend that book.

And I know Tygie's last name.

Tygie's last name is Ty.

Oh, okay.

There's also a ton of practice problems and explanations of data structures and algorithms.

So, if you were going for a more general software engineer position or a back-end position, then those practice problems would help you a lot.

For me, it wasn't that helpful.

because most of my questions were specifically front-end JavaScript related.

So it was still cool to go over some of that info.

I don't have a computer science background, so a lot of it was new to me.

So I'm sure it'll be helpful to me at some point, but just wasn't so much for the interview.

So if you're going for front-end stuff, then I think it's safe to skip over a lot of those sections of that book.

But the next resource that I used, and this is probably a little bit more front-end specific, is FreeCodeCamp.

So FreeCodeCamp has some practice interview questions,

and they also have some kind of less difficult JavaScript algorithm challenges.

So I think that's a great way to refresh your JavaScript knowledge should

if you already have a job um where you're not coding that much uh all the time

you want to get in the habit of of coding um as much as you can before you interview

you can go wash it off if you want Fine!

I ate a pancake at Jesus.

I'm in the carcass house.

So, I highly recommend Free Code Camp for a variety of things,

but in this case, for sure, for your interview prep.

And another resource that I used was JavaScript Data Structures and Algorithms book.

I'll put the official title and link to that below.

So I ended up getting the e-book.

So I had that on my phone.

So I got the hard copy of the Cracking the Coding interview.

But when I was in a situation where I didn't have my hard copy, but I always had my phone on me, then I could always look at that.

So that helped me because it was JavaScript specific, which is the language that I was being tested in. So

that was, it was easier for me to understand the example problems than what I was seeing in Cracking the Coding interview.

It was just another explanation of some of those data structures and algorithms, which, like I said, ended up not helping me that much because I didn't really get questions about it.

But if you are going for something that's a more full stack position or back end position, you may get asked questions about that.

So I highly recommend that as well.

Something that is back.

You're back.

And I'd recommend that for whatever books you're using,

I think it would be a good idea to have an electronic copy of the book.

So even if you like hard copies, that's great.

If you can only find it in hard copy, that's fine.

And sometimes, especially when you're looking at code, it's a lot easier to just have a hard copy sometimes.

But having that on my phone was so useful.

You know, if I was waiting in line, waiting at the doctor's office, you know, I didn't feel like I was wasting time.

I could always look at that in practice.

100

So it just kind of always kept it in my mind.

101

And I think that's really helpful. When you're...

102

You just need to be able to always be thinking about code.

103

It just makes it so much easier when you're actually on the spot in the interview.

104

You only have a short amount of time.

105

You're probably a little bit nervous.

106

So I think it's kind of like...

107

This is the Master Sword.

108

Yeah, it's the Master Sword from Zelda.

109

Yeah.

110

I mean, not the Master Sword, but a good replica.

111

I think like like you would approach let's say a foreign

112

language spoken language with more use you're gonna be more comfortable

113

when you actually get into a conversation with somebody the same way with coding even

114

if you didn't have great resources

115

but you still coded as as often as you could okay squeaky now no we're squeaking

116

if you throw it as often as you possibly could that's gonna be more useful than

117

if you have great resources the perfect books the perfect questions

118

and only looked over them

119

you know occasionally

120

just practice

121

actually go on the interview

122

just be be honest okay you don't have to you don't

123

have to be down on yourself you don't have to tell the interview all the things you don't know

124

but on the other hand don't claim that you know things

125

that you don't because they'll be able to figure it out really easily right

126

if they say hey do you know how to make a

127

network request in javascript you say oh yeah i do it all the time I say, okay, can you do it for me?

128

You know, write it on the whiteboard.

129

Well, then you're stuck, right, if you don't really know how to do it.

130

So just be honest.

131

You could say, you know what, hey, I've done it before, but I'm a little rusty on the syntax.

132

Or, you know what, I never actually had to do that.

133

I kind of know how it's done.

134

Can I just explain it to you?

135

So something like that is way more acceptable.

136

And if you have to just say, listen, I've never heard of that before.

137

Just say it.

138

And you can even add. So.

139

I really like her.

140

Hey, can I talk now?

141

Yeah.

142

Thank you. So. If you don't know.

143

Admit that you don't know.

144

But then it would be helpful to say.

145

Listen, like if I had to do that for my job.

146

Here's where I would go to find the answer.

147

You know, so say.

148

I would I would look this up on MDN or something like that

149

And then at least you would you could give some answer even

150

if you have no idea you've at least given some answer

151

And said like here's how I would approach this this problem

152

So Think I'm gonna wrap this video up The that was my my advice.

153

Let me know what you think if it's too distracting

154

here for the video or if you can't like I want Tiggy to say something and Tiggy say something

155

I really like toys and I really like animals

156

and I really am spitty and I eat humans

157

and I really want pancakes and butter and bread and everything in the whole world.

158

I'm going to say goodbye to everybody on YouTube.

159

Would you like to say goodbye?

160

Bye.

161

Bye.

162

Bye.

163

That was Heidi.

164

Bye.

165

That was me.

166

All right.

167

And now you.

168

See you later, everybody.

169

Hopefully this helped.

170

And give me your ideas for what videos I should do next.

171

Until next time, have a great day.

앱 다운로드

유창하게 말하는 데 필요한 모든 것

AI 발음 평가문장마다 점수 확인

IPA 발음 연습모든 소리 마스터

단어 학습나만의 단어장 만들기

단어 게임놀면서 외우기

QR 스캔

Download on theApp Store Get it onGoogle Play

📺 같은 채널

How to friction-max your learning with software engineer Jessica Rose [Podcast #216]

Daily ConversationUniversity StudentsWorking Adults

Inside a Hong Kong Hackathon [Full Documentary]

Daily ConversationUniversity StudentsWorking Adults

✨ 추천 영상

23 문장

🔥HR Interview Questions and Answers (2025) | Top HR Interview Questions for Freshers | Intellipaat

Business EnglishInterview EnglishUniversity Students

101 문장

3.3k

Business EnglishInterview EnglishUniversity Students

443 문장

pv content

Business EnglishInterview EnglishUniversity Students

119 문장

Cracking the Behavioral Interview for Software Developers

Interview EnglishUniversity StudentsWorking Adults

74 문장

Improve Your Speaking

Business EnglishInterview EnglishUniversity Students

이 레슨의 어휘와 말하기 포인트

이 B2 수준 말하기 레슨은 영상 “Interview Tips from a Senior Software Engineer... and a 4 year old”을(를) 바탕으로 합니다. 이 영상에는 섀도잉할 문장 171개와 단어 1799개가 있습니다. 말하는 구간의 길이는 12:55입니다. 화자는 분당 약 139단어의 일정한 속도로 말해서 섀도잉하기에 편한 속도입니다. 단어의 85%가 영어에서 가장 많이 쓰이는 3,000단어에 속합니다. 나머지는 연습 전에 미리 확인해 두세요.

이 영상의 핵심 어휘

영상에서 가장 어려운 단어 11개를 발음, 뜻과 함께 정리했습니다.

단어	발음	뜻
algorithm 명사	/ˈælɡəɹɪðm̩/	알고리즘, 알고리듬
interviewer 명사	/ˈɪntɚvjuɚ/	면접관
pancake 명사	/ˈpæn.keɪk/	팬케이크, 블리니
stack 명사	/stæk/	무더기
carcass 명사	/ˈkɑɹkəs/	사체
preposition 명사	/ˌpɹɛpəˈzɪʃən/	전치사
whiteboard 명사	/ˈwaɪtbɔɹd/	화이트보드, 백판
syntax 명사	/ˈsɪn.tæks/	통어론, 구문론
refresh 동사	/ɹɪˈfɹɛʃ/	새롭게 하다
wrap 동사	/ɹæp/	싸다
depend 동사	/dɪˈpɛnd/	의존하다, ...에 달려 있다

영상에 나오는 구동사

단어	뜻
look over 동사	훑어보다

따라 말해 볼 만한 문장

영상에 나오는 짧고 완결된 문장으로, 일상 대화에서 그대로 쓸 수 있습니다:

Shhh, okay, let's be quiet.
For me, it wasn't that helpful.
Can I just explain it to you?
Hey, can I talk now?
Would you like to say goodbye?

이 영상의 문법

화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.

문형	영상 속 표현
수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점	was called · was written · being tested
현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때	I've done · I've never heard
관계절 who / which + 절 — 사람이나 사물에 대한 추가 정보	woman who actually · specific, which is

주의할 발음

화자는 don't, you're, I'm 같은 축약형과 약화된 형태를 56번 사용합니다. 들리는 대로 짧게 발음하세요.

“sh”와 “zh” 소리: preposition /ˌpɹɛpəˈzɪʃən/, refresh /ɹɪˈfɹɛʃ/
긴 단어 — 강세 위치에 주의: interviewee /ˌɪn.tɚ.vjuːˈiː/, preposition /ˌpɹɛpəˈzɪʃən/, developer /dɪˈvɛləpɚ/

한국어 화자가 어려워하는 소리:

/v/ — ㅂ(/b/)과 구별하기: interviewer /ˈɪntɚvjuɚ/, interviewee /ˌɪn.tɚ.vjuːˈiː/, developer /dɪˈvɛləpɚ/
/r/과 /l/ 구별하기: algorithm /ˈælɡəɹɪðm̩/, replica /ˈɹɛplɪkə/

이 영상으로 연습하는 방법

먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
보통 속도로 한 문장씩 섀도잉하고, 화자의 리듬과 맞을 때까지 반복합니다.
자신의 목소리를 녹음해 원본과 비교하고, algorithm, interviewer, pancake 같은 단어에 특히 주의합니다.

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →

쉐도잉 연습: Interview Tips from a Senior Software Engineer... and a 4 year old - 영상으로 영어 말하기 배우기

연습 모드 선택

앱 다운로드

How to friction-max your learning with software engineer Jessica Rose [Podcast #216]

Inside a Hong Kong Hackathon [Full Documentary]

Interviewing Part 1 - What You Need To Ask In Advance

Senior Product Designer Mock Interview: App Critique of Yelp

A Day in the Life of an Amazon Software Engineer

My Senior UX Design Interview Experience | tips, questions, prep, & more!

Data Science Interview Prep: 3 Key Resources You Need to Know

Mastering iOS Development: Mock Interview with Ramiro Neto

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

🔥HR Interview Questions and Answers (2025) | Top HR Interview Questions for Freshers | Intellipaat

3.3k

pv content

Cracking the Behavioral Interview for Software Developers

Improve Your Speaking

이 레슨의 어휘와 말하기 포인트

이 영상의 핵심 어휘

영상에 나오는 구동사

따라 말해 볼 만한 문장

이 영상의 문법

주의할 발음

이 영상으로 연습하는 방법

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법