跟读练习: Interview Tips from a Senior Software Engineer... and a 4 year old - 通过视频学习英语口语

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.

📺 同频道

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

✨ 推荐视频

231 句

Describe a Job Interview You Had | IELTS Speaking Part 2 & 3 | Band 9 Vocabulary | Learnivo #ielts

IELTS PrepBusiness EnglishInterview English

本课的词汇与口语要点

这节 B2 级别的口语课以视频“Interview Tips from a Senior Software Engineer... and a 4 year old”为素材。这段视频共有 171 个句子、1799 个单词可供跟读。讲话部分时长为 12:55。说话人语速平稳，每分钟约 139 个词，很适合跟读。 85% 的单词属于英语最常用的 3,000 词，其余的词建议在练习前先学一下。

视频中的重点词汇

视频中最难的 15 个单词，附发音和释义：

单词	发音	释义
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ɹɛʃ/	提神
replica 名词	/ˈɹɛplɪkə/	複製品 /复制品, 仿製品 /仿制品
distract 动词	/dɪˈstɹækt/	分心
whoa	/woʊ/	吁
mindset 名词	/ˈmaɪn(d)ˌsɛt/	心態 /心态, 思維模式 /思维模式
tier 名词	/ˈtɪɚ/	層 /层, 排
wrap 动词	/ɹæp/	包裝 /包装, 包

视频中出现的短语动词

单词	释义
end up 动词	到达
break down 动词	壞了 /坏了, 出故障
find out 动词	找出, 查明
go through 动词	通過 /通过
sign up 动词	報名 /报名, 註冊 /注册

值得反复跟读的句子

视频中简短而完整的句子，可以直接用在日常对话里：

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

需要注意的发音

说话人用了 56 次缩略和弱读形式，例如 don't, you're, I'm。请按听到的简短形式来说。

“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/ — 不要读成 /w/，上齿轻触下唇: interviewer /ˈɪntɚvjuɚ/, interviewee /ˌɪn.tɚ.vjuːˈiː/, developer /dɪˈvɛləpɚ/
词尾辅音 — 要读清楚，后面不要加元音: slot /slɑt/, pancake /ˈpæn.keɪk/, stack /stæk/, carcass /ˈkɑɹkəs/, squeak /skwiːk/
/r/ 和 /l/ 的区别: algorithm /ˈælɡəɹɪðm̩/, replica /ˈɹɛplɪkə/

如何用这段视频练习

先完整听一遍视频，不要开口，记下不认识的单词。
用正常速度逐句跟读，每句重复到你的节奏与说话人一致为止。
录下自己的声音并与原声对比，特别注意 algorithm, interviewer, pancake 这类单词。

什么是跟读法？

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

影子跟读法: 阅读完整分步指南 →

跟读练习: 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]

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

Improve Your Speaking

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

I'm an ex-Google interviewer. You're doing LeetCode wrong.

Doing This (Almost) GUARANTEES You Get Hired In A Job Interview!

Mastering iOS Development: Mock Interview with Ramiro Neto

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

Phone Interview with a Recruiter

My Entire Job Search Process: Software Engineer Resume & Interviews

pv content

Cracking the Behavioral Interview for Software Developers

Describe a Job Interview You Had | IELTS Speaking Part 2 & 3 | Band 9 Vocabulary | Learnivo #ielts

本课的词汇与口语要点

视频中的重点词汇

视频中出现的短语动词

值得反复跟读的句子

视频中的语法

需要注意的发音

如何用这段视频练习

什么是跟读法？